-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New component: googlecloudmonitoringreceiver #33762
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
Labels
Accepted Component
New component has been sponsored
enhancement
New feature or request
Vendor-Specific Component
New component that interfaces with a vendor API and will be maintained by the vendor.
Comments
I will sponsor the component |
We can go over the configuration in the implementation PR. I would expect the config to look similar to the list API: https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.timeSeries/list |
This was referenced Jul 3, 2024
TylerHelmuth
pushed a commit
that referenced
this issue
Sep 5, 2024
…a to OTel Metrics Conversion Pipeline (#34677) **Description:** Transform GCP Timeseries Data to OTel Metrics Pipeline by establishing a client connection to the Google Cloud Monitoring API. This PR scrapes timeseries data based on configured metrics and converts it into the OpenTelemetry format for pipeline processing. **Link to tracking Issue:** #33762 **Testing:** No additional test cases were added. Existing tests cover the necessary functionality. **Documentation:** The **README.md** file was previously added and already includes relevant details about the component and the conversion process.
f7o
pushed a commit
to f7o/opentelemetry-collector-contrib
that referenced
this issue
Sep 12, 2024
…ng receiver (open-telemetry#34015) **Description:** Adding Google Cloud Monitoring receiver Closes open-telemetry#33762 **Testing:** Test cases for configuration added **Documentation:** README file added for describing the component
f7o
pushed a commit
to f7o/opentelemetry-collector-contrib
that referenced
this issue
Sep 12, 2024
…a to OTel Metrics Conversion Pipeline (open-telemetry#34677) **Description:** Transform GCP Timeseries Data to OTel Metrics Pipeline by establishing a client connection to the Google Cloud Monitoring API. This PR scrapes timeseries data based on configured metrics and converts it into the OpenTelemetry format for pipeline processing. **Link to tracking Issue:** open-telemetry#33762 **Testing:** No additional test cases were added. Existing tests cover the necessary functionality. **Documentation:** The **README.md** file was previously added and already includes relevant details about the component and the conversion process.
codeboten
added a commit
that referenced
this issue
Sep 25, 2024
…ceiver component stability to alpha (#35136) **Description:** This PR moves the stability of the googlecloudmonitoringreceiver component to alpha **Link to tracking Issue:** #33762 **Testing:** No additional test cases were added **Documentation:** Previously updated --------- Signed-off-by: Alex Boten <[email protected]> Co-authored-by: Alex Boten <[email protected]>
jriguera
pushed a commit
to springernature/opentelemetry-collector-contrib
that referenced
this issue
Oct 4, 2024
…ceiver component stability to alpha (open-telemetry#35136) **Description:** This PR moves the stability of the googlecloudmonitoringreceiver component to alpha **Link to tracking Issue:** open-telemetry#33762 **Testing:** No additional test cases were added **Documentation:** Previously updated --------- Signed-off-by: Alex Boten <[email protected]> Co-authored-by: Alex Boten <[email protected]>
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
enhancement
New feature or request
Vendor-Specific Component
New component that interfaces with a vendor API and will be maintained by the vendor.
The purpose and use-cases of the new component
The component will retrieve GCP Cloud Monitoring timeseries data and convert it into Otel compatible data format.
Example configuration for the component
Telemetry data types supported
Metrics
Is this a vendor-specific component?
Code Owner(s)
Tyler Helmuth, Abhishek Kothari
Sponsor (optional)
David Ashpole (dashpole)
Additional context
#2286
The component has already been accepted by the sponsor and we are on track to create the first PR soon. This issue is to primarily abide by the new component process as per the contribution guidelines.
The text was updated successfully, but these errors were encountered: