Troubleshooting
This page address common issues when getting started and using Grafana Logs Drilldown.
Can’t see Logs Drilldown in the menu
Grafana Explore Logs is installed by default in Grafana versions Grafana v11.3.0 through v11.5.
Grafana Logs Drilldown is installed by default in Grafana versions Grafana 11.6 and later.
For more information about the name change for this feature, see this blog post.
If you do not see Logs Drilldown under either name, then check to make sure you have the Grafana Logs Drilldown plugin installed and configured.
Note
Your instance needs internet connection in order to download the Logs Drilldown plugin. If you are working in an offline environment, you can download the Logs Drilldown plugin separately and add it to your Grafana
/plugins
repository.
Ensure Loki is properly configured
To use Grafana Logs Drilldown, you need to have Loki properly configured. You can find full instructions on how to do this when installing Grafana Logs Drilldown.
There are no services
If everything is presented as an unknown_service
when you access Grafana Logs Drilldown, you can try the following fixes:
- Ensure the Volume API is enabled by setting the
volume_enabled
configuration value in Loki. Enabled by default in Loki 3.1 and later. - Specify the label to use to identify services by setting the
discover_service_name
configuration value in Loki.
There are no detected levels
If you do not see detected_level
values in Grafana Logs Drilldown, you can try the following fixes:
- Ensure level detection is enabled by setting the
discover_log_levels
configuration value. Enabled by default in Loki 3.1 and later.
There are no labels
If you do not see any labels in Grafana Logs Drilldown, you can try the following fixes:
- Ensure your collector is properly configured to attach them.
To learn more about Labels, refer to the Loki labels documentation.
There are no patterns
Patterns are ephemeral and will only be available for the previous three hours. And patterns can change over time as your logging evolves.
If you aren’t getting any patterns, you can try the following fixes:
- Ensure pattern extraction is enabled by setting
pattern-ingester.enabled=true
in your Loki config. Learn about other necessary config. - Ensure the volume endpoint is enabled by setting
volume_enabled=true
within your Loki configuration file. - It is possible that no patterns were detected, although this is rare - please open an issue on GitHub or get in touch privately so we can see what’s going on.
Note
The Patterns feature does not support multi-tenant or cross-stack datasources.
If you see a message in the UI on the Patterns tab that says “An error occurred within the plugin.” or receive an error message HTTP 500 with the message multiple org IDs present
you have two options to work around the issue:
- Use a single-stack Loki data source to restore Patterns.
- Disable log patterns to continue using the other Logs Drilldown features with your multi-tenant or cross-stack data source. Go to Administration > Plugins and data > Plugins > Grafana Logs Drilldown and select the Disable patterns check box. This will disable use of the Patterns API and hide the Patterns tab in the user interface.
There are no color levels
Color coding for log severity levels is a setting in Loki. You must have discover_log_levels: true
in your Loki configuration file.
Cannot filter in JSON panel
The new dedicated visualization for JSON logs is experimental and was introduced in Loki version 3.5. If you cannot filter on the JSON panel on the Logs tab:
- Ensure that you are on Loki version 3.5. Users running older versions of Loki can view JSON logs, but cannot filter in the JSON panel.
I cannot find something
Please open an issue on GitHub or get in touch privately and let us know what’s not working for you.
If you have something urgent, please get in touch via support. Grafana Cloud users can open a support ticket here.