Skip to content
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

Open
3 tasks done
narcis96 opened this issue Sep 2, 2024 · 7 comments
Open
3 tasks done

New component: huaweicloudcesreceiver #34953

narcis96 opened this issue Sep 2, 2024 · 7 comments
Labels
Accepted Component New component has been sponsored

Comments

@narcis96
Copy link
Contributor

narcis96 commented Sep 2, 2024

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?

  • This is a vendor-specific component
  • If this is a vendor-specific component, I am a member of the OpenTelemetry organization.
  • If this is a vendor-specific component, I am proposing to contribute and support it as a representative of the vendor.

Code Owner(s)

@narcis96 , @heitorganzeli

Sponsor (optional)

@mwear

Additional context

No response

@narcis96 narcis96 added needs triage New item requiring triage Sponsor Needed New component seeking sponsor labels Sep 2, 2024
@narcis96 narcis96 changed the title New component: huaweicloudcesreceiver New component: huaweicloudreceiver Sep 3, 2024
@atoulme
Copy link
Contributor

atoulme commented Sep 4, 2024

@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?

@narcis96 narcis96 changed the title New component: huaweicloudreceiver New component: huaweicloudmetricsreceiver Sep 4, 2024
@narcis96 narcis96 changed the title New component: huaweicloudmetricsreceiver New component: huaweicloudcesreceiver Sep 4, 2024
@crobert-1
Copy link
Member

@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. 👍

@heitorganzeli
Copy link

heitorganzeli commented Sep 6, 2024

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

@crobert-1
Copy link
Member

Do you have any suggestions on how to get those two sponsors?

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. 👍

@narcis96
Copy link
Contributor Author

narcis96 commented Oct 22, 2024

@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
Copy link
Contributor Author

@mwear @atoulme can you please let us know how we can proceed with this component ?

@mwear
Copy link
Member

mwear commented Oct 29, 2024

@narcis96 I will sponsor this. Please review the guidelines, especially the bullet point labelled "First PR".

@mwear mwear added Accepted Component New component has been sponsored and removed Sponsor Needed New component seeking sponsor labels Oct 29, 2024
bogdandrutu pushed a commit that referenced this issue Nov 21, 2024
#### 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.
dmitryax pushed a commit that referenced this issue Dec 10, 2024
Description
Adds initial implementation of huaweicloudces.

Link to tracking issue

#34953
sbylica-splunk pushed a commit to sbylica-splunk/opentelemetry-collector-contrib that referenced this issue Dec 17, 2024
…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.
sbylica-splunk pushed a commit to sbylica-splunk/opentelemetry-collector-contrib that referenced this issue Dec 17, 2024
Description
Adds initial implementation of huaweicloudces.

Link to tracking issue

open-telemetry#34953
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Component New component has been sponsored
Projects
None yet
Development

No branches or pull requests

5 participants