You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using azuremonitor as exporter using the Otel Contrib distribution, exceptions which are logged per symantec definition of OpenTelemetry is forward to Azure Monitor as traces, not exceptions.
Steps to Reproduce
Setup otel azuremonitor contrib.
Configure span to include required attributes exception.type, exception.message
Await data in application insights, and verify that no exceptions has been logged, but an entry in traces exists.
Expected Result
Log records of span specified as exceptions, end in the exceptions table.
Actual Result
Log records appear in traces table.
Suggested code change:
Alter log_to_envelope.go. Change LogRecordToEnvelope(*) to use contracts.NewExceptionData() when span attributes fulfill the symantec specification of an exception.
Collector version
v.0.120.0
Environment information
Environment
OS: Ubuntu 20.04 and Windows 11.102
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component(s)
exporter/azuremonitor
What happened?
Description
When using azuremonitor as exporter using the Otel Contrib distribution, exceptions which are logged per symantec definition of OpenTelemetry is forward to Azure Monitor as traces, not exceptions.
Steps to Reproduce
Expected Result
Log records of span specified as exceptions, end in the exceptions table.
Actual Result
Log records appear in traces table.
Suggested code change:
Alter log_to_envelope.go. Change
LogRecordToEnvelope(*)
to usecontracts.NewExceptionData()
when span attributes fulfill the symantec specification of an exception.Collector version
v.0.120.0
Environment information
Environment
OS: Ubuntu 20.04 and Windows 11.102
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: