opensource/grafana
1
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-07-29 21:32:28 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs(): fixing image urls in docs

Browse Source
This commit is contained in:
Torkel Ödegaard
2016-11-04 20:29:17 +01:00
parent 3cc4a194a9
commit 2b81b204aa
31 changed files with 141 additions and 153 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/sources/installation/migrating_to2.md
View File

@ -61,7 +61,7 @@ sure your Elasticsearch data source is added. Specify the Elasticsearch
index name where your existing Grafana v1.x dashboards are stored
(the default is `grafana-dash`).
![](img/docs/v2/datasource_edit_elastic.jpg)
![](/img/docs/v2/datasource_edit_elastic.jpg)
### Importing dashboards from InfluxDB
@ -74,7 +74,7 @@ your Grafana v1.x dashboards are stored, the default is `grafana`.
Go to the `Dashboards` view and click on the dashboards search drop
down. Click the `Import` button at the bottom of the search drop down.
![](img/docs/v2/dashboard_import.jpg)
![](/img/docs/v2/dashboard_import.jpg)
### Import view
@ -82,7 +82,7 @@ In the Import view you find the section `Migrate dashboards`. Pick the
data source you added (from Elasticsearch or InfluxDB), and click the
`Import` button.
![](img/docs/v2/migrate_dashboards.jpg)
![](/img/docs/v2/migrate_dashboards.jpg)
Your dashboards should be automatically imported into the Grafana 2.0
back-end.

6
docs/sources/installation/troubleshooting.md
View File

@ -23,7 +23,7 @@ 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:
![](img/docs/v1/graph_timestore_error.png)
![](/img/docs/v1/graph_timestore_error.png)
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
@ -31,7 +31,7 @@ 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.
![](img/docs/v1/toubleshooting_chrome_dev_tools.png)
![](/img/docs/v1/toubleshooting_chrome_dev_tools.png)
There are two important tabs in the Chrome developer tools: `Network`
and `Console`. The `Console` tab will show you Javascript errors and
@ -49,7 +49,7 @@ chrome console error, request and response information from the
### Inspecting Grafana metric requests
![](img/docs/v1/toubleshooting_chrome_dev_tools_network.png)
![](/img/docs/v1/toubleshooting_chrome_dev_tools_network.png)
After opening the Chrome developer tools for the first time the
`Network` tab is empty. You will need to refresh the page to get