2016-10-21 04:01:34 -05:00
|
|
|
+++
|
|
|
|
|
title = "Troubleshooting"
|
|
|
|
|
description = "Guide to troubleshooting Grafana problems"
|
|
|
|
|
keywords = ["grafana", "troubleshooting", "documentation", "guide"]
|
|
|
|
|
type = "docs"
|
|
|
|
|
[menu.docs]
|
|
|
|
|
parent = "admin"
|
|
|
|
|
weight = 8
|
|
|
|
|
+++
|
|
|
|
|
|
2015-03-10 02:55:42 -05:00
|
|
|
|
|
|
|
|
# Troubleshooting
|
|
|
|
|
|
2015-05-10 15:15:34 -05:00
|
|
|
This page is dedicated to helping you solve any problem you have getting
|
|
|
|
|
Grafana to work. Please review it before opening a new [GitHub
|
|
|
|
|
issue](https://github.com/grafana/grafana/issues/new) or asking a
|
|
|
|
|
question in the `#grafana` IRC channel on freenode.
|
2015-03-10 02:55:42 -05:00
|
|
|
|
|
|
|
|
## General connection issues
|
2015-05-10 15:15:34 -05:00
|
|
|
|
|
|
|
|
When setting up Grafana for the first time you might experience issues
|
|
|
|
|
with Grafana being unable to query Graphite, OpenTSDB or InfluxDB. You
|
|
|
|
|
might not be able to get metric name completion or the graph might show
|
|
|
|
|
an error like this:
|
2015-03-10 02:55:42 -05:00
|
|
|
|
2016-11-04 14:29:17 -05:00
|
|
|
|
2015-03-10 02:55:42 -05:00
|
|
|
|
2015-08-11 13:58:30 -05:00
|
|
|
For some types of errors, the `View details` link will show you error
|
|
|
|
|
details. For many types of HTTP connection errors, however, there is very
|
2015-05-10 15:15:34 -05:00
|
|
|
little information. The best way to troubleshoot these issues is use
|
|
|
|
|
the [Chrome developer tools](https://developer.chrome.com/devtools/index).
|
|
|
|
|
By pressing `F12` you can bring up the chrome dev tools.
|
2015-03-10 02:55:42 -05:00
|
|
|
|
2016-11-04 14:29:17 -05:00
|
|
|
|
2015-03-10 02:55:42 -05:00
|
|
|
|
2015-05-10 15:15:34 -05:00
|
|
|
There are two important tabs in the Chrome developer tools: `Network`
|
|
|
|
|
and `Console`. The `Console` tab will show you Javascript errors and
|
|
|
|
|
HTTP request errors. In the Network tab you will be able to identify the
|
|
|
|
|
request that failed and review request and response parameters. This
|
|
|
|
|
information will be of great help in finding the cause of the error.
|
|
|
|
|
|
|
|
|
|
If you are unable to solve the issue, even after reading the remainder
|
|
|
|
|
of this troubleshooting guide, you should open a [GitHub support
|
|
|
|
|
issue](https://github.com/grafana/grafana/issues). Before you do that
|
|
|
|
|
please search the existing closed or open issues. Also if you need to
|
|
|
|
|
create a support issue, screen shots and or text information about the
|
|
|
|
|
chrome console error, request and response information from the
|
|
|
|
|
`Network` tab in Chrome developer tools are of great help.
|
2015-03-10 02:55:42 -05:00
|
|
|
|
|
|
|
|
### Inspecting Grafana metric requests
|
2015-05-10 15:15:34 -05:00
|
|
|
|
2016-11-04 14:29:17 -05:00
|
|
|
|
2015-03-10 02:55:42 -05:00
|
|
|
|
2015-05-10 15:15:34 -05:00
|
|
|
After opening the Chrome developer tools for the first time the
|
|
|
|
|
`Network` tab is empty. You will need to refresh the page to get
|
|
|
|
|
requests to show. For some type of errors, especially CORS-related,
|
|
|
|
|
there might not be a response at all.
|
2015-03-10 02:55:42 -05:00
|
|
|
|
