mirror of
https://github.com/grafana/grafana.git
synced 2025-02-25 18:55:37 -06:00
doc(Logs): Add clarification note about full range histogram in Loki (#49143)
* doc(Logs): Add clarification note about full range histogram in Loki Signed-off-by: Kaviraj <kavirajkanagaraj@gmail.com> * Update logs-integration.md * Update docs/sources/explore/logs-integration.md Co-authored-by: Jennifer Villa <jvilla2013@gmail.com> * Fix linting Co-authored-by: Jennifer Villa <jvilla2013@gmail.com> Co-authored-by: Ivana Huckova <ivana.huckova@gmail.com>
This commit is contained in:
committed by
GitHub
parent
d2fefec306
commit
4b1c4f7240
@@ -29,6 +29,8 @@ Results of log queries are shown as histograms in the graph and individual logs
|
||||
|
||||
If the data source supports a full range log volume histogram, the graph with log distribution for all entered log queries is shown automatically. This feature is currently supported by Elasticsearch and Loki data sources.
|
||||
|
||||
**NOTE:** In Loki, this full range log volume histogram is rendered by metric query which can be expensive depending on time range queried. This query may be particularly challenging for smaller Loki installations to process. To mitigate this, we recommend using a proxy like [nginx](https://www.nginx.com/) in front of Loki to set a custom timeout (e.g. 10 seconds) for these queries. Log volume histogram queries can be identified by looking for queries with the HTTP header `X-Query-Tags` with value `Source=logvolhist`; these headers are added by Grafana to all log volume histogram queries.
|
||||
|
||||
If the data source does not support loading full range log volume histogram, the logs model computes a time series based on the log row counts bucketed by an automatically calculated time interval, and the first log row's timestamp then anchors the start of the histogram from the result. The end of the time series is anchored to the time picker's **To** range.
|
||||
|
||||
#### Log level
|
||||
|
||||
Reference in New Issue
Block a user