mirror of
https://github.com/grafana/grafana.git
synced 2025-07-30 03:42:08 +08:00
c1c48dd610
* Use relative aliases for all non-current Grafana aliases
Prevents non-latest documentation "stealing" the page away from latest
and through permanent redirects for latest pages that no longer exist.
The redirected pages are indexed by search engines but our robots.txt
forbids them crawling the non-latest page.
Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
* Remove aliases from shared pages
Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
* Rewrite all current latest aliases to be next
Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
* Fix typo in latest alias
Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
* Remove all current page aliases
find docs/sources -type f -name '*.md' -exec sed -z -i 's#\n *- /docs/grafana/next/[^\n]*\n#\n#' {} \;
find docs/sources -type f -name '*.md' -exec sed -Ez -i 's#\n((aliases:\n *-)|aliases:\n)#\n\2#' {} \;
Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
* Prettier
Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
38 lines
1.3 KiB
Markdown
38 lines
1.3 KiB
Markdown
---
|
|
aliases:
|
|
- ../../troubleshooting/troubleshoot-queries/
|
|
description: Guide to troubleshooting Grafana queries
|
|
keywords:
|
|
- grafana
|
|
- troubleshooting
|
|
- documentation
|
|
- guide
|
|
- queries
|
|
title: Troubleshoot queries
|
|
weight: 200
|
|
---
|
|
|
|
# Troubleshoot queries
|
|
|
|
This page provides information to solve common dashboard problems.
|
|
|
|
## I get different results when I rearrange my functions
|
|
|
|
Function order is very important. Just like in math, the order that you place your functions can affect the result.
|
|
|
|
## Inspect your query request and response
|
|
|
|
The most common problems are related to the query and response from your data source. Even if it looks
|
|
like a bug or visualization issue in Grafana, it is almost always a problem with the data source query or
|
|
the data source response. Start by inspecting your panel query and response.
|
|
|
|
For more information, refer to [Inspect request and response data]({{< relref "../../panel-inspector/#inspect-query-request-and-response data/" >}}).
|
|
|
|
## My query is slow
|
|
|
|
How many data points is your query returning? A query that returns lots of data points will be slow. Try this:
|
|
|
|
- In **Query options**, limit the **Max data points** returned.
|
|
- In **Query options**, increase the **Min interval** time.
|
|
- In your query, use a `group by` function.
|