Using Graphite in Grafana

    • Open the side menu by clicking the Grafana icon in the top header.
    • In the side menu under the link you should find a link named Data Sources.
    • Click the + Add data source button in the top header.
    • Select Graphite from the Type dropdown.

    Access mode controls how requests to the data source will be handled. Server should be the preferred way if nothing else stated.

    All requests will be made from the browser to Grafana backend/server which in turn will forward the requests to the data source and by that circumvent possible Cross-Origin Resource Sharing (CORS) requirements. The URL needs to be accessible from the grafana backend/server if you select this access mode.

    Browser access mode

    All requests will be made from the browser directly to the data source and may be subject to Cross-Origin Resource Sharing (CORS) requirements. The URL needs to be accessible from the browser if you select this access mode.

    Metric editor

    Navigate metric segments

    Click the Select metric link to start navigating the metric space. One you start you can continue using the mouse or keyboard arrow keys. You can select a wildcard and still continue.

    [Graphite - 图2

    ]()

    Click the plus icon to the right to add a function. You can search for the function or select it from the menu. Once a function is selected it will be added and your focus will be in the text box of the first parameter. To later change a parameter just click on it and it will turn into a text box. To delete a function click the function name followed by the x icon.

    [Graphite - 图4

    ](https://grafana.com/docs/img/docs/v45/graphite_query2.gif)

    Optional parameters

    [Graphite - 图6

    ](https://grafana.com/docs/img/docs/v45/graphite_query3.gif)

    Nested Queries

    You can reference queries by the row “letter” that they’re on (similar to Microsoft Excel). If you add a second query to a graph, you can reference the first query simply by typing in #A. This provides an easy and convenient way to build compounded queries.

    [Graphite - 图8

    ](https://grafana.com/docs/img/docs/v45/graphite_nested_queries.gif)

    All Graphite metrics are consolidated so that Graphite doesn’t return more data points than there are pixels in the graph. By default, this consolidation is done using avg function. You can control how Graphite consolidates metrics by adding the Graphite consolidateBy function.

    Notice This means that legend summary values (max, min, total) cannot be all correct at the same time. They are calculated client side by Grafana. And depending on your consolidation function only one or two can be correct at the same time.

    Templating

    Instead of hard-coding things like server, application and sensor name in you metric queries you can use variables in their place. Variables are shown as dropdown select boxes at the top of the dashboard. These dropdowns makes it easy to change the data being displayed in your dashboard.

    Checkout the Templating documentation for an introduction to the templating feature and the different types of template variables.

    Graphite 1.1 introduced tags and Grafana added support for Graphite queries with tags in version 5.0. To create a variable using tag values, then you need to use the Grafana functions tags and .

    QueryDescription
    tags()Returns all tags.
    tags(server=~backend*)Returns only tags that occur in series matching the filter expression.
    tag_values(server)Return tag values for the specified tag.
    tag_values(server, server=~backend*)Returns filtered tag values that occur for the specified tag in series matching those expressions.
    tag_values(server, server=~backend*, app=~${apps:regex})Multiple filter expressions and expressions can contain other variables.

    The query you specify in the query field should be a metric find type of query. For example, a query like prod.servers.* will fill the variable with all possible values that exist in the wildcard position.

    You can also create nested variables that use other variables in their definition. For example apps.$app.servers.* uses the variable $app in its query definition.

    Variable Usage

    You can use a variable in a metric node path or as a parameter to a function.

    There are two syntaxes:

    • [[varname]] Example: apps.frontend.[[server]].requests.countWhy two ways? The first syntax is easier to read and write but does not allow you to use a variable in the middle of a word. Use the second syntax in expressions like my.server[[serverNumber]].count.

    Example: Graphite Templated Dashboard

    Variable Usage in Tag Queries

    Multi-value variables in tag queries use the advanced formatting syntax introduced in Grafana 5.0 for variables: {var:regex}. Non-tag queries will use the default glob formatting for multi-value variables.

    Example of a tag expression with regex formatting and using the Equal Tilde operator, =~:

    Checkout the Advanced Formatting Options section in the Variables documentation for examples and details.

    allows you to overlay rich event information on top of graphs. You add annotation queries via the Dashboard menu / Annotations view.

    Graphite supports two ways to query annotations. A regular metric query, for this you use the textbox. A Graphite events query, use the Graphite event tags textbox, specify a tag or wildcard (leave empty should also work)

    Configure the Datasource with Provisioning

    Here are some provisioning examples for this datasource.

    1. apiVersion: 1
    2. datasources:
    3. - name: Graphite
    4. type: graphite
    5. access: proxy
    6. url: http://localhost:8080