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

Add StackTrace to exporter/awscloudwatchlogs #31905

Closed
podger opened this issue Mar 22, 2024 · 5 comments
Closed

Add StackTrace to exporter/awscloudwatchlogs #31905

podger opened this issue Mar 22, 2024 · 5 comments
Labels
enhancement New feature or request exporter/awscloudwatchlogs awscloudwatchlogs exporter needs triage New item requiring triage

Comments

@podger
Copy link

podger commented Mar 22, 2024

Component(s)

exporter/awscloudwatchlogs

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

Is there any technical reason why the stacktrace is not supported in this exporter?

Describe the solution you'd like

Add the Stacktrace for the cloudwatchlogsexpoter

Describe alternatives you've considered

No response

Additional context

No response

@podger podger added enhancement New feature or request needs triage New item requiring triage labels Mar 22, 2024
@github-actions github-actions bot added the exporter/awscloudwatchlogs awscloudwatchlogs exporter label Mar 22, 2024
Copy link
Contributor

Pinging code owners:

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

@crobert-1
Copy link
Member

Excuse my ignorance, can you share what StackTrace means in the context of this exporter?

@podger
Copy link
Author

podger commented Apr 4, 2024

@crobert-1 Maybe I'm misusing this exporter but in my use case I use it to upload my application logs (errors, crash, info etc) to cloudwatch. Only the exception message is uploaded. The stacktrace is somehow lost.

@crobert-1
Copy link
Member

No worries! Thanks for clarifying, that makes sense. The next step is to try to better understand what component is causing the result to be different than what's expected.

Can you share your full config? Also, can you use the debug exporter configured with verbosity: detailed in your pipeline instead of the Amazon CloudWatch Logs exporter, and then share the output? This will help determine if the exporter itself dropping the stack traces, or if your logs simply don't have them in the first place.

@podger
Copy link
Author

podger commented Apr 8, 2024

Trying to setup the debugging exporter I figured it out myself. The .NET LogRecord doesn't track the StackTrace, I have to use different method: Activity.RecordException to track the exception within the trace and I have all metadata there.

Thanks for the help anyway! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request exporter/awscloudwatchlogs awscloudwatchlogs exporter needs triage New item requiring triage
Projects
None yet
Development

No branches or pull requests

3 participants