-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New component: huaweicloudcesreceiver #34953
Comments
@mwear you would be the next sponsor for vendor-backed component. Please see https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#rotating-sponsors for background. Would you please review? |
FYI, for a sponsor to be automatically assigned, the process now requires the contributor to be a member of the OpenTelemetry organization, from my understanding. That being said, @mwear is welcome to sponsor regardless. Also, @narcis96 and @heitorganzeli, it would be great if you could become OpenTelemetry organization members. It's not too cumbersome of a process, and will be necessary to be able to support this component going forward. 👍 |
Hello @crobert-1 , We'd love to follow the process to become members. However, we've just saw that it requires two sponsors. This is actually our first interaction with the community. Do you have any suggestions on how to get those two sponsors? Thank you created this request for now: open-telemetry/community#2339 |
Once you've contributed to an OpenTelemetry project you can add links to your contributions there. Usually in contributing to different issues you'll interact with project approvers and maintainers, the people who are able to sponsor. At that point, you can reach out to the approver/maintainer you've interacted with on the CNCF Slack and request their sponsorship. 👍 |
@crobert-1 I have became OpenTelemetry organization member. See open-telemetry/community#2340 Are there any other steps needed so we can proceed with this component ? |
@narcis96 I will sponsor this. Please review the guidelines, especially the bullet point labelled "First PR". |
#### Description Introduce a new receiver, huaweicloudces receiver. This is the first PR as skeleton for the receiver. #### Link to tracking issue Related to #34953 #### Testing N/A <!--Describe the documentation added.--> #### Documentation metadata.yaml, README.
Description Adds initial implementation of huaweicloudces. Link to tracking issue #34953
…y#36258) #### Description Introduce a new receiver, huaweicloudces receiver. This is the first PR as skeleton for the receiver. #### Link to tracking issue Related to open-telemetry#34953 #### Testing N/A <!--Describe the documentation added.--> #### Documentation metadata.yaml, README.
Description Adds initial implementation of huaweicloudces. Link to tracking issue open-telemetry#34953
The purpose and use-cases of the new component
This receiver contains the implementation of the Huawei Cloud Cloud Eye Service (CES) receiver for the OpenTelemetry Collector. The receiver collects metrics from Huawei Cloud's CES service and sends them to the OpenTelemetry Collector for processing and exporting.
Example configuration for the component
receivers:
huaweicloudcesreceiver:
collection_interval: 3h
initial_delay: 5s
region_id: eu-west-101
access_key: ${env:HUAWEICLOUD_SDK_AK}
secret_key: ${env:HUAWEICLOUD_SDK_SK}
project_id: "project_1"
period: 300
filter: average
no_verify_ssl: True
Telemetry data types supported
metrics
Is this a vendor-specific component?
Code Owner(s)
@narcis96 , @heitorganzeli
Sponsor (optional)
@mwear
Additional context
No response
The text was updated successfully, but these errors were encountered: