The tool for beautiful monitoring and metric analytics & dashboards for Graphite, InfluxDB & Prometheus & More

The open-source platform for monitoring and observability. Grafana allows you to query, visualize, alert on and understand your metrics no matter where they are stored. Create, explore, and share dashboards with your team and foster

Information

Category: Golang / Data Visualization
Watchers: 1.3k
Star: 53.6k
Fork: 10.4k
Last update: Jan 23, 2023

Resource links

https://github.com/grafana/grafana

Popular

The open-source platform for monitoring and observability.

Grafana allows you to query, visualize, alert on and understand your metrics no matter where they are stored. Create, explore, and share dashboards with your team and foster a data driven culture:

Visualize: Fast and flexible client side graphs with a multitude of options. Panel plugins for many different way to visualize metrics and logs.
Dynamic Dashboards: Create dynamic & reusable dashboards with template variables that appear as dropdowns at the top of the dashboard.
Explore Metrics: Explore your data through ad-hoc queries and dynamic drilldown. Split view and compare different time ranges, queries and data sources side by side.
Explore Logs: Experience the magic of switching from metrics to logs with preserved label filters. Quickly search through all your logs or streaming them live.
Alerting: Visually define alert rules for your most important metrics. Grafana will continuously evaluate and send notifications to systems like Slack, PagerDuty, VictorOps, OpsGenie.
Mixed Data Sources: Mix different data sources in the same graph! You can specify a data source on a per-query basis. This works for even custom datasources.

Grafana 7.0 and GrafanaCONline

Grafana 7.0 Beta is available for download.
Read what's is new.

Want to learn more about Grafana 7 and more? Sign up for our online conference!

Get started

Unsure if Grafana is for you? Watch Grafana in action on play.grafana.org!

Documentation

The Grafana documentation is available at grafana.com/docs.

Contributing

If you're interested in contributing to the Grafana project:

Start by reading the Contributing guide.
Learn how to set up your local environment, in our Developer guide.
Explore our beginner-friendly issues.

Get involved

Follow @grafana on Twitter
Read and subscribe to the Grafana blog
If you have a specific question, check out our discussion forums.
For general discussions, join us on the official Slack team.

License

Grafana is distributed under the Apache 2.0 License.

2956 Open More issues

Closed

Internationalisation

Hi,

how can we add a translation (language file) of the GUI? There is not a lot in English but our customer prefers German language.

If someone explains how to translate I will make the translation to German. Maybe other users will contribute other languages.

Thank you MarkusR

type/feature-request area/ux

opened May 27, 2014 by markusr 297

Closed

building alerting system for grafana

Hi everyone, I recently joined raintank and I will be working with @torkelo, @mattttt , and you, on alerting support for Grafana.

From the results of the Grafana User Survey it is obvious that alerting is the most commonly missed feature for Grafana. I have worked on/with a few alerting systems in the past (nagios, bosun, graph-explorer, etsy's kale stack, ...) and I'm excited about the opportunity in front of us: we can take the best of said systems, but combine them with Grafana's focus on a polished user experience, resulting in a powerful alerting system, well-integrated and smooth to work with.

First of all, terminology sync:

alerting: executing logic (threshold checks or more advanced) to know the state of an entity. (ok, warning, critical)
notifications: emails, text messages, posts to chat, etc to make people aware of a state change
monitoring: this term covers everything about monitoring (data collection, visualizations, alerting) so I won't be using it here.

I want to spec out requirements, possible implementation ideas and their pro's/cons. With your feedback, we can adjust, refine and choose a specific direction.

General thoughts:

integration with existing tools vs built-in: there's some powerfull alerting systems out there (bosun, kale) that deserve integration. Many alerting systems are more basic (define expression/threshold, get notification when breached), for those it seems integration is not worth the pain (though I won't stop you)
The integrations are a long term effort. I think the low hanging fruit ("meet 80% of the needs with 20% of the effort") can be met with a system that is more closely tied to Grafana, i.e. compiled into the grafana binary. That said, a lot of people confuse seperation of concerns with "must be different services". If the code is sane, it'll be decoupled packages but there's nothing necessarily wrong with compiling them together. i.e. you could run:
- 1 grafana binary that does everything (grafana as you know it + all alerting features) for simplicity
- multiple grafana binaries in different modes (visualization instances and alerting instances) even highly available/redundant setups if you want to, using an external worker queue

That said, we don't want to reinvent the wheel: we want alerting code and functionality to integrate well with Grafana, but if high-quality code is compatible, we should use it. In fact, I have a prototype that leverages some existing bosun code. (see "Current state")

polling vs stream processing: they have different performance characteristics, but they should be able to take the same or similar alerting rule definitions (thresholds, boolean logic, ..), they mostly are about how the actual rules are executed and don't change much about how rules are defined. Since polling is much simpler and should be able to scale fairly far this should IMHO be our initial focus.

Current state

The raintank/grafana version currently has an alerting package with a simple scheduler, an in-process worker bus as well as rabbitmq based, an alert executor and email notifications. It uses the bosun expression libraries which gives us the ability to evaluate arbitrarily complex expressions (use several metrics, use boolean logic, math, etc). This package is currently raintank-specific but we will merge a generic version of this into upstream grafana. This will provide an alert execution platform but notably still missing is

an interface to create and manage alerting rules
state management (acknowledgements etc)

these are harder problems, which I hope to tackle with your input.

Requirements, Future implementations

First off, I think bosun is a pretty fantastic system for alerting (not so much for visualization) You can make your alerting rules as advanced as you want, and it enables you to fine-tune over time, backtest on historical data, so you can get them just right. And it has a good state machine. In theory we could just compile bosun straight into grafana, and leverage bosun via its REST api instead of Golang api, but then we have less finegrained control and for now I feel more comfortable trying out piece by piece (piece meaning golang package) and make the integration decision on a case by case basis. Though the integration may look different down the road based on experience and as we figure out what we want our alerting to look like.

Either way, we don't just want great alerting. We want great alerting combined with great visualizations, notifications with context, and a smooth workflow where you can manage your alerts in the same place you manage your visualizations. So it needs to be nicely integrated into Grafana. To that end, there's a few things to consider:

some visualized metrics (metrics plotted on graphs) are not alerted on
some visualized metrics are alerted on:
- A: with simple threshold checks: easy to visualize alerting logic
- B: with more advanced logic: (e.g. look at standard deviation of the series being plotted, compare current median against historical median, etc): can't easily be visualized nex to the input series
some metrics used in alerting logic are not to be vizualized

Basically, there's a bunch of stuff you may want visualized (V), and a bunch of stuff you want alerts (A), and V and A have some overlap. I need to think about this a bit more and wonder what y'all think. There will definitely need to be 1 central place where you can get an overview of all the things you're alerting on, irrespective of where those rules are defined.

There's a few more complications which I'll explain through an example sketch of how alerting could look like:

let's say we have a timeseries for requests (A) and one for errorous requests (B) and this is what we want to plot. we then use fields C,D,E to put stuff that we don't want to alert on. C contains the formula for ratio of error requests against the total.

we may for example want to alert (see E) if the median of this ratio in the last 5min ago is more than 1.5 of what the ratio was in the same 5minute period last week, and also if the errors seen in the last 5min is worse than the errors seen since 2 months ago until 5min ago.

notes:

some queries use different timeranges than what is rendered
in addition to processing by tsdb (such as Graphite's sum(), divide() etc which return series) we need to be able to reduce series to single numbers. fairly easy to implement (and in fact currently the bosun library does this for us)
we need boolean logic (bosun also gives us this)
in this example the expression only uses variables defined within the same panel, but it might make sense to include expressions of other panels/graphs.

other ponderings:

do we integrate with current grafana graph threshold settings (which are currently for viz only, not for processing) ? if the expression is a threshold check, we could automatically display a threshold line
using the letters is a bit clunky, could we refer to the aliases instead? like #requests and #errors?
if the expression are stats.$site.requests and stats.$site.errors, and we want to have seperate alert instances for every site (but only set up the rule once)? what if we only want it for a select few of the sites. what if we want different parameters based on which site? bosun actually supports all these features, and we could expose them though we should probably build a UI around them.

I think for an initial implementation every graph could have two fields, like so:

warn: - expression
         - notification settings (email,http hook, ..)
crit: - expression
        -notification settings

where the expression is something like what I put in E in the sketch. for logic/data that we don't want to visualize, we just toggle off the visibility icon. grafana would replace the variables in the formula's, execute the expression (with the current bosun based executor). results (state changes) could be fed into something like elasticsearch and displayed via the annotations system.

Thoughts? Do you have concerns or needs that I didn't addres?

area/alerting

opened Jun 22, 2015 by Dieterbe 294

Closed

[Feature request] Add Alert support for singlestats

Please include this information:

What Grafana version are you using? v4.0.2 (commit: v4.0.2)
What datasource are you using? Graphite
What OS are you running grafana on? Mac OS
What did you do? Went to a dashboard, clicked on a single stat and expected to find the "Alert" tab.
What was the expected result? I was expecting to see the "Alert" tab
What happened instead? The "Alert" tab was not present for the Singlestat. It is present for Graph though.

If it relates to alerting

An image of the test execution data fully expanded.

type/feature-request area/alerting

opened Dec 15, 2016 by costimuraru 215

Closed

Grafana 2.0: SQL Data source

With the backend comes the possibility to have SQL data source.

My thinking is that when you add the data source you

db type (initially only mysql and postgres and sqlite3)
db connection details
specify a metric query template (basically a SQL query with params)
specify a annotation query template

Maybe also an option to allow RAW SQL queries from the panel metric query interface.

Any other ideas?

type/feature-request

opened Feb 28, 2015 by torkelo 168

Closed

[Feature request] Multiple alerts per graph

As per http://docs.grafana.org/alerting/rules/, Grafana plans to track state per series in future releases.

"If a query returns multiple series then the aggregation function and threshold check will be evaluated for each series. What Grafana does not do currently is track alert rule state per series." and
"To improve support for queries that return multiple series we plan to track state per series in a future release"

But it seems like there can be use cases where we have graphs containing set of metrics for which different sets of alerts are required. This is slightly different from "Support per series state change" ( https://github.com/grafana/grafana/issues/6041 ) because

The action (notifications) can be different.
Also, tracking separate states of an alert is not always preferred (as the end-user would need to know the details behind the individual states ) vs just knowing if alert is triggered.

Grafana version = 4.x

type/feature-request area/alerting

opened Mar 14, 2017 by sanchitraizada 149

Closed

Alerting support for queries using template variables

It would be pretty useful if grafana would support alerting for queries using template variables. The way I see it work it would be as follows:

Generate queries foreach template variable combination (discarding template variable for all)
When generating queries, consider the frozen list if the template variable is set to never refresh, else update the template variable list
Allow filtering (trough regex or by providing a static value) for each template variable

The current workaround is to use an invisible wildcard metric, but the problem I see with this approach is that it loses context.

type/feature-request area/alerting area/alerting/evaluation

opened Nov 12, 2016 by calind 141

Open

Chore: Fix goimports grouping

This PR deprecates https://github.com/grafana/grafana/pull/60870 and fixes goimports ordering in Multitenancy packages

area/backend no-backport enterprise-ok no-changelog

opened Jan 28, 2023 by zserge 0

Open

Chore: Fix goimports grouping

This PR deprecates https://github.com/grafana/grafana/pull/60870 and fixes goimports ordering in Observability Logs packages

datasource/Elasticsearch area/backend datasource/Loki enterprise-ok

opened Jan 28, 2023 by zserge 2

Open

Chore: Fix goimports grouping

This PR deprecates https://github.com/grafana/grafana/pull/60870 and fixes goimports ordering in Observability Metrics packages

datasource/Graphite datasource/Prometheus area/backend no-backport enterprise-ok no-changelog

opened Jan 28, 2023 by zserge 0

Open

Chore: Fix goimports grouping

This PR deprecates https://github.com/grafana/grafana/pull/60870 and fixes goimports ordering in AuthNZ packages

area/backend no-backport enterprise-ok no-changelog

opened Jan 28, 2023 by zserge 0

Open

Chore: Fix goimports grouping

This PR deprecates https://github.com/grafana/grafana/pull/60870 and fixes goimports ordering in plugins platform packages

area/backend no-backport no-changelog enterprise-failed

opened Jan 28, 2023 by zserge 0

Open

Chore: Fix goimports grouping

This PR deprecates https://github.com/grafana/grafana/pull/60870 and fixes goimports ordering in alerting packages

area/backend area/backend/db/migration no-backport enterprise-ok no-changelog

opened Jan 28, 2023 by zserge 0

influxdb-rs — asynchronous interface

Linux performance monitoring system

Metric learning algorithms in Python

📊 Prometheus Provider for Adonis 5 with some builtins metrics for monitoring your application.

M3 monorepo - Distributed TSDB, Aggregator and Query Engine, Prometheus Sidecar, Graphite Compatible, Metrics Platform

Scalable datastore for metrics, events, and real-time analytics

The Prometheus monitoring system and time series database.

Export Django monitoring metrics for Prometheus.io

API Scraper for pulling Vehicle Statistics from the Tesla Owner API into an InfluxDB + Grafana Dashboards

A tool to run periodic speedtests and save them in InfluxDB for graphing in Grafana

GOM：New Metric for Re-identification. 👉GOM explicitly balances the effect of performing retrieval and verification into a single unified metric.

Metric learning algorithms in Python

User-friendly Go library for building Grafana dashboards

Standalone application to aggregate data from the Plex ecosystem into InfluxDB using Grafana for a frontend

influxdb - InfluxDB Driver for Rust

Smarthome Dashboard with Grafana & InfluxDB

Encrypted, secure, user-owned productivity suite

Graphite UI replacement for Sketch.app

Graphite cursors theme for linux desktops

Graphite kde theme

Share this repo

Related Repos

Data Visualization

Reconstruct Open API Specifications from real-time workload traffic seamlessly.

APIClarity Reconstruct OpenAPI Specifications from real-time workload traffic seamlessly. Microservices API challenges Not all applications have an Op

Data Visualization

121

PlotNG - plotting utility for Chia.Net

This utility consisted of server backend and UI which manages the chia plot creation.

Data Visualization

Create diagrams from the Kubernetes API with go-diagrams.

Data Visualization

mtail, prometheus, and grafana config and dashboard for monitoring chia farming

ChiaMon Example using mtail to collect metrics from Chia logs, with docker-compose stack to collect data with Prometheus and graph in Grafana. mtail p

Data Visualization

Create changelogs for Helm Charts, based on git history

Data Visualization

Find out where you fall on the Open-Source Character Alignment Chart

Data Visualization

yml2dot - Turn YAML into beautiful Graph

Data Visualization

196

🚀 Statsview is a real-time Golang runtime stats visualization profiler

Statsview is a real-time Golang runtime stats visualization profiler. It is built top on another open-source project, go-echarts, which helps statsview to show its graphs on the browser.

Data Visualization

Physarum polycephalum slime mold simulation

This is a particle-based simulation inspired by the Physarum polycephalum slime mold.

Data Visualization

OKR | Objectives & Key Results with MindMapping

okr-mindmapping My personal OKR (Objectives & Key Results) on prespective mindmapping Prerequisites Mindmapping Tools using FreeMind Copyright Author:

Data Visualization

3.4k

Generate HTTP load and plot the results in real-time

Another load testing tool, inspired by vegeta and jplot.

Data Visualization

Create beautiful system diagrams with Go

Data Visualization

Converts 'go mod graph' output into Graphviz's DOT language

Data Visualization

2.4k

Skydive is an open source real-time network topology and protocols analyzer.

Skydive is an open source real-time network topology and protocols analyzer. It aims to provide a comprehensive way of understanding what is happening in the network infrastructure.

Data Visualization

370

Calendar heatmap in plain Go inspired by Github contribution activity