Grafana cli is a small executable that is bundled with grafana server and is suppose to be executed on the same machine as grafana runs.
Grafana cli is a small executable that is bundled with grafana server and is suppose to be
executed on the same machine as grafana runs.
## Plugins
## Plugins
The CLI helps you install, upgrade and manage your plugins on the same machine it CLI is running. You can find more information about how to install and manage your plugins at the [plugin page]({{<relref"/installation.md">}})
The CLI helps you install, upgrade and manage your plugins on the same machine it CLI is running.
You can find more information about how to install and manage your plugins at the
Grafana v2.1 brings initial support for KairosDB Datasources. While the process of adding the datasource is similar to adding a Graphite or OpenTSDB datasource type, Kairos DB does have a few different options for building queries.
## Adding the data source to Grafana
1. Open the side menu by clicking the the Grafana icon in the top header.
2. In the side menu under the `Dashboards` link you should find a link named `Data Sources`.
> NOTE: If this link is missing in the side menu it means that your current user does not have the `Admin` role for the current organization.
3. Click the `Add new` link in the top header.
4. Select `KairosDB` from the dropdown.
Name | Description
------------ | -------------
Name | The data source name, important that this is the same as in Grafana v1.x if you plan to import old dashboards.
Default | Default data source means that it will be pre-selected for new panels.
Url | The http protocol, ip and port of your kairosdb server (default port is usually 8080)
Access | Proxy = access via Grafana backend, Direct = access directly from browser.
## Query editor
Open a graph in edit mode by click the title.
For details on KairosDB metric queries checkout the official.
KairosDB Datasource Plugin provides following functions in `Variables values query` field in Templating Editor to query `metric names`, `tag names`, and `tag values` to kairosdb server.
Name | Description
| ------- | --------|
`metrics(query)` | Returns a list of metric names matching `query`. If nothing is given, returns a list of all metric names.
`tag_names(query)` | Returns a list of tag names matching `query`. If nothing is given, returns a list of all tag names.
`tag_values(metric,tag)` | Returns a list of values for `tag` from the given `metric`.
For details of `metric names`, `tag names`, and `tag values`, please refer to the KairosDB documentations.
@@ -3,6 +3,7 @@ title = "Using Prometheus in Grafana"
...
@@ -3,6 +3,7 @@ title = "Using Prometheus in Grafana"
description = "Guide for using Prometheus in Grafana"
description = "Guide for using Prometheus in Grafana"
keywords = ["grafana", "prometheus", "guide"]
keywords = ["grafana", "prometheus", "guide"]
type = "docs"
type = "docs"
aliases = ["/datasources/prometheus"]
[menu.docs]
[menu.docs]
name = "Prometheus"
name = "Prometheus"
parent = "datasources"
parent = "datasources"
...
@@ -74,7 +75,7 @@ You can also use raw queries & regular expressions to extract anything you might
...
@@ -74,7 +75,7 @@ You can also use raw queries & regular expressions to extract anything you might
### Using templated variables in queries
### Using templated variables in queries
When the `Include All` option or `Multi-Value` option is enabled, Grafana converts the labels from plain text to a regex compatible string.
When the `Include All` option or `Multi-Value` option is enabled, Grafana converts the labels from plain text to a regex compatible string.
Which means you have to use `=~` instead of `=` in your Prometheus queries. For example `ALERTS{instance=~$instance}` instead of `ALERTS{instance=$instance}`.
Which means you have to use `=~` instead of `=` in your Prometheus queries. For example `ALERTS{instance=~$instance}` instead of `ALERTS{instance=$instance}`.
The purpose of this data sources is to make it easier to create fake data for any panel.
The purpose of this data sources is to make it easier to create fake data for any panel.
Using `Grafana TestData` you can build your own time series and have any panel render it.
Using `Grafana TestData` you can build your own time series and have any panel render it.
This make is much easier to verify functionally since the data can be shared very
This make is much easier to verify functionally since the data can be shared very
## Enable
## Enable
`Grafana TestData` is not enabled by default. To enable it you have to go to `/plugins/testdata/edit` and click the enable button to enable it for each server.
`Grafana TestData` is not enabled by default. To enable it you have to go to `/plugins/testdata/edit` and click the enable button to enable it for each server.
...
@@ -33,8 +33,8 @@ You can now choose different scenario that you want rendered in the drop down me
...
@@ -33,8 +33,8 @@ You can now choose different scenario that you want rendered in the drop down me
## CSV
## CSV
The comma separated values scenario is the most powerful one since it lets you create any kind of graph you like.
The comma separated values scenario is the most powerful one since it lets you create any kind of graph you like.
Once you provided the numbers `Grafana TestData` will distribute them evenly based on the time range of your query.
Once you provided the numbers `Grafana TestData` will distribute them evenly based on the time range of your query.
...
@@ -45,10 +45,10 @@ Once you provided the numbers `Grafana TestData` will distribute them evenly bas
...
@@ -45,10 +45,10 @@ Once you provided the numbers `Grafana TestData` will distribute them evenly bas
### Commit updates to the dashboards
### Commit updates to the dashboards
If you want to submit a change to one of the current dashboards bundled with `Grafana TestData` you have to update the revision property.
If you want to submit a change to one of the current dashboards bundled with `Grafana TestData` you have to update the revision property.
Otherwise the dashboard will not be updated automatically for other Grafana users.
Otherwise the dashboard will not be updated automatically for other Grafana users.
## Using test data in issues
## Using test data in issues
If you post an issue on github regarding time series data or rendering of time series data we strongly advice you to use this data source to replicate the data.
If you post an issue on github regarding time series data or rendering of time series data we strongly advice you to use this data source to replicate the data.
That makes it much easier for the developers to replicate and solve the issue you have.
That makes it much easier for the developers to replicate and solve the issue you have.
@@ -16,7 +16,7 @@ This document is a “bottom up” introduction to basic concepts in Grafana, an
...
@@ -16,7 +16,7 @@ This document is a “bottom up” introduction to basic concepts in Grafana, an
### Data Source
### Data Source
Grafana supports many different storage backends for your time series data (Data Source). Each Data Source has a specific Query Editor that is customized for the features and capabilities that the particular Data Source exposes.
Grafana supports many different storage backends for your time series data (Data Source). Each Data Source has a specific Query Editor that is customized for the features and capabilities that the particular Data Source exposes.
The following datasources are officially supported: [Graphite](/datasources/graphite/), [InfluxDB](/datasources/influxdb/), [OpenTSDB](/datasources/opentsdb/), [Prometheus](/datasources/prometheus/), [Elasticsearch](/datasources/elasticsearch/), [CloudWatch](/datasources/cloudwatch/), and [KairosDB](/datasources/kairosdb)
The following datasources are officially supported: [Graphite]({{<relref"features/datasources/graphite.md">}}), [InfluxDB]({{<relref"features/datasources/influxdb.md">}}), [OpenTSDB]({{<relref"features/datasources/opentsdb.md">}}), [Prometheus]({{<relref"features/datasources/prometheus.md">}}), [Elasticsearch]({{<relref"features/datasources/elasticsearch.md">}}), [CloudWatch]({{<relref"features/datasources/cloudwatch.md">}}).
The query language and capabilities of each Data Source are obviously very different. You can combine data from multiple Data Sources onto a single Dashboard, but each Panel is tied to a specific Data Source that belongs to a particular Organization.
The query language and capabilities of each Data Source are obviously very different. You can combine data from multiple Data Sources onto a single Dashboard, but each Panel is tied to a specific Data Source that belongs to a particular Organization.
