-
Notifications
You must be signed in to change notification settings - Fork 13
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
Logs ingested with OTeL not showing detected_level and Detected Fields #486
Comments
Structured metadata used by OTEL is not yet supported in Explore Logs but we're working on this actively. #310 |
Will this include the level? What label does 'detected_level' search for? |
Just to be sure, which Loki version are you using and is the In this case it should get the |
loki version 3.0.0 and yes, im using the default value which is true for discover_log_levels |
Thanks @omri-shilton. In Loki 3.0.0 we wrote the |
FYI, I'll keep this issue open as we might consider being backwards compatible. Will update you accordingly, @omri-shilton. |
@svennergr is this still related to the fact that im using OTeL? because I dont have a label level or detected_level. i didnt configure anything special other than the fact to listen to otel logs and im sending them like instructed here: https://grafana.com/docs/enterprise-logs/latest/send-data/otel/ |
Got it, im waiting for the PR on that fix. for now it doesnt even seem to have a PR. |
Should be fixed by #736 |
@gtk-grafana it appears that the fix did not solve my issue. |
Hi @omri-shilton, As described, you would need to upgrade your Loki version to 3.2.0 which is the latest supported Loki version. |
@svennergr thanks, it works now |
We use OTeL for our logs and it works great.
In the regular explore it automatically structures the attributes as metadata and identifies the level.
In explore:
In explore logs it doesnt:
Are we doing something wrong?
The text was updated successfully, but these errors were encountered: