You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
***Dashboard**: TV & Kiosk mode changes, new cycle view mode button in dashboard toolbar [#13025](https://github.com/grafana/grafana/pull/13025)
3
7
***OAuth**: Gitlab OAuth with support for filter by groups [#5623](https://github.com/grafana/grafana/issues/5623), thx [@BenoitKnecht](https://github.com/BenoitKnecht)
4
-
***Dataproxy**: Pass configured/auth headers to a Datasource [#10971](https://github.com/grafana/grafana/issues/10971), thx [@mrsiano](https://github.com/mrsiano)
5
-
***Cleanup**: Make temp file time to live configurable [#11607](https://github.com/grafana/grafana/issues/11607), thx [@xapon](https://github.com/xapon)
***LDAP**: Define Grafana Admin permission in ldap group mappings [#2469](https://github.com/grafana/grafana/issues/2496), PR [#12622](https://github.com/grafana/grafana/issues/12622)
7
-
***Cloudwatch**: CloudWatch GetMetricData support [#11487](https://github.com/grafana/grafana/issues/11487), thx [@mtanda](https://github.com/mtanda)
8
-
***Configuration**: Allow auto-assigning users to specific organization (other than Main. Org) [#1823](https://github.com/grafana/grafana/issues/1823)[#12801](https://github.com/grafana/grafana/issues/12801), thx [@gzzo](https://github.com/gzzo) and [@ofosos](https://github.com/ofosos)
9
-
***Profile**: List teams that the user is member of in current/active organization [#12476](https://github.com/grafana/grafana/issues/12476)
10
13
***LDAP**: Client certificates support [#12805](https://github.com/grafana/grafana/issues/12805), thx [@nyxi](https://github.com/nyxi)
14
+
***Profile**: List teams that the user is member of in current/active organization [#12476](https://github.com/grafana/grafana/issues/12476)
15
+
***Configuration**: Allow auto-assigning users to specific organization (other than Main. Org) [#1823](https://github.com/grafana/grafana/issues/1823)[#12801](https://github.com/grafana/grafana/issues/12801), thx [@gzzo](https://github.com/gzzo) and [@ofosos](https://github.com/ofosos)
16
+
***Dataproxy**: Pass configured/auth headers to a Datasource [#10971](https://github.com/grafana/grafana/issues/10971), thx [@mrsiano](https://github.com/mrsiano)
17
+
***Cloudwatch**: CloudWatch GetMetricData support [#11487](https://github.com/grafana/grafana/issues/11487), thx [@mtanda](https://github.com/mtanda)
11
18
***Postgres**: TimescaleDB support, e.g. use `time_bucket` for grouping by time when option enabled [#12680](https://github.com/grafana/grafana/pull/12680), thx [svenklemm](https://github.com/svenklemm)
19
+
***Cleanup**: Make temp file time to live configurable [#11607](https://github.com/grafana/grafana/issues/11607), thx [@xapon](https://github.com/xapon)
12
20
13
21
### Minor
14
22
23
+
***Units**: Adds bitcoin axes unit. [#13125](https://github.com/grafana/grafana/pull/13125)
24
+
***GrafanaCli**: Fixed issue with grafana-cli install plugin resulting in corrupt http response from source error. Fixes [#13079](https://github.com/grafana/grafana/issues/13079)
25
+
***Logging**: Reopen log files after receiving a SIGHUP signal [#13112](https://github.com/grafana/grafana/pull/13112), thx [@filewalkwithme](https://github.com/filewalkwithme)
15
26
***Api**: Delete nonexistent datasource should return 404 [#12313](https://github.com/grafana/grafana/issues/12313), thx [@AustinWinstanley](https://github.com/AustinWinstanley)
16
27
***Dashboard**: Fix selecting current dashboard from search should not reload dashboard [#12248](https://github.com/grafana/grafana/issues/12248)
17
28
***Dashboard**: Use uid when linking to dashboards internally in a dashboard [#10705](https://github.com/grafana/grafana/issues/10705)
@@ -41,7 +52,6 @@
41
52
***Cloudwatch**: Add new Redshift metrics and dimensions [#12063](https://github.com/grafana/grafana/pulls/12063), thx [@A21z](https://github.com/A21z)
42
53
***Table**: Adjust header contrast for the light theme [#12668](https://github.com/grafana/grafana/issues/12668)
43
54
***Table**: Fix link color when using light theme and thresholds in use [#12766](https://github.com/grafana/grafana/issues/12766)
44
-
om/grafana/grafana/issues/12668)
45
55
***Table**: Fix for useless horizontal scrollbar for table panel [#9964](https://github.com/grafana/grafana/issues/9964)
46
56
***Table**: Make table sorting stable when null values exist [#12362](https://github.com/grafana/grafana/pull/12362), thx [@bz2](https://github.com/bz2)
47
57
***Elasticsearch**: For alerting/backend, support having index name to the right of pattern in index pattern [#12731](https://github.com/grafana/grafana/issues/12731)
***InfluxDB**: Support timeFilter in query templating for InfluxDB [#12598](https://github.com/grafana/grafana/pull/12598), thx [kichristensen](https://github.com/kichristensen)
58
68
***Provisioning**: Should allow one default datasource per organisation [#12229](https://github.com/grafana/grafana/issues/12229)
59
69
***Heatmap**: Fix broken tooltip and crosshair on Firefox [#12486](https://github.com/grafana/grafana/issues/12486)
70
+
***Login**: Show loading animation while waiting for authentication response on login [#12865](https://github.com/grafana/grafana/issues/12865)
60
71
61
72
### Breaking changes
62
73
63
74
* Postgres datasource no longer automatically adds time column alias when using the $__timeGroup alias. However, there's code in place which should make this change backward compatible and shouldn't create any issues.
75
+
* Kiosk mode now also hides submenu (variables)
76
+
* ?inactive url parameter no longer supported, replaced with kiosk=tv url parameter
64
77
65
78
### New experimental features
66
79
@@ -72,6 +85,12 @@ These are new features that's still being worked on and are in an experimental p
72
85
73
86
***Frontend**: Convert all Frontend Karma tests to Jest tests [#12224](https://github.com/grafana/grafana/issues/12224)
74
87
88
+
# 5.2.3 (2018-08-29)
89
+
90
+
### Important fix for LDAP & OAuth login vulnerability
91
+
92
+
See [security announcement](https://community.grafana.com/t/grafana-5-2-3-and-4-6-4-security-update/10050) for details.
93
+
75
94
# 5.2.2 (2018-07-25)
76
95
77
96
### Minor
@@ -440,6 +459,12 @@ The following properties have been deprecated and will be removed in a future re
440
459
-`uri` property in `GET /api/search` -> Use new `url` or `uid` property instead
441
460
-`meta.slug` property in `GET /api/dashboards/uid/:uid` and `GET /api/dashboards/db/:slug` -> Use new `meta.url` or `dashboard.uid` property instead
442
461
462
+
# 4.6.4 (2018-08-29)
463
+
464
+
### Important fix for LDAP & OAuth login vulnerability
465
+
466
+
See [security announcement](https://community.grafana.com/t/grafana-5-2-3-and-4-6-4-security-update/10050) for details.
When this option is checked additional notifications (reminders) will be sent for triggered alerts. You can specify how often reminders
41
+
should be sent using number of seconds (s), minutes (m) or hours (h), for example `30s`, `3m`, `5m` or `1h` etc.
42
+
43
+
**Important:** Alert reminders are sent after rules are evaluated. Therefore a reminder can never be sent more frequently than a configured [alert rule evaluation interval](/alerting/rules/#name-evaluation-interval).
44
+
45
+
These examples show how often and when reminders are sent for a triggered alert.
46
+
47
+
Alert rule evaluation interval | Send reminders every | Reminder sent every (after last alert notification)
48
+
---------- | ----------- | -----------
49
+
`30s` | `15s` | ~30 seconds
50
+
`1m` | `5m` | ~5 minutes
51
+
`5m` | `15m` | ~15 minutes
52
+
`6m` | `20m` | ~24 minutes
53
+
`1h` | `15m` | ~1 hour
54
+
`1h` | `2h` | ~2 hours
55
+
56
+
<divclass="clearfix"></div>
34
57
35
58
## Supported Notification Types
36
59
@@ -132,23 +155,23 @@ Once these two properties are set, you can send the alerts to Kafka for further
132
155
133
156
### All supported notifiers
134
157
135
-
Name | Type |Support images
136
-
-----|------------ | ------
137
-
Slack | `slack` | yes
138
-
Pagerduty | `pagerduty` | yes
139
-
Email | `email` | yes
140
-
Webhook | `webhook` | link
141
-
Kafka | `kafka` | no
142
-
Hipchat | `hipchat` | yes
143
-
VictorOps | `victorops` | yes
144
-
Sensu | `sensu` | yes
145
-
OpsGenie | `opsgenie` | yes
146
-
Threema | `threema` | yes
147
-
Pushover | `pushover` | no
148
-
Telegram | `telegram` | no
149
-
Line | `line` | no
150
-
Prometheus Alertmanager | `prometheus-alertmanager` | no
151
-
Microsoft Teams | `teams` | yes
158
+
Name | Type |Support images | Support reminders
159
+
-----|------------ | ------ | ------ |
160
+
Slack | `slack` | yes | yes
161
+
Pagerduty | `pagerduty` | yes | yes
162
+
Email | `email` | yes | yes
163
+
Webhook | `webhook` | link | yes
164
+
Kafka | `kafka` | no | yes
165
+
Hipchat | `hipchat` | yes | yes
166
+
VictorOps | `victorops` | yes | yes
167
+
Sensu | `sensu` | yes | yes
168
+
OpsGenie | `opsgenie` | yes | yes
169
+
Threema | `threema` | yes | yes
170
+
Pushover | `pushover` | no | yes
171
+
Telegram | `telegram` | no | yes
172
+
Line | `line` | no | yes
173
+
Microsoft Teams | `teams` | yes | yes
174
+
Prometheus Alertmanager | `prometheus-alertmanager` | no | no
Copy file name to clipboardExpand all lines: docs/sources/alerting/rules.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,6 +88,11 @@ So as you can see from the above scenario Grafana will not send out notification
88
88
to fire if the rule already is in state `Alerting`. To improve support for queries that return multiple series
89
89
we plan to track state **per series** in a future release.
90
90
91
+
> Starting with Grafana v5.3 you can configure reminders to be sent for triggered alerts. This will send additional notifications
92
+
> when an alert continues to fire. If other series (like server2 in the example above) also cause the alert rule to fire they will
93
+
> be included in the reminder notification. Depending on what notification channel you're using you may be able to take advantage
94
+
> of this feature for identifying new/existing series causing alert to fire. [Read more about notification reminders here](/alerting/notifications/#send-reminders).
95
+
91
96
### No Data / Null values
92
97
93
98
Below your conditions you can configure how the rule evaluation engine should handle queries that return no data or only null values.
Copy file name to clipboardExpand all lines: docs/sources/features/datasources/postgres.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,9 @@ Name | Description
31
31
*User* | Database user's login/username
32
32
*Password* | Database user's password
33
33
*SSL Mode* | This option determines whether or with what priority a secure SSL TCP/IP connection will be negotiated with the server.
34
-
*TimescaleDB* | With this option enabled Grafana will use TimescaleDB features, e.g. use ```time_bucket``` for grouping by time (only available in Grafana 5.3+).
34
+
*Version* | This option determines which functions are available in the query builder (only available in Grafana 5.3+).
35
+
*TimescaleDB* | TimescaleDB is a time-series database built as a PostgreSQL extension. If enabled, Grafana will use `time_bucket` in the `$__timeGroup` macro and display TimescaleDB specific aggregate functions in the query builder (only available in Grafana 5.3+).
Copy file name to clipboardExpand all lines: docs/sources/guides/getting_started.md
+29-1Lines changed: 29 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,35 @@ weight = 1
13
13
14
14
# Getting started
15
15
16
-
This guide will help you get started and acquainted with Grafana. It assumes you have a working Grafana server up and running and have added at least one [Data Source](/features/datasources/).
16
+
This guide will help you get started and acquainted with Grafana. It assumes you have a working Grafana server up and running. If not please read the [installation guide](/installation/).
17
+
18
+
## Logging in for the first time
19
+
20
+
To run Grafana open your browser and go to http://localhost:3000/. 3000 is the default http port that Grafana listens to if you haven't [configured a different port](/installation/configuration/#http-port).
21
+
22
+
There you will see the login page. Default username is admin and default password is admin. When you log in for the first time you will be asked to change your password. We strongly encourage you to
23
+
follow Grafana’s best practices and change the default administrator password. You can later go to user preferences and change your user name.
Before you create your first dashboard you need to add your data source.
31
+
32
+
First move your cursor to the cog on the side menu which will show you the configuration menu. If the side menu is not visible click the Grafana icon in the upper left corner. The first item on the configuration menu is data sources, click on that and you'll be taken to the data sources page where you can add and edit data sources. You can also simply click the cog.
33
+
34
+
35
+
Click Add data source and you will come to the settings page of your new data source.
First, give the data source a Name and then select which Type of data source you'll want to create, see [Supported data sources](/features/datasources/#supported-data-sources/) for more information and how to configure your data source.
0 commit comments