profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/grafana/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Grafana Labs grafana Sweden https://grafana.com Grafana Labs is behind leading open source projects Grafana and Loki, and the creator of the first open & composable observability platform.

grafana/carbon-relay-ng 441

Fast carbon relay+aggregator with admin interfaces for making changes online - production ready

grafana/agent 437

Prometheus Metrics, Loki Logs, and Tempo Traces, optimized for Grafana Cloud.

grafana/awesome-k6 132

A curated list of resources on automated load- and performance testing using k6 🗻

grafana/azure-monitor-datasource 91

Grafana data source for Azure Monitor/Application Insights (deprecated - now included in core Grafana)

grafana/clock-panel 72

Clock Panel Plugin for Grafana

grafana/cortex-jsonnet 65

This repo has the jsonnet for deploying and also the mixin for monitoring Cortex

grafana/azure-data-explorer-datasource 32

Grafana datasource plugin for Microsoft Azure Data Explorer (formerly Azure Kusto)

grafana/cortex 25

A multitenant, horizontally scalable Prometheus as a Service

grafana/cloud-graphite-scripts 10

Example program to send data to Grafana Hosted Metrics Graphite service

grafana/ansible-grafana 8

Ansible role for grafana deployment

startedgrafana/grafana

started time in 18 minutes

create barnchgrafana/yet-another-cloudwatch-exporter

branch : cristian/tags-refactoring

created branch time in 21 minutes

issue commentgrafana/grafana

[Time Series] Dot is shown at the end of the graph

Update: I've noticed it also occurs on other panels. image

My last assumption, where I said it happens only on panels where last value is null, wasn't true.

Here are the settings of the blue graph: image

image

image

image

szerwi

comment created time in 26 minutes

startedgrafana/grafana

started time in an hour

push eventgrafana/grafana

Ryan McKinley

commit sha c9ae46a9adde629e762a298f1d3001c89ed88aa3

PanelOptions: fix array with siblings (#39620)

view details

Ryan McKinley

commit sha 27074317693d058b4558f8527dc58568ed8472b8

Merge remote-tracking branch 'origin/main' into scatter-plot-v2

view details

Ryan McKinley

commit sha 6135a6466b98f74e0858c7e70e70623d42406825

scatter

view details

push time in an hour

startedgrafana/tempo

started time in an hour

startedgrafana/k6

started time in an hour

push eventgrafana/grafana

Grot (@grafanabot)

commit sha fee11227daf94802494eadc07a137c8fe0e70969

PanelOptions: fix array with siblings (#39620) (#39623) (cherry picked from commit c9ae46a9adde629e762a298f1d3001c89ed88aa3) Co-authored-by: Ryan McKinley <ryantxu@gmail.com>

view details

push time in 2 hours

delete branch grafana/grafana

delete branch : backport-39620-to-v8.2.x

delete time in 2 hours

PR merged grafana/grafana

Reviewers
[v8.2.x] PanelOptions: fix array paths with siblings area/frontend backport

Backport c9ae46a9adde629e762a298f1d3001c89ed88aa3 from #39620

+2 -0

0 comment

2 changed files

grafanabot

pr closed time in 2 hours

startedgrafana/grafana

started time in 2 hours

PullRequestReviewEvent

create barnchgrafana/grafana

branch : backport-39620-to-v8.2.x

created branch time in 2 hours

PR opened grafana/grafana

[v8.2.x] PanelOptions: fix array paths with siblings

Backport c9ae46a9adde629e762a298f1d3001c89ed88aa3 from #39620

+2 -0

0 comment

2 changed files

pr created time in 2 hours

push eventgrafana/grafana

Ryan McKinley

commit sha c9ae46a9adde629e762a298f1d3001c89ed88aa3

PanelOptions: fix array with siblings (#39620)

view details

Ryan McKinley

commit sha 10b8d7c7382871eb16121077a15a0f56a7d6addc

Merge remote-tracking branch 'origin/main' into nested-options-again

view details

push time in 2 hours

push eventgrafana/grafana

Ryan McKinley

commit sha c9ae46a9adde629e762a298f1d3001c89ed88aa3

PanelOptions: fix array with siblings (#39620)

view details

push time in 2 hours

delete branch grafana/grafana

delete branch : fix-nested-options

delete time in 2 hours

PR merged grafana/grafana

Reviewers
PanelOptions: fix array paths with siblings area/frontend backport v8.2.x

Fixes to #39499, found while working with #39491

+2 -0

0 comment

2 changed files

ryantxu

pr closed time in 2 hours

startedgrafana/grafana

started time in 3 hours

startedgrafana/grafana

started time in 3 hours

issue commentgrafana/grafana

Node Graph Panel does not render properly.

you can find all info here

pep-pig

comment created time in 3 hours

issue commentgrafana/grafana

Send alert notification for every alert eval regardless of state

Would really love to see an OPTIONAL feature added to be to send alerts for each event that crosses the threshold.

2021-09-24_7-44-37

You can use reminders

Now grafana has a send reminders option now in the Alert Notifications page. Which allows notification to be sent every interval(selected by you) while alert is still on.

qhh0205

comment created time in 4 hours

startedgrafana/grafana

started time in 4 hours

startedgrafana/k6

started time in 5 hours

push eventgrafana/cuetsy

sam boyer

commit sha c3c26918ce20088c5585743a73f76aaffa2d0cc9

Add gitignore

view details

push time in 5 hours

issue openedgrafana/grafana

Panels oscillate between showing full data and "no data"

What happened:

We were using Grafana 6 and I upgraded to see if this issue was fixed but it's not. It might be a prometheus or configuration problem but it's very difficult to search for.

It's best explained via a video:

https://user-images.githubusercontent.com/1636971/134770302-a77a12b3-d5f4-4567-a552-c3dd660d0f45.mov

This is on a 5s refresh, but it happens without auto refresh, you just have to be (un)lucky enough to load the page at the right time and most of the graphs will show "no data", but a couple of refreshes later and you see charts.

I opened the inspector and checked out some of the queries and a lot of them just return this:

{"status":"success","data":{"resultType":"matrix","result":[]}}

Which is going through the grafana server side proxy to prometheus' API.

What you expected to happen:

If there's no data, it seems like there should be gaps in the data but when the graph renders normally, it shows all the data going back through the selected time range.

I would expect an error if there's actually no data available but I'm thinking this might be a prometheus issue rather than grafana - but figured I'd start here and see if anyone has any ideas.

How to reproduce it (as minimally and precisely as possible):

Not entirely sure unfortunately, I have the exact same setup: https://github.com/picostack/core running on a few servers of mine and other people's and a couple of them do this, the rest don't. We can't figure out the exact differences between environments that may cause this. The configs are the same.

Anything else we need to know?:

Environment: Linux, Docker, This exact setup: https://github.com/picostack/core

  • Grafana version: 8.1.5
  • Data source type & version: Prometheus v2.18.1
  • OS Grafana is installed on: Linux Ubuntu 20
  • User OS & Browser: Mac, chrome latest stable
  • Grafana plugins: None

created time in 6 hours

startedgrafana/grafana

started time in 6 hours

issue commentgrafana/grafana

Too many ESTABLISHED tcp connection from Grafana to alertmanager

Grafana Service Logs :

Sep 23 10:04:00 monitoring alertmanager[541401]: 2021/09/23 10:04:00 http: Accept error: accept tcp [::]:9093: accept4: too many open files; retrying in 1s Sep 23 10:04:01 monitoring alertmanager[541401]: 2021/09/23 10:04:01 http: Accept error: accept tcp [::]:9093: accept4: too many open files; retrying in 1s Sep 23 10:04:02 monitoring alertmanager[541401]: 2021/09/23 10:04:02 http: Accept error: accept tcp [::]:9093: accept4: too many open files; retrying in 1s Sep 23 10:04:03 monitoring alertmanager[541401]: 2021/09/23 10:04:03 http: Accept error: accept tcp [::]:9093: accept4: too many open files; retrying in 1s Sep 23 10:04:04 monitoring alertmanager[541401]: 2021/09/23 10:04:04 http: Accept error: accept tcp [::]:9093: accept4: too many open files; retrying in 1s lsof Command output : grafana-s 549286 grafana 27u IPv4 598948692 0t0 TCP 127.0.0.1:42314->127.0.0.1:9093 (ESTABLISHED) grafana-s 549286 grafana 28u IPv4 598942905 0t0 TCP 127.0.0.1:38036->127.0.0.1:9093 (ESTABLISHED) grafana-s 549286 grafana 29u IPv4 598954114 0t0 TCP 127.0.0.1:43378->127.0.0.1:9093 (ESTABLISHED) grafana-s 549286 grafana 30u IPv4 598943199 0t0 TCP 127.0.0.1:39098->127.0.0.1:9093 (ESTABLISHED) grafana-s 549286 grafana 31u IPv4 598954518 0t0 TCP 127.0.0.1:44458->127.0.0.1:9093 (ESTABLISHED) grafana-s 549286 grafana 32u IPv4 598955747 0t0 TCP 127.0.0.1:45524->127.0.0.1:9093 (ESTABLISHED) grafana-s 549286 grafana 33u IPv4 598959917 0t0 TCP 127.0.0.1:46616->127.0.0.1:9093 (ESTABLISHED) grafana-s 549286 grafana 34u IPv4 598961686 0t0 TCP 127.0.0.1:47688->127.0.0.1:9093 (ESTABLISHED) grafana-s 549286 grafana 35u IPv4 598963736 0t0 TCP 127.0.0.1:48760->127.0.0.1:9093 (ESTABLISHED) grafana-s 549286 grafana 36u IPv4 598965092 0t0 TCP 127.0.0.1:49846->127.0.0.1:9093 (ESTABLISHED)

sahandhabibi

comment created time in 6 hours

issue openedgrafana/grafana

centrifuge "debug: true" enabled by default

What happened centrifuge console debug is enabled by default.

Bildschirmfoto 2021-09-25 um 13 37 52

How to reproduce it (as minimally and precisely as possible) Install Grafana over APT

Environment

  • Grafana version: Version 8.1.2 (commit: 103f8fa094, branch: HEAD)
  • OS Grafana is installed on: Ubuntu 20.04.3 LTS

created time in 6 hours

startedgrafana/k6

started time in 7 hours