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.

2724 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

[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.
screen shot 2016-12-16 at 02 28 33
area/alerting type/feature-request 
opened Dec 15, 2016 by costimuraru 190
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

  1. The action (notifications) can be different.
  2. 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

area/alerting type/feature-request 
opened Mar 14, 2017 by sanchitraizada 148
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 141
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
Open

Explore logs doesn't show the colors [Grafana v8.0.3]

Here is what I see when querying my k8s app logs on Grafana: Screenshot from 2021-06-23 00-58-08

But, here is what "kubectl logs <pod_id>" shows: Screenshot from 2021-06-23 00-58-38

You can see that Grafana displays UTF8 characters, while it should display purple color text...

Do you have the same problem?

Thanks for your help!

Environment:

  • Grafana version: v8.0.3
  • Data source type & version: Loki latest
  • OS Grafana is installed on: Kubernetes
opened Jun 22, 2021 by waterdrop01 0
Open

FieldColors: Unique colors by value mode POC (alternative)

Alternative to #35961 -- far from great, but worth discussing

This flavor will keep stable colors regardless of the order.

TODO: this will pick a reasonable value for strings, can we indicate that this should use the value rather than -Infinity in: https://github.com/grafana/grafana/commit/ca8f6addabb2558e8dc76d6d72c11e40f73061a9#diff-abbff869c6239f7bfd1ea0fdb5efce90ce5e8c1d21fa48546f54a2e390d14f5cL116

this was pulled out to the code we reverted because it gave all strings an odd background in tables :(

area/frontend 
opened Jun 22, 2021 by ryantxu 0
Open

[NG-Alerting] Microsoft Teams template missing new-lines before Annotations & Silence (cosmetic issue)

What happened: I setup the ng-alerting with Microsoft Teams webhook as a contact point. The alerts are sent as expected and contain the correct information. This is just a cosmetic issue. The default template for the Microsoft Teams notification seems to be missing two new-lines: one after the last Label and before Annotations and one after the last Annotation and before Silence

In the example image, severity is my last label

image

What you expected to happen: I would expect two bullet point lists: Labels, Annotations and (after a new line): the silence link

Environment:

  • Grafana version: 8.0.3
  • Data source type & version: InfluxDB 1.8
  • OS Grafana is installed on: Docker
  • User OS & Browser: Windows 10/Chromium
  • Grafana plugins: n/a
area/unified-alerting needs investigation 
opened Jun 22, 2021 by diveflo 0
Open

[Feature Request] [NG-Alerting] Filter alert instances based on their state in Alerts view and Alert List panel

What would you like to be added: Ability to filter ng-alert instances based on their state, rather than only per alert. This would be great for both the Alert view as Alert List panel.

Why is this needed: We have a few alerts which thanks to the new alerting in Grafana 8 are multidimensional and create hundrets of alert instances each. Going through them to find the one that's firing can be quite cumbersome.

image

Version: 8.0.3

area/unified-alerting type/feature-request 
opened Jun 22, 2021 by diveflo 0
Open

StreamingDataFrame: skip empty labels

Currently if a result has values with labels and without, we display some bad lables:

image

With this PR applied it is a bit more sensible: image

area/frontend area/live 
opened Jun 22, 2021 by ryantxu 0
Open

[Feature Request] Ability to see the alerts matching the silence when creating one

What would you like to be added: The ability to see how much alerts would match the silence when creating one and possibly the list of them

Why is this needed: When manually creating a silence, there's no way to know how much alerts would be muted when the alert would be created. You can easily create the silence just to realize later that you've messed up the filters and the alert you wanted to silence was ignored.

area/alerting type/feature-request 
opened Jun 22, 2021 by Freak12Techno 0

v8.0.3(Jun 18, 2021)

Download page What's new highlights

Features and enhancements

  • Alerting: Increase alertmanager_conf column if MySQL. #35657, @kylebrandt
  • Time series/Bar chart panel: Handle infinite numbers as nulls when converting to plot array. #35638, @dprokop
  • TimeSeries: Ensure series overrides that contain color are migrated, and migrate the previous fieldConfig when changing the panel type. #35676, @ashharrison90
  • ValueMappings: Improve singlestat value mappings migration. #35578, @dprokop

Bug fixes

  • Annotations: Fix annotation line and marker colors. #35608, @torkelo
  • AzureMonitor: Fix KQL template variable queries without default workspace. #35836, @joshhunt
  • CloudWatch/Logs: Fix missing response data for log queries. #35724, @aocenas
  • Elasticsearch: Restore previous field naming strategy when using variables. #35624, @Elfo404
  • LibraryPanels: Fix crash in library panels list when panel plugin is not found. #35907, @torkelo
  • LogsPanel: Fix performance drop when moving logs panel in dashboard. #35379, @aocenas
  • Loki: Parse log levels when ANSI coloring is enabled. #35607, @olbo98
  • MSSQL: Fix issue with hidden queries still being executed. #35787, @torkelo
  • PanelEdit: Display the VisualizationPicker that was not displayed if a panel has an unknown panel plugin. #35831, @jackw
  • Plugins: Fix loading symbolically linked plugins. #35635, @domasx2
  • Prometheus: Fix issue where legend name was replaced with name Value in stat and gauge panels. #35863, @torkelo
  • State Timeline: Fix crash when hovering over panel. #35692, @hugohaggmark

v7.5.8(Jun 16, 2021)

Download page What's new highlights

Features and enhancements

  • Datasource: Add support for max_conns_per_host in dataproxy settings. #35519, @jvrplmlmn
  • Datasource: Add support for max_idle_connections_per_host in dataproxy settings. #35365, @dsotirakis
  • Instrumentation: Add metrics for outbound HTTP connections. #35321, @dsotirakis
  • Snapshots: Remove dashboard links from dashboard snapshots. #35567, @torkelo

v8.0.2(Jun 14, 2021)

Download page What's new highlights

Features and enhancements

  • Datasource: Add support for max_conns_per_host in dataproxy settings. #35520, @jvrplmlmn

Bug fixes

v8.0.1(Jun 10, 2021)

Download page What's new highlights

Bug fixes

  • Alerting/SSE: Fix "count_non_null" reducer validation. #35451, @kylebrandt
  • Cloudwatch: Fix duplicated time series. #35433, @sunker
  • Cloudwatch: Fix missing defaultRegion. #35436, @andresmgot
  • Dashboard: Fix Dashboard init failed error on dashboards with old singlestat panels in collapsed rows. #35425, @torkelo
  • Datasource: Fix storing timeout option as numeric. #35441, @marefr
  • Postgres/MySQL/MSSQL: Fix annotation parsing for empty responses. #35367, @marcbachmann
  • Postgres/MySQL/MSSQL: Fix so that numeric/non-string values are returned from query variables. #35411, @marefr
  • Postgres: Fix error thrown when annotation query does not return any results. #35382, @dprokop
  • StatPanel: Fix issue with graph look when switching color mode. #35460, @torkelo
  • Visualizations: Fix Stat/BarGauge/Gauge/PieChart all values mode showing same name if same value. #35368, @torkelo

Plugin development fixes & changes

  • Toolkit: Resolve external fonts when Grafana is served from a sub path. #35352, @jackw

v8.0.0(Jun 8, 2021)

Download page What's new highlights

Features and enhancements

  • AzureMonitor: Require default subscription for workspaces() template variable query. #35181, @joshhunt
  • AzureMonitor: Use resource type display names in the UI. #35060, @joshhunt
  • Dashboard: Remove support for loading and deleting dashboard by slug. #35104, @dsotirakis
  • InfluxDB: Deprecate direct browser access in data source. #35105, @gabor
  • VizLegend: Add a read-only property. #35096, @dprokop

Bug fixes

  • AzureMonitor: Fix Azure Resource Graph queries in Azure China. #35235, @kostrse
  • Checkbox: Fix vertical layout issue with checkboxes due to fixed height. #35022, @torkelo
  • Dashboard: Fix Table view when editing causes the panel data to not update. #34998, @axelavargas
  • Dashboard: Fix issues where unsaved-changes warning is not displayed. #34989, @torkelo
  • Login: Fixes Unauthorized message showing when on login page or snapshot page. #35311, @torkelo
  • NodeGraph: Fix sorting markers in grid view. #35200, @aocenas
  • Short URL: Include orgId in generated short URLs. #34696, @farodin91
  • Variables: Support raw values of boolean type. #34727, @simPod

Breaking changes

The following endpoints were deprecated for Grafana v5.0 and support for them has now been removed:

  • GET /dashboards/db/:slug
  • GET /dashboard-solo/db/:slug
  • GET /api/dashboard/db/:slug
  • DELETE /api/dashboards/db/:slug Issue #35104

v8.0.0-beta3(Jun 1, 2021)

Download page What's new highlights

Features and enhancements

  • API: Support folder UID in dashboards API. #33991, @zserge
  • Alerting: Add support for configuring avatar URL for the Discord notifier. #33355, @ChipWolf
  • Alerting: Clarify that Threema Gateway Alerts support only Basic IDs. #34828, @dbrgn
  • Azure: Expose Azure settings to external plugins. #34484, @sunker
  • AzureMonitor: Deprecate using separate credentials for Azure Monitor Logs. #34758, @andresmgot
  • AzureMonitor: Display variables in resource picker for Azure Monitor Logs. #34648, @joshhunt
  • AzureMonitor: Hide application insights for data sources not using it. #34725, @joshhunt
  • AzureMonitor: Support querying subscriptions and resource groups in Azure Monitor Logs. #34766, @joshhunt
  • AzureMonitor: remove requirement for default subscription. #34787, @kostrse
  • CloudWatch: Add [email protected] Amazon CloudFront metrics. #34561, @razor-x
  • CloudWatch: Add missing AWS and AppSync metrics. #34691, @razor-x
  • ConfirmModal: Auto focus delete button. #34917, @torkelo
  • Explore: Add caching for queries that are run from logs navigation. #34297, @ivanahuckova
  • Loki: Add formatting for annotations. #34774, @fredr
  • Loki: Bring back processed bytes as meta information. #34092, @mmenbawy
  • NodeGraph: Display node graph collapsed by default with trace view. #34491, @aocenas
  • Overrides: Include a manual override option to hide something from visualization. #34783, @torkelo
  • PieChart: Support row data in pie charts. #34755, @torkelo
  • Prometheus: Update default HTTP method to POST for existing data sources. #34599, @ivanahuckova
  • Time series panel: Position tooltip correctly when window is scrolled or resized. #34782, @dprokop

Bug fixes

  • Admin: Fix infinite loading edit on the profile page. #34627, @hugohaggmark
  • Color: Fix issues with random colors in string and date fields. #34913, @torkelo
  • Dashboard: Fix issue with title or folder change has no effect after exiting settings view. #34677, @torkelo
  • DataLinks: Fix an issue __series.name is not working in data link. #34932, @torkelo
  • Datasource: Fix dataproxy timeout should always be applied for outgoing data source HTTP requests. #34597, @dsotirakis
  • Elasticsearch: Fix NewClient not passing httpClientProvider to client impl. #34539, @KiVirgil
  • Explore: Fix Browser title not updated on Navigation to Explore. #34651, @axelavargas
  • GraphNG: Remove fieldName and hideInLegend properties from UPlotSeriesBuilder. #34901, @dprokop
  • OAuth: Fix fallback to auto_assign_org_role setting for Azure AD OAuth when no role claims exists. #34838, @idafurjes
  • PanelChrome: Fix issue with empty panel after adding a non data panel and coming back from panel edit. #34765, @torkelo
  • StatPanel: Fix data link tooltip not showing for single value. #34934, @torkelo
  • Table: Fix sorting for number fields. #34722, @hugohaggmark
  • Table: Have text underline for datalink, and add support for image datalink. #34635, @thisisobate
  • Time series panel: Position tooltip correctly when window is scrolled or resized. #34584, @dprokop
  • Transformations: Prevent FilterByValue transform from crashing panel edit. #34747, @jackw

Breaking changes

The default HTTP method for Prometheus data source is now POST. Previously, it was GET. The POST APIs have been available since January 2018 (Prometheus 2.1.0) and they have fewer limitations than the GET APIs. For example, when dealing with high cardinality labels, GET hits the URL size limit.

If you have a Prometheus instance with version < 2.1.0, which uses the default HTTP method, update your HTTP method to GET. Issue #34599

Information
Category: Golang / Data Visualization
Watchers: 1.2k
Star: 42.6k
Fork: 8.5k
Last update: Jun 17, 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
    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.7k
    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
     
    Data Visualization
    1.4k
    A flamegraph generator for Postgres EXPLAIN ANALYZE output.
    mgartner pg_flame A flamegraph generator for Postgres EXPLAIN ANALYZE output. Demo Try the demo here. Installation Homebrew You can install via Homebrew with the follow command: $ brew install mgartner/tap/pg_fla
     
    Data Visualization
    28
    📊 Update a pinned gist to contain your weekly WakaTime stat
    YouEclipse 📊 Update a pinned gist to contain your weekly WakaTime stats. This is a Golang implementation, see the original version
     
    Data Visualization
    249
    Generate High Level Microservice Architecture diagrams for GraphViz using simple YAML synt...
    lucasepe A commandline tool that generate High Level microservice & serverless Architecture diagrams using a declarative syntax defined in a YAML file.
     
    Data Visualization
    25
    Visualize call permissions between Cloud Run services
    ahmetb This tool visualizes call permissions between Cloud Run fully managed services.
     
    Data Visualization
    28
    program to visualize resource usage, very similar to Dag Wieers’s dstat default output
    gokrazy program to visualize resource usage, very similar to Dag Wieers’s dstat default output
     
    Data Visualization
    124
    Generate image plots of processes' memory usage very quickly, within a single binary.
    0x0f0f0f A small utility written in golang to quickly plot memory usage of processes