-
Notifications
You must be signed in to change notification settings - Fork 70
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
pushError loses context data #486
Labels
bug
Report a bug
Comments
Having this exact same issue, any updates / fixes in sight? |
Anyone looking at this? We think we are running into the same issue. |
4 tasks
Found the issue: grafana/alloy#1413 |
The fix will be release with Alloy v1.4 |
Alloy v1.4 i already released. Closing this issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Context data attached to a error via the context object gets lost in the backend when using Grafana Agent.
The issue was reported on the Faro community Slack.
I tested it with the Faro Receiver in cloud and the Grafana Agent.
Faro receiver works well, but when using the Agent the context attributes do not appear in the Loki log.
Steps to reproduce
I started the Demo app which uses the Grafana Agent and sent a custom error with context attributes attached.
The context attributes did not show up in the error log.
Then I started the fe-o11y plugin, which is using the Faro receiver, locally and sent a custom error with context attributes attached as well.
The context attributes showed up in the error log as excpected.
Expected behavior
Context attributes should appear in the Loki log.
Actual behavior
context attributes do not appear in the Loki log.
Environment
Demo
Context
The text was updated successfully, but these errors were encountered: