Closed rajim17 closed 1 year ago
Thank you for opening this, @rajim17. It sounds very similar to issue #18899 which has an open PR in #18898. Could it potentially help with your use case if you provide review on that PR and/or improve the specification in the issue?
@nslaughter Thanks for pointing out. I should be able to contribute. I will review and add my comments
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
This issue has been closed as inactive because it has been stale for 120 days with no activity.
The purpose and use-cases of the new component
This component is to collect metrics from Azure Monitor platform and parse into OTLP metric format. Azure Monitor provides OS/CPU and major resource level metrics users are interested. List of metrics supported by Azure Monitor can be found here.
Component also provides a way to configure interested metric namespaces to collect.
Example configuration for the component
Telemetry data types supported
Metrics
Is this a vendor-specific component?
Sponsor (optional)
No response
Additional context