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

[receiver/azureeventhub] Allow Metrics in Azure Resource Log format to be received #18690

Closed
cparkins opened this issue Feb 15, 2023 · 7 comments

Comments

@cparkins
Copy link
Contributor

Component(s)

receiver/azureeventhub

Is your feature request related to a problem? Please describe.

Currently when receiving events in from Azure Event Hubs only log events are supported. When working with Azure Monitor (Diagnostic Settings) there are two types of Events supported: Log and Metrics.

Describe the solution you'd like

Allow the Azure Event Hub Receiver to receive metrics by converting the Azure Resource Logs into Open Telemetry Metrics to be processed by the Collector pipeline.

Describe alternatives you've considered

Creating a process to convert from Log Events into Metrics in Splunk.

Additional context

I think logically it makes sense to separate the two types to allow Azure Metrics to be processed in a separate pipeline for use cases where the Metrics may or may not be processed elsewhere.

@cparkins cparkins added enhancement New feature or request needs triage New item requiring triage labels Feb 15, 2023
@github-actions
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@atoulme
Copy link
Contributor

atoulme commented Feb 16, 2023

That's a good idea. @cparkins you showed me a fragment of such a metric doc as json, and I guess we could directly translate that to metric data and have the receiver deal with metrics.

Please let us know if you're interested to help out on this.

@atoulme atoulme removed the needs triage New item requiring triage label Feb 16, 2023
@cparkins
Copy link
Contributor Author

I'm absolutely interested in helping. Still working through my companies CLA process (I should have a meeting sometime soon to discuss my contributions).

@github-actions
Copy link
Contributor

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.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Apr 18, 2023
@atoulme
Copy link
Contributor

atoulme commented Apr 18, 2023

@cparkins did this land? I think it did but can't remember off the top of my head.

@cparkins
Copy link
Contributor Author

cparkins commented Apr 18, 2023

@cparkins did this land? I think it did but can't remember off the top of my head.

@atoulme It absolutely did. I'm using it in a container so it's there.

@atoulme
Copy link
Contributor

atoulme commented Apr 18, 2023

Closing! Thanks!

@atoulme atoulme closed this as completed Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants