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

[Azure Monitor Exporter] Span Events support #16260

Closed
JorTurFer opened this issue Nov 11, 2022 · 3 comments
Closed

[Azure Monitor Exporter] Span Events support #16260

JorTurFer opened this issue Nov 11, 2022 · 3 comments
Labels

Comments

@JorTurFer
Copy link

JorTurFer commented Nov 11, 2022

Component(s)

exporter/azuremonitor

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

Open Telemetry supports Span Events, and we use them in our applications because they are used for sending exceptions (as the protocol says at least for dotnet). We are checking the collector to remove the process in the apps but azure monitor exporter doesn't support any type of Span Events.

Describe the solution you'd like

I'd like to have full implemented behavior for Span Events in azure monitor, sending the exceptions to the azure monitor exceptions table and the other events to the custom events table.

Describe alternatives you've considered

There isn't any alternative, this is a blocker for us because we need at least the exceptions part implemented, or we can't move to collector because we would lose very valuable information.
The only alternative is forking and detaching our branch from the upstream, what we would like to avoid.

Additional context

I'm willing to contribute with the feature and opening a PR if you find it useful

@JorTurFer JorTurFer added enhancement New feature or request needs triage New item requiring triage labels Nov 11, 2022
@github-actions
Copy link
Contributor

Pinging code owners:

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

@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 Jan 11, 2023
@fatsheep9146
Copy link
Contributor

I think this issue is solved by #16354, closed.

@fatsheep9146 fatsheep9146 removed Stale needs triage New item requiring triage labels Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants