Home / Golang / Data Visualization

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
Popular

Grafana

The open-source platform for monitoring and observability.

License Circle CI Go Report Card

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

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

GrafanaCONline

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:

Get involved

License

Grafana is distributed under the Apache 2.0 License.

2511 Open More issues
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

  1. an interface to create and manage alerting rules
  2. 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:

  1. some visualized metrics (metrics plotted on graphs) are not alerted on
  2. 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
  3. 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: sketch

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

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

Localize time_format in graphs

Hello dear developers team. Thank you for a awesome product, but I have one problem.

Now there is a hadcoded US date format in time_format function. The most annoying case is display month and day. When I see something like "2/3" I'm a bit confused. Is it "the second of Mart" or "the third of February"? The most sad thing, that I can't to configure this behaviour.

Unfortunately the simplest way (and may be the most proper) doesn't help here. I mean toLocaleString with additional options. You can return different array of options instead of hardcoded format pattern and this method convert date in accordance with a right locale. But in our case there is a jquery plot and it requires date format for converting timestamp by itself.

So, the second way is make some kind of mapping locale -> format array. Example. It seems a bit ugly. But it could be a single working solution.

May be I missed some obvious and better solutions. That's why I didn't create a pull request. =)

area/panel/graph type/feature-request 
opened Feb 10, 2015 by Alarmfifa 140
Closed

Elasticsearch as timeseries datasource

I'm aware of #158, but in this issue I want to discuss whether Elasticsearch is a good fit for storing timeseries data and whether grafana's graph panel should support fetching timeseris data from elasticsearch. I'm not suggesting that grafana should also implement features like log analytics.

Elasticsearch offers the date_histogram aggregation that could be used to feed the graphs. When comparing the available aggregations elasticsearch has to offer to InfluxDB's aggregate functions, you can see, that they are quite simmilar.

One could argue, that if InfluxDB already offers this features, why add 'yad' (yet another datasource)? Even though it looks like InfluxDB's development is moving fast, I think that elasticsearch is a more mature, easier to scale scaleable, and easier to install and operate. Also, because it's based on Java it just runs anywhere, even Windows and Solaris for example.

Besides, a lot of people already use elasticsearch to store the dashboards and add annotations to the graphs. If elasticsearch could also be used as a timeseries datasource, you would just have to install one database which again reduces time and cost to install and operate the system.

Because you would store metrics in a json format, the ideas described in metric 2.0 could be incorporated.

A metric document could look something like this:

{
    "@timestamp" : "2013-07-20T09:43:58.000+0000",
    "name" : "bulk-request-timer",
    "tags" : {
        "application"  : "my awesome app",
        "host"  : "host-1",
        "datacenter"  : "dc1"
    },
    "values" : {
        "count" : 114,
        "max" : 109.681,
        "mean" : 5.439666666666667,
        "min" : 2.457,
        "p50" : 4.3389999999999995,
        "p75" : 5.0169999999999995,
        "p95" : 8.37175,
        "p98" : 9.6832,
        "p99" : 94.68429999999942,
        "p999" : 109.681,
        "stddev" : 9.956913151098842,
        "m15_rate" : 0.10779994503690074,
        "m1_rate" : 0.07283351433589833,
        "m5_rate" : 0.10101298115113727,
        "mean_rate" : 0.08251056571678642
    }
}

Finally, I think that these features should rather be added to grafana than to kibana. IMHO kibana's focus just isn't displaying metrics but analytics. For example, it is not possible to add multiple graphs to one panel. For instance, if you wanted to display multiple percentiles of the response time in one panel, that's just not possible. Also there is no such functionality like grafana's templated queries. That could be implemented in grafana by performing a terms aggregation e.g. on the host field to populate the dropdown with all available hosts.

I think @Dieterbe already experimented using elasticsearch as a timeseries database for his graphite-ng project. What are your experiences and thoughts about my thoughts? @torkelo what do you think about all of that?

opened Nov 9, 2014 by felixbarny 133
Closed

Feature Request (Grafana 2.0): LDAP / Active Directory authentication and import groups

I need to authenticate user against an Active Directory Backend.

We need also import all "memberOf" groups as main groups to organize dashboards.

Could be possible that every user can see / edit (depending on the group permissions ) the dashboards contained on the groups where he belongs ?

area/backend/auth 
opened Feb 10, 2015 by toni-moreno 132
Closed

Support for multiple organizations

Update: Thank you for your feedback on this, we've decided to keep multi org support. Refer to the closing comment on this issue for more information.

Organizations (orgs) were originally created to support a multi-tenancy hosting service. Meaning, to use a single Grafana server to provide a fully isolated Grafana experience to multiple companies.

But mainly used orgs to help split a large installation up and create some separation between users & teams within a single company. In Grafana v5 we added teams & dashboard permissions to help manage a large single organization within Grafana so that use case is no longer recommended.

Multi-org support is currently a big usability problem, especially around user management. Removing multi-org support would make Grafana a lot easier to manage and setup for single org setups. But we realize this could be very disruptive and want to gather all feedback on use cases first.

Whatever we decide, we plan to have some migration story ready when we remove multi-org support.

opened May 12, 2020 by torkelo 127
Open

[v7.5.x] loki_datasource: add documentation to label_format and line_format

Backport 0b6b8de6f898c784885fd77d6fdf21a343c9db49 from #31710

backport 
opened Mar 5, 2021 by grafanabot 0
Open

Docs: Update organization_roles.md

Updated in response to PR #31242

Clarifies organization Editor and Admin permissions in regards to folders.

opened Mar 5, 2021 by oddlittlebird 0
Open

Grafana 7.4.3 variable query against MS SQL fails with "p.fields is undefined"

What happened: This query has been functioning fine in older versions of Grafana with an existing dashboard, but I rarely update the variable contents. It set to update never as it is an expensive query and I just go in and run it on demand with the update button as needed. I just found that after upgrading to 7.4.3, updating this variable now fails with the message "p.fields is undefined". I tested it in a newly created dashboard with the same result. The same query works fine in a table panel.

What you expected to happen:
Variable contents to update.

How to reproduce it (as minimally and precisely as possible): Running a simple query like this one against MS SQL: "select distinct JSON_VALUE(version, '$.CTL') from SWVersion"

Anything else we need to know?: Response payload for query: {"results":{"CTL_VER":{"refId":"CTL_VER","meta":{"executedQueryString":"select distinct JSON_VALUE(IFWV, '$.CTL') from SWVersion","rowCount":206},"series":null,"tables":[{"columns":[{"text":""}],"rows":[[null],["\u0005"],["\u000c"],["T0.1.1-1-g0702-d"]...[LOTS OF ROWS]...["v2.3.3-0-gd1a5"]]}],"dataframes":null}}}

Is the null dataframe the problem?

Environment:

  • Grafana version: 7.4.3
  • Data source type & version: MS SQL
  • OS Grafana is installed on: ubunt bionic
  • User OS & Browser: Mac OS 10.15 and Firefox 85
opened Mar 5, 2021 by nathanpegram 1
Open

Docs: Add 7.5 whats new content

  • Added content to What's New
  • Minor edits to Licensing restrictions topic

@sunker - Are there or will there be documentation updates due to the new Cloud Watch and Cloud Monitoring features?

@mjseaman - I removed the link to Reporting from the reporting variables topic, because the content is not yet published. We will add the link when the content exists to link to.

opened Mar 5, 2021 by oddlittlebird 0
Open

Query variable with multiple fields

Dear Grafana team, I would like to know if it is possible to query a variable using multiple fields. i.e. {"find": "terms", "field": "data.name", "field": "data.name_short", "size": 1000} I would like to use the information from two fields in the same variable. Thanks!

opened Mar 5, 2021 by 4quarks 0
Open

Docs: API reference doc page not rendering on the Website

What happened: The API Reference page for @grafana/data is not properly formated.

What you expected to happen: It should render the table and hide any overflow text on the left side-panel.

How to reproduce it (as minimally and precisely as possible): Visit: https://grafana.com/docs/grafana/latest/packages_api/data/

image

Anything else we need to know?: Maybe apply text-overflow: ellipsis; for left side-panel list for names, and some character are missing which is not rendering the table properly.

Environment:

  • Grafana version: NA
  • Data source type & version: NA
  • OS Grafana is installed on: NA
  • User OS & Browser: macOS Catalina, Google Chrome
  • Grafana plugins: NA
  • Others: NA
opened Mar 5, 2021 by starkblaze01 0

v7.5.0-beta1(Mar 4, 2021)

Download page What's new highlights

Features and enhancements

  • Alerting: Customise OK notification priorities for Pushover notifier. #30169, @acaire
  • Alerting: Improve default message for SensuGo notifier. #31428, @M4teo
  • Alerting: PagerDuty: adding current state to the payload. #29270, @Eraac
  • AzureMonitor: Add deprecation message for App Insights/Insights Analytics. #30633, @joshhunt
  • CloudMonitoring: Allow free text input for GCP project on dashboard variable query. #28048
  • CloudMonitoring: Increase service api page size. #30892, @sunker
  • CloudMonitoring: Show service and SLO display name in SLO Query editor. #30900, @sunker
  • CloudWatch: Add AWS Ground Station metrics and dimensions. #31362, @ilyastoli
  • CloudWatch: Add AWS Network Firewall metrics and dimensions. #31498, @ilyastoli
  • CloudWatch: Add AWS Timestream Metrics and Dimensions. #31624, @ilyastoli
  • CloudWatch: Add RDS Proxy metrics. #31595, @sunker
  • CloudWatch: Add eu-south-1 Cloudwatch region. #31198, @rubycut
  • CloudWatch: Make it possible to specify custom api endpoint. #31402, @sunker
  • Cloudwatch: Add AWS/DDoSProtection metrics and dimensions. #31297, @relvira
  • Dashboard: Remove template variables option from ShareModal. #30395, @oscarkilhed
  • Docs: Define TLS/SSL terminology. #30533, @aknuds1
  • Elasticsearch: Add word highlighting to search results. #30293, @simianhacker
  • Folders: Editors should be able to edit name and delete folders. #31242, @torkelo
  • Graphite/SSE: update graphite to work with server side expressions. #31455, @kylebrandt
  • InfluxDB: Improve maxDataPoints error-message in Flux-mode, raise limits. #31259, @gabor
  • InfluxDB: In flux query editor, do not run query when disabled. #31324, @gabor
  • LogsPanel: Add deduplication option for logs. #31019, @ivanahuckova
  • Loki: Add line limit for annotations. #31183, @ivanahuckova
  • Loki: Add support for alerting. #31424, @ivanahuckova
  • Loki: Label browser. #30351, @davkal
  • PieChart: Add color changing options to pie chart. #31588, @oscarkilhed
  • PostgreSQL: Allow providing TLS/SSL certificates as text in addition to file paths. #30353, @ying-jeanne
  • Postgres: SSL certification. #30352, @ying-jeanne
  • Profile: Prevent OAuth users from changing user details or password. #27886, @dupondje
  • Prometheus: Change default httpMethod for new instances to POST. #31292, @ivanahuckova
  • Prometheus: Min step defaults to seconds when no unit is set. #30966, @nutmos
  • Stats: Exclude folders from total dashboard count. #31320, @bergquist
  • Tracing: Specify type of data frame that is expected for TraceView. #31465, @aocenas
  • Transformers: Add search to transform selection. #30854, @ryantxu

Bug fixes

  • Alerting: Ensure Discord notification is sent when metric name is absent. #31257, @LeviHarrison
  • Alerting: Fix case when Alertmanager notifier fails if a URL is not working. #31079, @kurokochin
  • CloudMonitoring: Prevent resource type variable function from crashing. #30901, @sunker
  • Color: Fix issue where colors are reset to gray when switching panels. #31611, @torkelo
  • Explore: Show ANSI colored logs in logs context. #31510, @ivanahuckova
  • Explore: keep enabled/disabled state in angular based QueryEditors correctly. #31558, @gabor
  • Graph: Fix tooltip not being displayed when close to edge of viewport. #31493, @msober
  • Heatmap: Fix missing value in legend. #31430, @kurokochin
  • InfluxDB: Handle columns named "table". #30985, @gabor
  • Prometheus: Use configured HTTP method for /series and /labels endpoints. #31401, @ivanahuckova
  • RefreshPicker: Make valid intervals in url visible in RefreshPicker. #30474, @hugohaggmark
  • TimeSeriesPanel: Fix overlapping time axis ticks. #31332, @torkelo
  • TraceViewer: Fix show log marker in spanbar. #30742, @zoltanbedi

Plugin development fixes & changes

  • Plugins: Add autoEnabled plugin JSON field to auto enable App plugins and add configuration link to menu by default. #31354, @torkelo
  • Pagination: Improve pagination for large number of pages. #30151, @nathanrodman

v7.4.3(Feb 24, 2021)

Download page What's new highlights

Bug fixes

  • AdHocVariables: Fix an issue where adhoc filter values stored as integer was causing Grafana to crash. #31382, @hugohaggmark
  • DashboardLinks: Fix an issue where the dashboard links were causing a full page reload. #31334, @torkelo
  • Elasticsearch: Fix query initialization logic & query transformation from Prometheus/Loki. #31322, @Elfo404
  • QueryEditor: Fix disabling queries in dashboards. #31336, @gabor
  • Streaming: Fix an issue with the time series panel and streaming data source when scrolling back from being out of view. #31431, @torkelo
  • Table: Fix an issue regarding the fixed min and auto max values in bar gauge cell. #31316, @torkelo

v7.4.2(Feb 17, 2021)

Download page What's new highlights

Features and enhancements

  • Explore: Do not show non queryable data sources in data source picker. #31144, @torkelo
  • Snapshots: Disallow anonymous user to create snapshots. #31263, @marefr

Bug fixes

  • CloudWatch: Ensure empty query row errors are not passed to the panel. #31172, @sunker
  • DashboardLinks: Fixes links always cause full page reload. #31178, @torkelo
  • DashboardListPanel: Fixes issue with folder picker always showing All and using old form styles. #31160, @torkelo
  • IPv6: Support host address configured with enclosing square brackets. #31226, @aknuds1
  • Permissions: Fix team and role permissions on folders/dashboards not displayed for non Grafana Admin users. #31132, @AgnesToulet
  • Postgres: Fix timeGroup macro converts long intervals to invalid numbers when TimescaleDB is enabled. #31179, @kurokochin
  • Prometheus: Fix enabling of disabled queries when editing in dashboard. #31055, @ivanahuckova
  • QueryEditors: Fixes issue that happens after moving queries then editing would update other queries. #31193, @torkelo
  • SqlDataSources: Fixes the Show Generated SQL button in query editors. #31236, @torkelo
  • StatPanels: Fixes to palette color scheme is not cleared when loading panel. #31126, @torkelo
  • Variables: Adds back default option for data source variable. #31208, @hugohaggmark
  • Variables: Fixes missing empty elements from regex filters. #31156, @hugohaggmark

v7.4.1(Feb 11, 2021)

Download page What's new highlights

Features and enhancements

  • Influx: Make max series limit configurable and show the limiting message if applied. #31025, @aocenas
  • Make value mappings correctly interpret numeric-like strings. #30893, @dprokop
  • Variables: Adds queryparam formatting option. #30858, @hugohaggmark

Bug fixes

  • Alerting: Fixes so notification channels are properly deleted. #31040, @hugohaggmark
  • BarGauge: Improvements to value sizing and table inner width calculations. #30990, @torkelo
  • DashboardLinks: Fixes crash when link has no title. #31008, @hugohaggmark
  • Elasticsearch: Fix alias field value not being shown in query editor. #30992, @Elfo404
  • Elasticsearch: Fix log row context errors. #31088, @Elfo404
  • Elasticsearch: Show Size setting for raw_data metric. #30980, @Elfo404
  • Graph: Fixes so graph is shown for non numeric time values. #30972, @hugohaggmark
  • Logging: Ignore 'file already closed' error when closing file. #31119, @aknuds1
  • Plugins: Fix plugin signature validation for manifest v2 on Windows. #31045, @wbrowne
  • TextPanel: Fixes so panel title is updated when variables change. #30884, @hugohaggmark
  • Transforms: Fixes Outer join issue with duplicate field names not getting the same unique field names as before. #31121, @torkelo

v7.4.0(Feb 4, 2021)

Download page What's new highlights

Features and enhancements

Bug fixes

Plugin development fixes & changes

  • Plugins: Fix failing plugin builds because of wrong internal import. #30439, @aocenas

v7.4.0-beta1(Jan 20, 2021)

Download page What's new highlights

Features and enhancements

Bug fixes

  • API: Query database from /api/health endpoint. #28349, @ceh
  • Alerting: Return proper status code when trying to create alert notification channel with duplicate name or uid. #28043, @jgulick48
  • Auth: Fix default maximum lifetime an authenticated user can be logged in. #30030, @papagian
  • Backend: Fix IPv6 address parsing erroneous. #28585, @taciomcosta
  • CloudWatch: Make sure stats grow horizontally and not vertically in the Query Editor. #30106, @sunker
  • Cloudwatch: Fix issue with field calculation transform not working properly with Cloudwatch data. #28761, @torkelo
  • Dashboards: Hide playlist edit functionality from viewers and snapshots link from unauthenticated users. #28992, @jackw
  • Data source proxy: Convert 401 HTTP status code from data source to 400. #28962, @aknuds1
  • Decimals: Improving auto decimals logic for high numbers and scaled units. #30262, @torkelo
  • Elasticsearch: Fix date histogram auto interval handling for alert queries. #30049, @simianhacker
  • Elasticsearch: Fix index pattern not working with multiple base sections. #28348, @tomdaly
  • Explore: Clear errors after running a new query. #30367, @ivanahuckova
  • Graph: Fixes stacking issues like floating bars when data is not aligned. #29051, @torkelo
  • Graph: Staircase and null value=null calculates auto Y-Min incorrectly (fixed in new Time series panel). #12995
  • Graph: Staircase mode, do now draw line segment from zero when drawing null values as null (Fixed in new Time series panel). #17838
  • Image uploader: Fix uploading of images to GCS. #26493, @gastonqiu
  • Influx: Fixes issue with many queries being issued as you type in the variable query field. #29968, @dprokop
  • Logs Panel: Fix inconsistent highlighting. #28971, @ivanahuckova
  • Logs Panel: Fixes problem dragging scrollbar inside logs panel. #28974, @aocenas
  • Loki: Fix hiding of series in table if labels have number values. #30185, @ivanahuckova
  • Loki: Lower min step to 1ms. #30135, @ivanahuckova
  • Loki: Remove showing of unique labels with the empty string value. #30363, @ivanahuckova
  • Loki: Timeseries should not produce 0-values for missing data. #30116, @davkal
  • Plugins: Fix panic when using complex dynamic URLs in app plugin routes. #27977, @cinaglia
  • Prometheus: Fix link to Prometheus graph in dashboard. #29543, @ivanahuckova
  • Provisioning: Build paths in an os independent way. #29143, @amattheisen
  • Provisioning: Fixed problem with getting started panel being added to custom home dashboard. #28750, @torkelo
  • SAML: Fixes bug in processing SAML response with empty element by updating saml library (Enterprise). #29991, @alexanderzobnin
  • SQL: Define primary key for tables without it. #22255, @azhiltsov
  • Tracing: Fix issue showing more than 300 spans. #29377, @zoltanbedi
  • Units: Changes FLOP/s to FLOPS and some other rates per second units get /s suffix. #28825, @Berbe
  • Variables: Fixes Constant variable persistence confusion. #29407, @hugohaggmark
  • Variables: Fixes Textbox current value persistence. #29481, @hugohaggmark
  • Variables: Fixes loading with a custom all value in url. #28958, @hugohaggmark
  • Variables: Fixes so clicking on Selected in drop down will exclude All value from selection. #29844, @hugohaggmark

Breaking changes

Constant variables

In order to minimize the confusion with Constant variable usage, we've removed the ability to make Constant variables visible. This change will also migrate all existing visible Constant variables to Textbox variables because which we think this is a more appropriate type of variable for this use case. Issue #29407

Plugin compatibility

We have upgraded AngularJS from version 1.6.6 to 1.8.2. Due to this upgrade some old angular plugins might stop working and will require a small update. This is due to the deprecation and removal of pre-assigned bindings. So if your custom angular controllers expect component bindings in the controller constructor you need to move this code to an $onInit function. For more details on how to migrate AngularJS code open the migration guide and search for pre-assigning bindings.

In order not to break all angular panel plugins and data sources we have some custom angular inject behavior that makes sure that bindings for these controllers are still set before constructor is called so many old angular panels and data source plugins will still work. Issue #28736

Deprecations

Query variable value group tags

This option to group query variable values into groups by tags has been an experimental feature since it was introduced. It was introduced to work around the lack of tags support in time series databases at the time. Now that tags (ie. labels) are the norm there is no longer any great need for this feature. This feature will be removed in Grafana v8 later this year. Issue #30160

Plugin development fixes & changes

  • FieldConfig API: Add ability to hide field option or disable it from the overrides. #29879, @dprokop
  • Select: Changes default menu placement for Select from auto to bottom. #29837, @hugohaggmark
  • Collapse: Allow component children to use height: 100% styling. #29776, @aocenas
  • DataSourceWithBackend: Throw error if health check fails in DataSourceWithBackend. #29743, @aocenas
  • NodeGraph: Add node graph visualization. #29706, @aocenas
  • FieldColor: Handling color changes when switching panel types. #28875, @dprokop
  • CodeEditor: Added support for javascript language. #28818, @ae3e
  • grafana/toolkit: Allow builds with lint warnings. #28810, @dprokop
  • grafana/toolkit: Drop console and debugger statements by default when building plugin. #28776, @dprokop
  • Card: Add new Card component. #28216, @Clarity-89
  • FieldConfig: Implementation slider editor (#27592). #28007, @isaozlerfm
  • MutableDataFrame: Remove unique field name constraint and values field index and unused/seldom used stuff. #27573, @torkelo
Information
Category: Golang / Data Visualization
Watchers: 1.2k
Star: 40.2k
Fork: 8.1k
Last update: Mar 6, 2021

Contents
    Resource links
    https://github.com/grafana/grafana
    Share this repo
    Most popular
    grafana The tool for beautiful monitoring and metric analytics & dashboards for Graphite, InfluxDB & Prometheus & More
    wcharczuk go chart is a basic charting library in native golang.
    nakabonne Generate HTTP load and plot the results in real-time
    skydive-project Skydive is an open source real-time network topology and protocols analyzer.
    guptarohit Go package to make lightweight ASCII line graph ╭┈╯ in command line apps with no other dependencies.
    mgartner A flamegraph generator for Postgres EXPLAIN ANALYZE output.
    sgreben dead simple terminal plots from JSON data. single binary, no dependencies. linux, osx, windows.
    nghialv Visualize the traffic of your clusters in realtime from Prometheus data
    marianogappa Quick & smart charting for STDIN
    Arafatk Glot is a plotting library for Golang built on top of gnuplot.

    Related Repos


    Data Visualization
    25
    This example shows how to use Anychart library with the Go programming language and MySQL ...
    anychart-integrations Go basic template This example shows how to use Anychart library with the Go programming language and MySQL database. Running To use this sample you must have Go installed as described here, and follow the official
     
    Data Visualization
    521
    Quick & smart charting for STDIN
    marianogappa chart Quick & smart charting for STDIN Blogpost Learn by example! Cheatsheet Syntax chart [options] pie: render a pie chart bar: render a bar chart line: render a line chart scatter:
     
    Data Visualization
    124
    Create plots from Prometheus metrics and send them to you
    qvl 📈 promplot promplot is an opinionated tool to create plots from your Prometheus metrics and automatically sends them to you. Slack example: promplot -title "Open File Descriptors" -query "process_open_fds" -range
     
    Popular
    Data Visualization
    40.2k
    The tool for beautiful monitoring and metric analytics & dashboards for Graphite, InfluxDB...
    grafana 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
     
    Data Visualization
    348
    Glot is a plotting library for Golang built on top of gnuplot.
    Arafatk Glot glot is a plotting library for Golang built on top of gnuplot. glot currently supports styles like lines, points, bars, steps, histogram, circle, and many others. We are continuously making efforts to add more features.
     
    Data Visualization
    883
    Visualize the traffic of your clusters in realtime from Prometheus data
    nghialv Promviz Promviz is an application that helps you visualize the traffic of your cluster from Prometheus data. It has 2 components: Promviz: retrieves data from Prometheus servers, aggregates them and provides an API to ge
     
    Data Visualization
    1.2k
    dead simple terminal plots from JSON data. single binary, no dependencies. linux, osx, win...
    sgreben jp Dead simple terminal plots from JSON (or CSV) data. Bar charts, line charts, scatter plots, histograms and heatmaps are supported. Get it Use it Examples Bar chart Separate X and Y values
     
    Data Visualization
    1.6k
    Go package to make lightweight ASCII line graph ╭┈╯ in command line apps with no other dep...
    guptarohit asciigraph Go package to make lightweight ASCII line graphs ╭┈╯. Installation go get github.com/guptarohit/asciigraph Usage Basic graph package main import