Merge branch 'docs'

docs/mkdocs.yml

@@ -1,6 +1,6 @@
 site_name: Grafana-Zabbix Documentation
 site_description: Documentation for Grafana-Zabbix, Zabbix monitoring system plugin bundle for Grafana
-site_url: https://alexanderzobnin.github.io/grafana-zabbix
+site_url: https://alexanderzobnin.github.io/grafana-zabbix/
 repo_url: https://github.com/alexanderzobnin/grafana-zabbix/
 edit_uri: blob/docs/docs/sources/
 copyright: Copyright © 2015-2018, Alexander Zobnin

docs/sources/configuration/index.md

@@ -58,7 +58,7 @@ Direct DB Connection allows plugin to use existing SQL data source for querying
 database. This way usually faster than pulling data from Zabbix API, especially on the wide time ranges, and reduces
 amount of data transfered.
 
-Read [how to configure](/configuration/sql_datasource) SQL data source in Grafana.
+Read [how to configure](./sql_datasource) SQL data source in Grafana.
 
 - **Enable**: enable Direct DB Connection.
 - **SQL Data Source**: Select SQL Data Source for Zabbix database.

docs/sources/features.md

@@ -7,11 +7,11 @@ Grafana in couple with Grafana-Zabbix plugin allows to create great dashboards.
 features:
 
 - Rich graphing features
-- Create interactive and reusable dashboards with [template variables](/guides/templating/)
+- Create interactive and reusable dashboards with [template variables](../guides/templating/)
 - Show events on graphs with [Annotations](http://docs.grafana.org/reference/annotations/)
-- Select multiple metrics [by using Regex](/guides/gettingstarted/#multiple-items-on-one-graph)
+- Select multiple metrics [by using Regex](../guides/gettingstarted/#multiple-items-on-one-graph)
 - Display active problems with Triggers panel
-- Transform and shape your data with [metric processing functions](/reference/functions/) (Avg, Median, Min, Max, Multiply, Summarize, Time shift, Alias)
+- Transform and shape your data with [metric processing functions](../reference/functions/) (Avg, Median, Min, Max, Multiply, Summarize, Time shift, Alias)
-- Find problems faster with [Alerting](/reference/alerting/) feature
+- Find problems faster with [Alerting](../reference/alerting/) feature
 - Mix metrics from multiple data sources in the same dashboard or even graph
 - Discover and share [dashboards](https://grafana.com/dashboards) in the official library

docs/sources/index.md

@@ -17,7 +17,7 @@ this tool better.
 If you have any troubles with Grafana or you just want clarification on a feature, there are
 a number of ways to get help:
 
-- [Troubleshooting guide](/configuration/troubleshooting/)
+- [Troubleshooting guide](./configuration/troubleshooting/)
 - Search closed and open [issues on GitHub](https://github.com/grafana/grafana/issues)
 - [Grafana Community](https://community.grafana.com)
 - [Twitter](https://twitter.com/AlexanderZobnin)

docs/sources/installation/index.md

@@ -28,4 +28,4 @@ Read more about installing plugins in [Grafana docs](http://docs.grafana.org/plu
 
 ## Building from sources
 
-If you want to build a package yourself, or contribute - read [building instructions](/installation/run_from_master).
+If you want to build a package yourself, or contribute - read [building instructions](./run_from_master).

docs/sources/reference/direct-db-connection.md

@@ -4,7 +4,7 @@ Since version 4.3 Grafana can use MySQL as a native data source. The Grafana-Zab
 
 One of the most resource intensive queries for Zabbix API is the history query. For long time intervals `history.get`
 returns a huge amount of data. In order to display it, the plugin should adjust time series resolution
-by using [consolidateBy](/reference/functions/#consolidateby). Ultimately, Grafana displays this reduced
+by using [consolidateBy](../functions/#consolidateby). Ultimately, Grafana displays this reduced
 time series, but that data should be loaded and processed on the client side first. Direct DB Connection solves these two problems by moving consolidation to the server side. Thus, the client gets a 'ready-to-use' dataset which is much smaller. This allows the data to load faster and the client doesn't spend time processing the data.
 
 Also, many users see better performance from direct database queries versus API calls. This could be the result of several reasons,