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
Currently, the only available logging format supported by the Faro Receiver is logfmt. JSON is a widely adopted standard for logging and is also the only structured format supported in addition to logfmt in LogQL queries.
Our concrete use-case is the we use the faro.receiver which uses logfmt , but our developers complains that this makes combined searches hard for them because everything else we have in our company uses json as log format.
The text was updated successfully, but these errors were encountered:
This issue has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!
Hi Team, I would like to work on this issue, I can see logs, traces and metrics exported from receiver. I think this format is applicable only for logs ? I am hoping the format option is only applicable for logs ? Correct me if my understanding is incorrect
Request
Currently, the only available logging format supported by the Faro Receiver is logfmt. JSON is a widely adopted standard for logging and is also the only structured format supported in addition to logfmt in LogQL queries.
Ref: https://grafana.slack.com/archives/C01050C3D8F/p1728549514784879
Use case
Our concrete use-case is the we use the faro.receiver which uses logfmt , but our developers complains that this makes combined searches hard for them because everything else we have in our company uses json as log format.
The text was updated successfully, but these errors were encountered: