diff --git a/.betterer.results b/.betterer.results index c5d0b69eb13..7f8ff5acfac 100644 --- a/.betterer.results +++ b/.betterer.results @@ -83,7 +83,7 @@ exports[`no enzyme tests`] = { "public/app/features/dimensions/editors/ThresholdsEditor/ThresholdsEditor.test.tsx:4164297658": [ [0, 17, 13, "RegExp match", "2409514259"] ], - "public/app/features/folders/FolderSettingsPage.test.tsx:1109052730": [ + "public/app/features/folders/FolderSettingsPage.test.tsx:1208063654": [ [0, 19, 13, "RegExp match", "2409514259"] ], "public/app/plugins/datasource/cloudwatch/components/ConfigEditor.test.tsx:4057721851": [ @@ -115,9 +115,6 @@ exports[`no enzyme tests`] = { ], "public/app/plugins/datasource/prometheus/configuration/AzureCredentialsForm.test.tsx:3424320489": [ [0, 19, 13, "RegExp match", "2409514259"] - ], - "public/app/plugins/panel/bargauge/BarGaugePanel.test.tsx:3368730691": [ - [0, 31, 13, "RegExp match", "2409514259"] ] }` }; @@ -4366,12 +4363,6 @@ exports[`better eslint`] = { [0, 0, 0, "Unexpected any. Specify a different type.", "0"], [0, 0, 0, "Unexpected any. Specify a different type.", "1"] ], - "public/app/features/dashboard/components/SubMenu/DashboardLinksDashboard.tsx:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"], - [0, 0, 0, "Unexpected any. Specify a different type.", "2"], - [0, 0, 0, "Unexpected any. Specify a different type.", "3"] - ], "public/app/features/dashboard/components/SubMenu/SubMenu.tsx:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"] ], @@ -4765,16 +4756,16 @@ exports[`better eslint`] = { [0, 0, 0, "Unexpected any. Specify a different type.", "10"], [0, 0, 0, "Unexpected any. Specify a different type.", "11"] ], - "public/app/features/datasources/DataSourceDashboards.tsx:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"] - ], - "public/app/features/datasources/__mocks__/dataSourcesMocks.ts:5381": [ - [0, 0, 0, "Do not use any type assertions.", "0"] - ], - "public/app/features/datasources/settings/ButtonRow.tsx:5381": [ + "public/app/features/datasources/components/ButtonRow.tsx:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"], [0, 0, 0, "Unexpected any. Specify a different type.", "1"] ], + "public/app/features/datasources/passwordHandlers.test.ts:5381": [ + [0, 0, 0, "Unexpected any. Specify a different type.", "0"] + ], + "public/app/features/datasources/passwordHandlers.ts:5381": [ + [0, 0, 0, "Unexpected any. Specify a different type.", "0"] + ], "public/app/features/datasources/state/actions.test.ts:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"], [0, 0, 0, "Unexpected any. Specify a different type.", "1"], @@ -4799,12 +4790,6 @@ exports[`better eslint`] = { [0, 0, 0, "Do not use any type assertions.", "0"], [0, 0, 0, "Do not use any type assertions.", "1"] ], - "public/app/features/datasources/utils/passwordHandlers.test.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"] - ], - "public/app/features/datasources/utils/passwordHandlers.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"] - ], "public/app/features/dimensions/color.ts:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"] ], @@ -5377,15 +5362,7 @@ exports[`better eslint`] = { [0, 0, 0, "Unexpected any. Specify a different type.", "0"], [0, 0, 0, "Unexpected any. Specify a different type.", "1"], [0, 0, 0, "Unexpected any. Specify a different type.", "2"], - [0, 0, 0, "Unexpected any. Specify a different type.", "3"], - [0, 0, 0, "Unexpected any. Specify a different type.", "4"] - ], - "public/app/features/playlist/PlaylistNewPage.test.tsx:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"], - [0, 0, 0, "Unexpected any. Specify a different type.", "2"], - [0, 0, 0, "Unexpected any. Specify a different type.", "3"], - [0, 0, 0, "Unexpected any. Specify a different type.", "4"] + [0, 0, 0, "Unexpected any. Specify a different type.", "3"] ], "public/app/features/playlist/PlaylistSrv.test.ts:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"], @@ -5475,9 +5452,6 @@ exports[`better eslint`] = { [0, 0, 0, "Do not use any type assertions.", "2"], [0, 0, 0, "Do not use any type assertions.", "3"] ], - "public/app/features/plugins/admin/state/reducer.ts:5381": [ - [0, 0, 0, "Do not use any type assertions.", "0"] - ], "public/app/features/plugins/admin/state/selectors.ts:5381": [ [0, 0, 0, "Do not use any type assertions.", "0"] ], @@ -5517,11 +5491,8 @@ exports[`better eslint`] = { [0, 0, 0, "Unexpected any. Specify a different type.", "20"], [0, 0, 0, "Do not use any type assertions.", "21"], [0, 0, 0, "Unexpected any. Specify a different type.", "22"], - [0, 0, 0, "Do not use any type assertions.", "23"], - [0, 0, 0, "Do not use any type assertions.", "24"], - [0, 0, 0, "Do not use any type assertions.", "25"], - [0, 0, 0, "Unexpected any. Specify a different type.", "26"], - [0, 0, 0, "Do not use any type assertions.", "27"] + [0, 0, 0, "Unexpected any. Specify a different type.", "23"], + [0, 0, 0, "Do not use any type assertions.", "24"] ], "public/app/features/plugins/hooks/tests/useImportAppPlugin.test.tsx:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"], @@ -5551,11 +5522,39 @@ exports[`better eslint`] = { [0, 0, 0, "Do not use any type assertions.", "7"], [0, 0, 0, "Do not use any type assertions.", "8"] ], + "public/app/features/plugins/sql/components/query-editor-raw/SQLEditor.tsx:5381": [ + [0, 0, 0, "Unexpected any. Specify a different type.", "0"], + [0, 0, 0, "Do not use any type assertions.", "1"], + [0, 0, 0, "Do not use any type assertions.", "2"], + [0, 0, 0, "Do not use any type assertions.", "3"], + [0, 0, 0, "Do not use any type assertions.", "4"], + [0, 0, 0, "Do not use any type assertions.", "5"] + ], "public/app/features/plugins/sql/components/visual-query-builder/AwesomeQueryBuilder.tsx:5381": [ [0, 0, 0, "Do not use any type assertions.", "0"], [0, 0, 0, "Do not use any type assertions.", "1"], [0, 0, 0, "Unexpected any. Specify a different type.", "2"] ], + "public/app/features/plugins/sql/mocks/Monaco.ts:5381": [ + [0, 0, 0, "Unexpected any. Specify a different type.", "0"] + ], + "public/app/features/plugins/sql/mocks/queries/singleLineFullQuery.ts:5381": [ + [0, 0, 0, "Do not use any type assertions.", "0"] + ], + "public/app/features/plugins/sql/standardSql/definition.ts:5381": [ + [0, 0, 0, "Unexpected any. Specify a different type.", "0"] + ], + "public/app/features/plugins/sql/test-utils/statementPosition.ts:5381": [ + [0, 0, 0, "Unexpected any. Specify a different type.", "0"], + [0, 0, 0, "Do not use any type assertions.", "1"], + [0, 0, 0, "Unexpected any. Specify a different type.", "2"], + [0, 0, 0, "Do not use any type assertions.", "3"] + ], + "public/app/features/plugins/sql/utils/debugger.ts:5381": [ + [0, 0, 0, "Unexpected any. Specify a different type.", "0"], + [0, 0, 0, "Do not use any type assertions.", "1"], + [0, 0, 0, "Unexpected any. Specify a different type.", "2"] + ], "public/app/features/plugins/tests/datasource_srv.test.ts:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"], [0, 0, 0, "Unexpected any. Specify a different type.", "1"], @@ -5719,35 +5718,24 @@ exports[`better eslint`] = { [0, 0, 0, "Unexpected any. Specify a different type.", "1"] ], "public/app/features/scenes/core/SceneObjectBase.tsx:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], + [0, 0, 0, "Do not use any type assertions.", "0"], [0, 0, 0, "Do not use any type assertions.", "1"], - [0, 0, 0, "Do not use any type assertions.", "2"], - [0, 0, 0, "Unexpected any. Specify a different type.", "3"], - [0, 0, 0, "Do not use any type assertions.", "4"], + [0, 0, 0, "Unexpected any. Specify a different type.", "2"], + [0, 0, 0, "Do not use any type assertions.", "3"], + [0, 0, 0, "Unexpected any. Specify a different type.", "4"], [0, 0, 0, "Do not use any type assertions.", "5"], - [0, 0, 0, "Unexpected any. Specify a different type.", "6"], - [0, 0, 0, "Do not use any type assertions.", "7"], - [0, 0, 0, "Unexpected any. Specify a different type.", "8"], - [0, 0, 0, "Do not use any type assertions.", "9"], - [0, 0, 0, "Unexpected any. Specify a different type.", "10"] + [0, 0, 0, "Unexpected any. Specify a different type.", "6"] ], "public/app/features/scenes/core/SceneTimeRange.tsx:5381": [ [0, 0, 0, "Do not use any type assertions.", "0"], [0, 0, 0, "Unexpected any. Specify a different type.", "1"] ], - "public/app/features/scenes/core/events.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"], - [0, 0, 0, "Unexpected any. Specify a different type.", "2"] - ], "public/app/features/scenes/core/types.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"] + [0, 0, 0, "Unexpected any. Specify a different type.", "0"] ], "public/app/features/scenes/editor/SceneObjectTree.tsx:5381": [ [0, 0, 0, "Do not use any type assertions.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"], - [0, 0, 0, "Do not use any type assertions.", "2"] + [0, 0, 0, "Unexpected any. Specify a different type.", "1"] ], "public/app/features/scenes/querying/SceneQueryRunner.ts:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"], @@ -7678,8 +7666,7 @@ exports[`better eslint`] = { [0, 0, 0, "Unexpected any. Specify a different type.", "10"], [0, 0, 0, "Unexpected any. Specify a different type.", "11"], [0, 0, 0, "Unexpected any. Specify a different type.", "12"], - [0, 0, 0, "Unexpected any. Specify a different type.", "13"], - [0, 0, 0, "Unexpected any. Specify a different type.", "14"] + [0, 0, 0, "Unexpected any. Specify a different type.", "13"] ], "public/app/plugins/datasource/loki/datasource.ts:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"], @@ -7688,8 +7675,7 @@ exports[`better eslint`] = { [0, 0, 0, "Unexpected any. Specify a different type.", "3"], [0, 0, 0, "Unexpected any. Specify a different type.", "4"], [0, 0, 0, "Unexpected any. Specify a different type.", "5"], - [0, 0, 0, "Unexpected any. Specify a different type.", "6"], - [0, 0, 0, "Unexpected any. Specify a different type.", "7"] + [0, 0, 0, "Unexpected any. Specify a different type.", "6"] ], "public/app/plugins/datasource/loki/getDerivedFields.ts:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"], @@ -7778,171 +7764,15 @@ exports[`better eslint`] = { [0, 0, 0, "Do not use any type assertions.", "1"], [0, 0, 0, "Do not use any type assertions.", "2"] ], - "public/app/plugins/datasource/mssql/datasource.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"], - [0, 0, 0, "Do not use any type assertions.", "2"], - [0, 0, 0, "Unexpected any. Specify a different type.", "3"], - [0, 0, 0, "Unexpected any. Specify a different type.", "4"], - [0, 0, 0, "Unexpected any. Specify a different type.", "5"], - [0, 0, 0, "Unexpected any. Specify a different type.", "6"], - [0, 0, 0, "Unexpected any. Specify a different type.", "7"], - [0, 0, 0, "Do not use any type assertions.", "8"], - [0, 0, 0, "Unexpected any. Specify a different type.", "9"] - ], - "public/app/plugins/datasource/mssql/module.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"] - ], - "public/app/plugins/datasource/mssql/query_ctrl.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"], - [0, 0, 0, "Unexpected any. Specify a different type.", "2"], - [0, 0, 0, "Unexpected any. Specify a different type.", "3"] - ], - "public/app/plugins/datasource/mssql/response_parser.ts:5381": [ - [0, 0, 0, "Do not use any type assertions.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"], - [0, 0, 0, "Do not use any type assertions.", "2"] - ], - "public/app/plugins/datasource/mssql/specs/datasource.test.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"], - [0, 0, 0, "Unexpected any. Specify a different type.", "2"], - [0, 0, 0, "Unexpected any. Specify a different type.", "3"], - [0, 0, 0, "Unexpected any. Specify a different type.", "4"], - [0, 0, 0, "Unexpected any. Specify a different type.", "5"], - [0, 0, 0, "Unexpected any. Specify a different type.", "6"], - [0, 0, 0, "Unexpected any. Specify a different type.", "7"], - [0, 0, 0, "Unexpected any. Specify a different type.", "8"] - ], - "public/app/plugins/datasource/mssql/types.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"], - [0, 0, 0, "Unexpected any. Specify a different type.", "2"], - [0, 0, 0, "Unexpected any. Specify a different type.", "3"], - [0, 0, 0, "Unexpected any. Specify a different type.", "4"], - [0, 0, 0, "Unexpected any. Specify a different type.", "5"] - ], - "public/app/plugins/datasource/mysql/datasource.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"], - [0, 0, 0, "Do not use any type assertions.", "2"], - [0, 0, 0, "Unexpected any. Specify a different type.", "3"], - [0, 0, 0, "Unexpected any. Specify a different type.", "4"], - [0, 0, 0, "Unexpected any. Specify a different type.", "5"], - [0, 0, 0, "Do not use any type assertions.", "6"], - [0, 0, 0, "Unexpected any. Specify a different type.", "7"], - [0, 0, 0, "Unexpected any. Specify a different type.", "8"], - [0, 0, 0, "Unexpected any. Specify a different type.", "9"], - [0, 0, 0, "Unexpected any. Specify a different type.", "10"], - [0, 0, 0, "Unexpected any. Specify a different type.", "11"] - ], - "public/app/plugins/datasource/mysql/meta_query.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"] - ], - "public/app/plugins/datasource/mysql/module.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"] - ], - "public/app/plugins/datasource/mysql/mysql_query_model.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"], - [0, 0, 0, "Unexpected any. Specify a different type.", "2"], - [0, 0, 0, "Unexpected any. Specify a different type.", "3"], - [0, 0, 0, "Unexpected any. Specify a different type.", "4"], - [0, 0, 0, "Unexpected any. Specify a different type.", "5"], - [0, 0, 0, "Unexpected any. Specify a different type.", "6"], - [0, 0, 0, "Unexpected any. Specify a different type.", "7"], - [0, 0, 0, "Unexpected any. Specify a different type.", "8"], - [0, 0, 0, "Unexpected any. Specify a different type.", "9"], - [0, 0, 0, "Unexpected any. Specify a different type.", "10"], - [0, 0, 0, "Unexpected any. Specify a different type.", "11"], - [0, 0, 0, "Unexpected any. Specify a different type.", "12"], - [0, 0, 0, "Unexpected any. Specify a different type.", "13"], - [0, 0, 0, "Unexpected any. Specify a different type.", "14"], - [0, 0, 0, "Unexpected any. Specify a different type.", "15"] - ], - "public/app/plugins/datasource/mysql/query_ctrl.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"], - [0, 0, 0, "Unexpected any. Specify a different type.", "2"], - [0, 0, 0, "Unexpected any. Specify a different type.", "3"], - [0, 0, 0, "Unexpected any. Specify a different type.", "4"], - [0, 0, 0, "Unexpected any. Specify a different type.", "5"], - [0, 0, 0, "Unexpected any. Specify a different type.", "6"], - [0, 0, 0, "Unexpected any. Specify a different type.", "7"], - [0, 0, 0, "Unexpected any. Specify a different type.", "8"], - [0, 0, 0, "Unexpected any. Specify a different type.", "9"], - [0, 0, 0, "Unexpected any. Specify a different type.", "10"], - [0, 0, 0, "Unexpected any. Specify a different type.", "11"], - [0, 0, 0, "Unexpected any. Specify a different type.", "12"], - [0, 0, 0, "Unexpected any. Specify a different type.", "13"], - [0, 0, 0, "Unexpected any. Specify a different type.", "14"], - [0, 0, 0, "Unexpected any. Specify a different type.", "15"], - [0, 0, 0, "Unexpected any. Specify a different type.", "16"], - [0, 0, 0, "Unexpected any. Specify a different type.", "17"], - [0, 0, 0, "Unexpected any. Specify a different type.", "18"], - [0, 0, 0, "Unexpected any. Specify a different type.", "19"], - [0, 0, 0, "Unexpected any. Specify a different type.", "20"], - [0, 0, 0, "Unexpected any. Specify a different type.", "21"], - [0, 0, 0, "Unexpected any. Specify a different type.", "22"], - [0, 0, 0, "Unexpected any. Specify a different type.", "23"], - [0, 0, 0, "Do not use any type assertions.", "24"], - [0, 0, 0, "Do not use any type assertions.", "25"], - [0, 0, 0, "Unexpected any. Specify a different type.", "26"], - [0, 0, 0, "Unexpected any. Specify a different type.", "27"], - [0, 0, 0, "Unexpected any. Specify a different type.", "28"], - [0, 0, 0, "Unexpected any. Specify a different type.", "29"], - [0, 0, 0, "Unexpected any. Specify a different type.", "30"], - [0, 0, 0, "Unexpected any. Specify a different type.", "31"], - [0, 0, 0, "Unexpected any. Specify a different type.", "32"], - [0, 0, 0, "Unexpected any. Specify a different type.", "33"], - [0, 0, 0, "Unexpected any. Specify a different type.", "34"], - [0, 0, 0, "Unexpected any. Specify a different type.", "35"], - [0, 0, 0, "Unexpected any. Specify a different type.", "36"], - [0, 0, 0, "Unexpected any. Specify a different type.", "37"], - [0, 0, 0, "Unexpected any. Specify a different type.", "38"], - [0, 0, 0, "Unexpected any. Specify a different type.", "39"], - [0, 0, 0, "Unexpected any. Specify a different type.", "40"], - [0, 0, 0, "Unexpected any. Specify a different type.", "41"], - [0, 0, 0, "Unexpected any. Specify a different type.", "42"], - [0, 0, 0, "Unexpected any. Specify a different type.", "43"], - [0, 0, 0, "Unexpected any. Specify a different type.", "44"], - [0, 0, 0, "Unexpected any. Specify a different type.", "45"], - [0, 0, 0, "Unexpected any. Specify a different type.", "46"], - [0, 0, 0, "Unexpected any. Specify a different type.", "47"], - [0, 0, 0, "Unexpected any. Specify a different type.", "48"], - [0, 0, 0, "Unexpected any. Specify a different type.", "49"], - [0, 0, 0, "Unexpected any. Specify a different type.", "50"], - [0, 0, 0, "Unexpected any. Specify a different type.", "51"], - [0, 0, 0, "Unexpected any. Specify a different type.", "52"], - [0, 0, 0, "Unexpected any. Specify a different type.", "53"], - [0, 0, 0, "Unexpected any. Specify a different type.", "54"] - ], - "public/app/plugins/datasource/mysql/response_parser.ts:5381": [ - [0, 0, 0, "Do not use any type assertions.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"], - [0, 0, 0, "Do not use any type assertions.", "2"] - ], "public/app/plugins/datasource/mysql/specs/datasource.test.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"] - ], - "public/app/plugins/datasource/mysql/sql_part.ts:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"], - [0, 0, 0, "Unexpected any. Specify a different type.", "1"], - [0, 0, 0, "Unexpected any. Specify a different type.", "2"], - [0, 0, 0, "Unexpected any. Specify a different type.", "3"] + [0, 0, 0, "Unexpected any. Specify a different type.", "0"] ], "public/app/plugins/datasource/mysql/types.ts:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"], [0, 0, 0, "Unexpected any. Specify a different type.", "1"], [0, 0, 0, "Unexpected any. Specify a different type.", "2"], [0, 0, 0, "Unexpected any. Specify a different type.", "3"], - [0, 0, 0, "Unexpected any. Specify a different type.", "4"], - [0, 0, 0, "Unexpected any. Specify a different type.", "5"] + [0, 0, 0, "Unexpected any. Specify a different type.", "4"] ], "public/app/plugins/datasource/opentsdb/datasource.d.ts:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"] @@ -8405,8 +8235,7 @@ exports[`better eslint`] = { [0, 0, 0, "Unexpected any. Specify a different type.", "32"], [0, 0, 0, "Unexpected any. Specify a different type.", "33"], [0, 0, 0, "Unexpected any. Specify a different type.", "34"], - [0, 0, 0, "Unexpected any. Specify a different type.", "35"], - [0, 0, 0, "Unexpected any. Specify a different type.", "36"] + [0, 0, 0, "Unexpected any. Specify a different type.", "35"] ], "public/app/plugins/datasource/prometheus/language_provider.test.ts:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"], @@ -8886,9 +8715,6 @@ exports[`better eslint`] = { "public/app/plugins/panel/bargauge/BarGaugeMigrations.test.ts:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"] ], - "public/app/plugins/panel/bargauge/BarGaugePanel.test.tsx:5381": [ - [0, 0, 0, "Unexpected any. Specify a different type.", "0"] - ], "public/app/plugins/panel/bargauge/BarGaugePanel.tsx:5381": [ [0, 0, 0, "Unexpected any. Specify a different type.", "0"] ], diff --git a/.drone.star b/.drone.star index b9d6ab67c91..10719f988f5 100644 --- a/.drone.star +++ b/.drone.star @@ -4,12 +4,12 @@ # 3. Run `make drone` # More information about this process here: https://github.com/grafana/deployment_tools/blob/master/docs/infrastructure/drone/signing.md -load('scripts/drone/pipelines/pr.star', 'pr_pipelines') -load('scripts/drone/pipelines/main.star', 'main_pipelines') +load('scripts/drone/events/pr.star', 'pr_pipelines') +load('scripts/drone/events/main.star', 'main_pipelines') load('scripts/drone/pipelines/docs.star', 'docs_pipelines') -load('scripts/drone/pipelines/release.star', 'release_pipelines', 'publish_image_pipelines', 'publish_artifacts_pipelines', 'publish_npm_pipelines', 'publish_packages_pipeline', 'artifacts_page_pipeline') +load('scripts/drone/events/release.star', 'release_pipelines', 'publish_image_pipelines', 'publish_artifacts_pipelines', 'publish_npm_pipelines', 'publish_packages_pipeline', 'artifacts_page_pipeline') load('scripts/drone/version.star', 'version_branch_pipelines') -load('scripts/drone/pipelines/cron.star', 'cronjobs') +load('scripts/drone/events/cron.star', 'cronjobs') load('scripts/drone/vault.star', 'secrets') def main(ctx): diff --git a/.drone.yml b/.drone.yml index d83de1d157f..cb881e4910d 100644 --- a/.drone.yml +++ b/.drone.yml @@ -15,7 +15,7 @@ steps: name: identify-runner - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -58,7 +58,7 @@ steps: name: identify-runner - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -66,13 +66,13 @@ steps: - ./bin/grabpl gen-version --build-id ${DRONE_BUILD_NUMBER} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - yarn install --immutable depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - commands: - yarn run prettier:check @@ -83,14 +83,14 @@ steps: - yarn-install environment: TEST_MAX_WORKERS: 50% - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-frontend - commands: - yarn betterer ci depends_on: - yarn-install failure: ignore - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: betterer-frontend - commands: - yarn run ci:test-frontend @@ -98,7 +98,7 @@ steps: - yarn-install environment: TEST_MAX_WORKERS: 50% - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-frontend trigger: event: @@ -134,7 +134,7 @@ steps: name: identify-runner - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -142,7 +142,7 @@ steps: - ./bin/grabpl gen-version --build-id ${DRONE_BUILD_NUMBER} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - '# It is required that code generated from Thema/CUE be committed and in sync @@ -151,13 +151,13 @@ steps: in output.' - CODEGEN_VERIFY=1 make gen-cue depends_on: [] - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - make gen-go depends_on: - verify-gen-cue - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - |- @@ -169,13 +169,13 @@ steps: wan" > words_to_ignore.txt - codespell -I words_to_ignore.txt docs/ - rm words_to_ignore.txt - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: codespell - commands: - ./bin/grabpl shellcheck depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: shellcheck - commands: - make lint-go @@ -183,19 +183,19 @@ steps: - wire-install environment: CGO_ENABLED: "1" - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-backend - commands: - go test -short -covermode=atomic -timeout=30m ./pkg/... depends_on: - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-backend - commands: - go test -run Integration -covermode=atomic -timeout=30m ./pkg/... depends_on: - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-backend-integration trigger: event: @@ -234,7 +234,7 @@ steps: name: identify-runner - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -242,7 +242,7 @@ steps: - ./bin/grabpl gen-version --build-id ${DRONE_BUILD_NUMBER} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - '# It is required that code generated from Thema/CUE be committed and in sync @@ -251,19 +251,19 @@ steps: in output.' - CODEGEN_VERIFY=1 make gen-cue depends_on: [] - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - make gen-go depends_on: - verify-gen-cue - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - yarn install --immutable depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - failure: ignore image: grafana/drone-downstream @@ -283,7 +283,7 @@ steps: depends_on: - gen-version - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-backend - commands: - ./bin/grabpl build-frontend --jobs 8 --edition oss --build-id ${DRONE_BUILD_NUMBER} @@ -292,7 +292,7 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend - commands: - ./bin/grabpl build-frontend-packages --jobs 8 --edition oss --build-id ${DRONE_BUILD_NUMBER} @@ -301,7 +301,7 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend-packages - commands: - ./bin/grabpl build-plugins --jobs 8 --edition oss @@ -309,7 +309,7 @@ steps: - gen-version - yarn-install environment: null - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-plugins - commands: - . scripts/build/gpg-test-vars.sh && ./bin/grabpl package --jobs 8 --edition oss @@ -320,7 +320,7 @@ steps: - build-frontend - build-frontend-packages environment: null - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: package - commands: - ./scripts/grafana-server/start-server @@ -333,7 +333,7 @@ steps: environment: ARCH: linux-amd64 PORT: 3001 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: grafana-server - commands: - apt-get install -y netcat @@ -411,8 +411,15 @@ steps: - build-frontend-packages environment: NODE_OPTIONS: --max_old_space_size=4096 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-storybook +- commands: + - ls dist/*.tar.gz* + - cp dist/*.tar.gz* packaging/docker/ + depends_on: + - package + image: grafana/build-container:1.5.8 + name: copy-packages-for-docker - commands: - yarn wait-on http://$HOST:$PORT - pa11y-ci --config .pa11yci-pr.conf.js @@ -426,13 +433,6 @@ steps: failure: always image: grafana/docker-puppeteer:1.0.0 name: test-a11y-frontend -- commands: - - ls dist/*.tar.gz* - - cp dist/*.tar.gz* packaging/docker/ - depends_on: - - package - image: grafana/build-container:1.5.7 - name: copy-packages-for-docker - commands: - ./bin/grabpl build-docker --edition oss -archs amd64 depends_on: @@ -491,7 +491,7 @@ services: steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -506,13 +506,13 @@ steps: in output.' - CODEGEN_VERIFY=1 make gen-cue depends_on: [] - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - make gen-go depends_on: - verify-gen-cue - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - apt-get update @@ -528,7 +528,7 @@ steps: GRAFANA_TEST_DB: postgres PGPASSWORD: grafanatest POSTGRES_HOST: postgres - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: postgres-integration-tests - commands: - apt-get update @@ -544,7 +544,7 @@ steps: environment: GRAFANA_TEST_DB: mysql MYSQL_HOST: mysql - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: mysql-integration-tests trigger: event: @@ -578,7 +578,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -590,13 +590,13 @@ steps: - ./bin/grabpl gen-version --build-id ${DRONE_BUILD_NUMBER} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - yarn install --immutable depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - commands: - |- @@ -608,7 +608,7 @@ steps: wan" > words_to_ignore.txt - codespell -I words_to_ignore.txt docs/ - rm words_to_ignore.txt - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: codespell - commands: - yarn run prettier:checkDocs @@ -616,7 +616,7 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-docs - commands: - ./bin/grabpl build-frontend-packages --jobs 8 --edition oss --build-id ${DRONE_BUILD_NUMBER} @@ -625,13 +625,13 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend-packages - commands: - ./scripts/ci-reference-docs-lint.sh ci depends_on: - build-frontend-packages - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend-docs - commands: - mkdir -p /hugo/content/docs/grafana @@ -668,7 +668,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -680,13 +680,13 @@ steps: - ./bin/grabpl gen-version --build-id ${DRONE_BUILD_NUMBER} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - yarn install --immutable depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - commands: - |- @@ -698,7 +698,7 @@ steps: wan" > words_to_ignore.txt - codespell -I words_to_ignore.txt docs/ - rm words_to_ignore.txt - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: codespell - commands: - yarn run prettier:checkDocs @@ -706,7 +706,7 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-docs - commands: - ./bin/grabpl build-frontend-packages --jobs 8 --edition oss --build-id ${DRONE_BUILD_NUMBER} @@ -715,13 +715,13 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend-packages - commands: - ./scripts/ci-reference-docs-lint.sh ci depends_on: - build-frontend-packages - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend-docs - commands: - mkdir -p /hugo/content/docs/grafana @@ -757,7 +757,7 @@ steps: name: identify-runner - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -765,13 +765,13 @@ steps: - ./bin/grabpl gen-version --build-id ${DRONE_BUILD_NUMBER} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - yarn install --immutable depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - commands: - yarn run prettier:check @@ -782,14 +782,14 @@ steps: - yarn-install environment: TEST_MAX_WORKERS: 50% - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-frontend - commands: - yarn betterer ci depends_on: - yarn-install failure: ignore - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: betterer-frontend - commands: - yarn run ci:test-frontend @@ -797,7 +797,7 @@ steps: - yarn-install environment: TEST_MAX_WORKERS: 50% - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-frontend trigger: branch: main @@ -825,7 +825,7 @@ steps: name: identify-runner - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -833,7 +833,7 @@ steps: - ./bin/grabpl gen-version --build-id ${DRONE_BUILD_NUMBER} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - '# It is required that code generated from Thema/CUE be committed and in sync @@ -842,20 +842,14 @@ steps: in output.' - CODEGEN_VERIFY=1 make gen-cue depends_on: [] - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - make gen-go depends_on: - verify-gen-cue - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install -- commands: - - ./bin/grabpl verify-drone - depends_on: - - grabpl - image: byrnedo/alpine-curl:0.1.8 - name: lint-drone - commands: - |- echo -e "unknwon @@ -866,13 +860,13 @@ steps: wan" > words_to_ignore.txt - codespell -I words_to_ignore.txt docs/ - rm words_to_ignore.txt - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: codespell - commands: - ./bin/grabpl shellcheck depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: shellcheck - commands: - make lint-go @@ -880,20 +874,26 @@ steps: - wire-install environment: CGO_ENABLED: "1" - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-backend - commands: - go test -short -covermode=atomic -timeout=30m ./pkg/... depends_on: - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-backend - commands: - go test -run Integration -covermode=atomic -timeout=30m ./pkg/... depends_on: - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-backend-integration +- commands: + - ./bin/grabpl verify-drone + depends_on: + - grabpl + image: byrnedo/alpine-curl:0.1.8 + name: lint-drone trigger: branch: main event: @@ -920,7 +920,7 @@ steps: name: identify-runner - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -928,7 +928,7 @@ steps: - ./bin/grabpl gen-version --build-id ${DRONE_BUILD_NUMBER} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - '# It is required that code generated from Thema/CUE be committed and in sync @@ -937,19 +937,19 @@ steps: in output.' - CODEGEN_VERIFY=1 make gen-cue depends_on: [] - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - make gen-go depends_on: - verify-gen-cue - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - yarn install --immutable depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - commands: - git clone "https://$${GITHUB_TOKEN}@github.com/grafana/grafana-enterprise.git" @@ -970,7 +970,7 @@ steps: from_secret: github_token TEST_TAG: v0.0.0-test failure: ignore - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: trigger-test-release when: paths: @@ -994,7 +994,7 @@ steps: depends_on: - gen-version - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-backend - commands: - ./bin/grabpl build-frontend --jobs 8 --edition oss --build-id ${DRONE_BUILD_NUMBER} @@ -1003,7 +1003,7 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend - commands: - ./bin/grabpl build-frontend-packages --jobs 8 --edition oss --build-id ${DRONE_BUILD_NUMBER} @@ -1012,7 +1012,7 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend-packages - commands: - ./bin/grabpl build-plugins --jobs 8 --edition oss @@ -1022,7 +1022,7 @@ steps: environment: GRAFANA_API_KEY: from_secret: grafana_api_key - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-plugins - commands: - ./bin/grabpl package --jobs 8 --edition oss --build-id ${DRONE_BUILD_NUMBER} --sign @@ -1040,7 +1040,7 @@ steps: from_secret: gpg_pub_key GRAFANA_API_KEY: from_secret: grafana_api_key - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: package - commands: - ./scripts/grafana-server/start-server @@ -1053,7 +1053,7 @@ steps: environment: ARCH: linux-amd64 PORT: 3001 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: grafana-server - commands: - apt-get install -y netcat @@ -1131,26 +1131,15 @@ steps: - build-frontend-packages environment: NODE_OPTIONS: --max_old_space_size=4096 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-storybook - commands: - - ./bin/grabpl store-storybook --deployment canary --src-bucket grafana-storybook + - ls dist/*.tar.gz* + - cp dist/*.tar.gz* packaging/docker/ depends_on: - - build-storybook - - end-to-end-tests-dashboards-suite - - end-to-end-tests-panels-suite - - end-to-end-tests-smoke-tests-suite - - end-to-end-tests-various-suite - environment: - GCP_KEY: - from_secret: gcp_key - PRERELEASE_BUCKET: - from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 - name: store-storybook - when: - repo: - - grafana/grafana + - package + image: grafana/build-container:1.5.8 + name: copy-packages-for-docker - commands: - yarn wait-on http://$HOST:$PORT - pa11y-ci --config .pa11yci.conf.js --json > pa11y-ci-results.json @@ -1164,6 +1153,24 @@ steps: failure: ignore image: grafana/docker-puppeteer:1.0.0 name: test-a11y-frontend +- commands: + - ./bin/grabpl store-storybook --deployment canary --src-bucket grafana-storybook + depends_on: + - build-storybook + - end-to-end-tests-dashboards-suite + - end-to-end-tests-panels-suite + - end-to-end-tests-smoke-tests-suite + - end-to-end-tests-various-suite + environment: + GCP_KEY: + from_secret: gcp_key + PRERELEASE_BUCKET: + from_secret: prerelease_bucket + image: grafana/grafana-ci-deploy:1.3.3 + name: store-storybook + when: + repo: + - grafana/grafana - commands: - ./scripts/ci-frontend-metrics.sh | ./bin/grabpl publish-metrics $${GRAFANA_MISC_STATS_API_KEY} depends_on: @@ -1172,18 +1179,11 @@ steps: GRAFANA_MISC_STATS_API_KEY: from_secret: grafana_misc_stats_api_key failure: ignore - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: publish-frontend-metrics when: repo: - grafana/grafana -- commands: - - ls dist/*.tar.gz* - - cp dist/*.tar.gz* packaging/docker/ - depends_on: - - package - image: grafana/build-container:1.5.7 - name: copy-packages-for-docker - commands: - ./bin/grabpl build-docker --edition oss depends_on: @@ -1260,7 +1260,7 @@ steps: environment: NPM_TOKEN: from_secret: npm_token - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: release-canary-npm-packages when: repo: @@ -1277,7 +1277,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: upload-packages when: repo: @@ -1291,7 +1291,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: upload-cdn-assets when: repo: @@ -1305,12 +1305,6 @@ volumes: - host: path: /var/run/docker.sock name: docker -- name: postgres - temp: - medium: memory -- name: mysql - temp: - medium: memory --- depends_on: [] kind: pipeline @@ -1344,7 +1338,7 @@ services: steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -1359,13 +1353,13 @@ steps: in output.' - CODEGEN_VERIFY=1 make gen-cue depends_on: [] - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - make gen-go depends_on: - verify-gen-cue - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - apt-get update @@ -1381,7 +1375,7 @@ steps: GRAFANA_TEST_DB: postgres PGPASSWORD: grafanatest POSTGRES_HOST: postgres - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: postgres-integration-tests - commands: - apt-get update @@ -1397,7 +1391,7 @@ steps: environment: GRAFANA_TEST_DB: mysql MYSQL_HOST: mysql - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: mysql-integration-tests trigger: branch: main @@ -1434,7 +1428,7 @@ steps: name: identify-runner - commands: - $$ProgressPreference = "SilentlyContinue" - - Invoke-WebRequest https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/windows/grabpl.exe + - Invoke-WebRequest https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/windows/grabpl.exe -OutFile grabpl.exe image: grafana/ci-wix:0.1.1 name: windows-init @@ -1522,7 +1516,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -1530,7 +1524,7 @@ steps: - ./bin/grabpl gen-version --build-id ${DRONE_BUILD_NUMBER} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - echo $DRONE_RUNNER_NAME @@ -1552,7 +1546,7 @@ steps: from_secret: gpg_pub_key GRAFANA_COM_API_KEY: from_secret: grafana_api_key - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: store-packages-oss trigger: branch: main @@ -1613,7 +1607,7 @@ steps: name: identify-runner - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -1621,7 +1615,7 @@ steps: - ./bin/grabpl gen-version ${DRONE_TAG} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - '# It is required that code generated from Thema/CUE be committed and in sync @@ -1630,26 +1624,26 @@ steps: in output.' - CODEGEN_VERIFY=1 make gen-cue depends_on: [] - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - make gen-go depends_on: - verify-gen-cue - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - yarn install --immutable depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - commands: - ./bin/grabpl build-backend --jobs 8 --edition oss ${DRONE_TAG} depends_on: - gen-version - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-backend - commands: - ./bin/grabpl build-frontend --jobs 8 --edition oss ${DRONE_TAG} @@ -1658,7 +1652,7 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend - commands: - ./bin/grabpl build-frontend-packages --jobs 8 --edition oss ${DRONE_TAG} @@ -1667,7 +1661,7 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend-packages - commands: - ./bin/grabpl build-plugins --jobs 8 --edition oss @@ -1677,7 +1671,7 @@ steps: environment: GRAFANA_API_KEY: from_secret: grafana_api_key - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-plugins - commands: - ./bin/grabpl package --jobs 8 --edition oss --sign ${DRONE_TAG} @@ -1695,14 +1689,14 @@ steps: from_secret: gpg_pub_key GRAFANA_API_KEY: from_secret: grafana_api_key - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: package - commands: - ls dist/*.tar.gz* - cp dist/*.tar.gz* packaging/docker/ depends_on: - package - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: copy-packages-for-docker - commands: - ./bin/grabpl build-docker --edition oss --shouldSave @@ -1739,7 +1733,7 @@ steps: environment: ARCH: linux-amd64 PORT: 3001 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: grafana-server - commands: - apt-get install -y netcat @@ -1817,7 +1811,7 @@ steps: - build-frontend-packages environment: NODE_OPTIONS: --max_old_space_size=4096 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-storybook - commands: - ./bin/grabpl upload-cdn --edition oss @@ -1828,7 +1822,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: upload-cdn-assets - commands: - ./bin/grabpl upload-packages --edition oss @@ -1842,7 +1836,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: upload-packages - commands: - ./bin/grabpl store-storybook --deployment latest --src-bucket grafana-prerelease @@ -1860,7 +1854,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: store-storybook - commands: - ./bin/grabpl artifacts npm store --tag ${DRONE_TAG} @@ -1871,7 +1865,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: store-npm-packages trigger: event: @@ -1910,7 +1904,7 @@ steps: name: identify-runner - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -1918,7 +1912,7 @@ steps: - ./bin/grabpl gen-version ${DRONE_TAG} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - '# It is required that code generated from Thema/CUE be committed and in sync @@ -1927,25 +1921,25 @@ steps: in output.' - CODEGEN_VERIFY=1 make gen-cue depends_on: [] - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - make gen-go depends_on: - verify-gen-cue - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - yarn install --immutable depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - commands: - ./bin/grabpl shellcheck depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: shellcheck - commands: - |- @@ -1957,7 +1951,7 @@ steps: wan" > words_to_ignore.txt - codespell -I words_to_ignore.txt docs/ - rm words_to_ignore.txt - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: codespell - commands: - make lint-go @@ -1965,7 +1959,7 @@ steps: - wire-install environment: CGO_ENABLED: "1" - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-backend - commands: - yarn run prettier:check @@ -1976,19 +1970,19 @@ steps: - yarn-install environment: TEST_MAX_WORKERS: 50% - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-frontend - commands: - go test -short -covermode=atomic -timeout=30m ./pkg/... depends_on: - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-backend - commands: - go test -run Integration -covermode=atomic -timeout=30m ./pkg/... depends_on: - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-backend-integration - commands: - yarn run ci:test-frontend @@ -1996,7 +1990,7 @@ steps: - yarn-install environment: TEST_MAX_WORKERS: 50% - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-frontend trigger: event: @@ -2045,7 +2039,7 @@ services: steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -2060,13 +2054,13 @@ steps: in output.' - CODEGEN_VERIFY=1 make gen-cue depends_on: [] - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - make gen-go depends_on: - verify-gen-cue - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - apt-get update @@ -2082,7 +2076,7 @@ steps: GRAFANA_TEST_DB: postgres PGPASSWORD: grafanatest POSTGRES_HOST: postgres - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: postgres-integration-tests - commands: - apt-get update @@ -2098,7 +2092,7 @@ steps: environment: GRAFANA_TEST_DB: mysql MYSQL_HOST: mysql - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: mysql-integration-tests trigger: event: @@ -2139,7 +2133,7 @@ steps: name: identify-runner - commands: - $$ProgressPreference = "SilentlyContinue" - - Invoke-WebRequest https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/windows/grabpl.exe + - Invoke-WebRequest https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/windows/grabpl.exe -OutFile grabpl.exe image: grafana/ci-wix:0.1.1 name: windows-init @@ -2198,7 +2192,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -2213,7 +2207,7 @@ steps: environment: GITHUB_TOKEN: from_secret: github_token - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: clone-enterprise - commands: - mv bin/grabpl /tmp/ @@ -2229,25 +2223,25 @@ steps: environment: GITHUB_TOKEN: from_secret: github_token - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: init-enterprise - commands: - make gen-go depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - yarn install --immutable depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - commands: - ./bin/grabpl gen-version ${DRONE_TAG} depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - '# It is required that code generated from Thema/CUE be committed and in sync @@ -2257,14 +2251,14 @@ steps: - CODEGEN_VERIFY=1 make gen-cue depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - ./bin/grabpl build-backend --jobs 8 --edition enterprise ${DRONE_TAG} depends_on: - gen-version - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-backend - commands: - ./bin/grabpl build-frontend --jobs 8 --edition enterprise ${DRONE_TAG} @@ -2273,7 +2267,7 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend - commands: - ./bin/grabpl build-frontend-packages --jobs 8 --edition enterprise ${DRONE_TAG} @@ -2282,7 +2276,7 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend-packages - commands: - ./bin/grabpl build-plugins --jobs 8 --edition enterprise @@ -2292,14 +2286,14 @@ steps: environment: GRAFANA_API_KEY: from_secret: grafana_api_key - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-plugins - commands: - ./bin/grabpl build-backend --jobs 8 --edition enterprise2 ${DRONE_TAG} depends_on: - gen-version - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-backend-enterprise2 - commands: - ./bin/grabpl package --jobs 8 --edition enterprise --sign ${DRONE_TAG} @@ -2318,14 +2312,14 @@ steps: from_secret: gpg_pub_key GRAFANA_API_KEY: from_secret: grafana_api_key - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: package - commands: - ls dist/*.tar.gz* - cp dist/*.tar.gz* packaging/docker/ depends_on: - package - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: copy-packages-for-docker - commands: - ./bin/grabpl build-docker --edition enterprise --shouldSave @@ -2363,7 +2357,7 @@ steps: ARCH: linux-amd64 PORT: 3001 RUNDIR: scripts/grafana-server/tmp-grafana-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: grafana-server - commands: - apt-get install -y netcat @@ -2442,7 +2436,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: upload-cdn-assets - commands: - ./bin/grabpl upload-packages --edition enterprise @@ -2453,7 +2447,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: upload-packages - commands: - ./bin/grabpl artifacts npm store --tag ${DRONE_TAG} @@ -2464,7 +2458,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: store-npm-packages - commands: - ./bin/grabpl package --jobs 8 --edition enterprise2 --sign ${DRONE_TAG} @@ -2483,7 +2477,7 @@ steps: from_secret: gpg_pub_key GRAFANA_API_KEY: from_secret: grafana_api_key - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: package-enterprise2 - commands: - ./bin/grabpl upload-cdn --edition enterprise2 @@ -2494,7 +2488,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: upload-cdn-assets-enterprise2 - commands: - ./bin/grabpl upload-packages --edition enterprise2 @@ -2505,7 +2499,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: upload-packages-enterprise2 trigger: event: @@ -2544,7 +2538,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -2559,7 +2553,7 @@ steps: environment: GITHUB_TOKEN: from_secret: github_token - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: clone-enterprise - commands: - mv bin/grabpl /tmp/ @@ -2575,25 +2569,25 @@ steps: environment: GITHUB_TOKEN: from_secret: github_token - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: init-enterprise - commands: - make gen-go depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - yarn install --immutable depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - commands: - ./bin/grabpl gen-version ${DRONE_TAG} depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - '# It is required that code generated from Thema/CUE be committed and in sync @@ -2603,7 +2597,7 @@ steps: - CODEGEN_VERIFY=1 make gen-cue depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - |- @@ -2615,7 +2609,7 @@ steps: wan" > words_to_ignore.txt - codespell -I words_to_ignore.txt docs/ - rm words_to_ignore.txt - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: codespell - commands: - make lint-go @@ -2623,7 +2617,7 @@ steps: - wire-install environment: CGO_ENABLED: "1" - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-backend - commands: - yarn run prettier:check @@ -2634,19 +2628,19 @@ steps: - yarn-install environment: TEST_MAX_WORKERS: 50% - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-frontend - commands: - go test -short -covermode=atomic -timeout=30m ./pkg/... depends_on: - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-backend - commands: - go test -run Integration -covermode=atomic -timeout=30m ./pkg/... depends_on: - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-backend-integration - commands: - yarn run ci:test-frontend @@ -2654,7 +2648,7 @@ steps: - yarn-install environment: TEST_MAX_WORKERS: 50% - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-frontend - commands: - make lint-go @@ -2662,13 +2656,13 @@ steps: - wire-install environment: CGO_ENABLED: "1" - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-backend-enterprise2 - commands: - go test -tags=pro -covermode=atomic -timeout=30m ./pkg/... depends_on: - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-backend-enterprise2 trigger: event: @@ -2727,7 +2721,7 @@ services: steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -2742,7 +2736,7 @@ steps: environment: GITHUB_TOKEN: from_secret: github_token - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: clone-enterprise - commands: - mv bin/grabpl /tmp/ @@ -2758,7 +2752,7 @@ steps: environment: GITHUB_TOKEN: from_secret: github_token - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: init-enterprise - commands: - '# It is required that code generated from Thema/CUE be committed and in sync @@ -2768,13 +2762,13 @@ steps: - CODEGEN_VERIFY=1 make gen-cue depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - make gen-go depends_on: - verify-gen-cue - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - apt-get update @@ -2790,7 +2784,7 @@ steps: GRAFANA_TEST_DB: postgres PGPASSWORD: grafanatest POSTGRES_HOST: postgres - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: postgres-integration-tests - commands: - apt-get update @@ -2806,7 +2800,7 @@ steps: environment: GRAFANA_TEST_DB: mysql MYSQL_HOST: mysql - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: mysql-integration-tests - commands: - dockerize -wait tcp://redis:6379/0 -timeout 120s @@ -2815,7 +2809,7 @@ steps: - wire-install environment: REDIS_URL: redis://redis:6379/0 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: redis-integration-tests - commands: - dockerize -wait tcp://memcached:11211 -timeout 120s @@ -2824,7 +2818,7 @@ steps: - wire-install environment: MEMCACHED_HOSTS: memcached:11211 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: memcached-integration-tests trigger: event: @@ -2869,7 +2863,7 @@ steps: name: identify-runner - commands: - $$ProgressPreference = "SilentlyContinue" - - Invoke-WebRequest https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/windows/grabpl.exe + - Invoke-WebRequest https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/windows/grabpl.exe -OutFile grabpl.exe - git clone "https://$$env:GITHUB_TOKEN@github.com/grafana/grafana-enterprise.git" - cd grafana-enterprise @@ -2944,7 +2938,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -3022,7 +3016,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -3083,7 +3077,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -3162,7 +3156,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -3224,7 +3218,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -3237,7 +3231,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: publish-artifacts trigger: event: @@ -3262,7 +3256,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -3275,7 +3269,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: publish-artifacts trigger: event: @@ -3300,7 +3294,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -3308,7 +3302,7 @@ steps: - yarn install --immutable depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - commands: - ./bin/grabpl artifacts npm retrieve --tag v${TAG} @@ -3319,7 +3313,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: retrieve-npm-packages - commands: - ./bin/grabpl artifacts npm release --tag v${TAG} @@ -3328,7 +3322,7 @@ steps: environment: NPM_TOKEN: from_secret: npm_token - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: release-npm-packages trigger: event: @@ -3356,7 +3350,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -3364,7 +3358,7 @@ steps: - ./bin/grabpl gen-version ${DRONE_TAG} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - ./bin/grabpl store-packages --edition oss --packages-bucket grafana-downloads @@ -3382,7 +3376,7 @@ steps: from_secret: gpg_pub_key GRAFANA_COM_API_KEY: from_secret: grafana_api_key - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: store-packages-oss trigger: event: @@ -3410,7 +3404,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -3418,7 +3412,7 @@ steps: - ./bin/grabpl gen-version ${DRONE_TAG} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - ./bin/grabpl store-packages --edition enterprise --packages-bucket grafana-downloads @@ -3436,7 +3430,7 @@ steps: from_secret: gpg_pub_key GRAFANA_COM_API_KEY: from_secret: grafana_api_key - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: store-packages-enterprise trigger: event: @@ -3461,7 +3455,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -3469,7 +3463,7 @@ steps: - ./bin/grabpl artifacts-page depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: artifacts-page trigger: event: @@ -3497,7 +3491,7 @@ steps: name: identify-runner - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -3505,7 +3499,7 @@ steps: - ./bin/grabpl gen-version --build-id ${DRONE_BUILD_NUMBER} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - '# It is required that code generated from Thema/CUE be committed and in sync @@ -3514,26 +3508,26 @@ steps: in output.' - CODEGEN_VERIFY=1 make gen-cue depends_on: [] - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - make gen-go depends_on: - verify-gen-cue - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - yarn install --immutable depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - commands: - ./bin/grabpl build-backend --jobs 8 --edition oss --build-id ${DRONE_BUILD_NUMBER} depends_on: - gen-version - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-backend - commands: - ./bin/grabpl build-frontend --jobs 8 --edition oss --build-id ${DRONE_BUILD_NUMBER} @@ -3542,7 +3536,7 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend - commands: - ./bin/grabpl build-frontend-packages --jobs 8 --edition oss --build-id ${DRONE_BUILD_NUMBER} @@ -3551,7 +3545,7 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend-packages - commands: - ./bin/grabpl build-plugins --jobs 8 --edition oss @@ -3561,7 +3555,7 @@ steps: environment: GRAFANA_API_KEY: from_secret: grafana_api_key - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-plugins - commands: - ./bin/grabpl package --jobs 8 --edition oss --build-id ${DRONE_BUILD_NUMBER} --sign @@ -3579,14 +3573,14 @@ steps: from_secret: gpg_pub_key GRAFANA_API_KEY: from_secret: grafana_api_key - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: package - commands: - ls dist/*.tar.gz* - cp dist/*.tar.gz* packaging/docker/ depends_on: - package - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: copy-packages-for-docker - commands: - ./bin/grabpl build-docker --edition oss --shouldSave @@ -3623,7 +3617,7 @@ steps: environment: ARCH: linux-amd64 PORT: 3001 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: grafana-server - commands: - apt-get install -y netcat @@ -3701,7 +3695,7 @@ steps: - build-frontend-packages environment: NODE_OPTIONS: --max_old_space_size=4096 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-storybook - commands: - ./bin/grabpl upload-cdn --edition oss @@ -3712,7 +3706,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: upload-cdn-assets when: repo: @@ -3729,7 +3723,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: upload-packages when: repo: @@ -3765,7 +3759,7 @@ steps: name: identify-runner - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -3773,7 +3767,7 @@ steps: - ./bin/grabpl gen-version --build-id ${DRONE_BUILD_NUMBER} depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - '# It is required that code generated from Thema/CUE be committed and in sync @@ -3782,25 +3776,25 @@ steps: in output.' - CODEGEN_VERIFY=1 make gen-cue depends_on: [] - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - make gen-go depends_on: - verify-gen-cue - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - yarn install --immutable depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - commands: - ./bin/grabpl shellcheck depends_on: - grabpl - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: shellcheck - commands: - |- @@ -3812,7 +3806,7 @@ steps: wan" > words_to_ignore.txt - codespell -I words_to_ignore.txt docs/ - rm words_to_ignore.txt - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: codespell - commands: - make lint-go @@ -3820,7 +3814,7 @@ steps: - wire-install environment: CGO_ENABLED: "1" - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-backend - commands: - yarn run prettier:check @@ -3831,19 +3825,19 @@ steps: - yarn-install environment: TEST_MAX_WORKERS: 50% - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-frontend - commands: - go test -short -covermode=atomic -timeout=30m ./pkg/... depends_on: - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-backend - commands: - go test -run Integration -covermode=atomic -timeout=30m ./pkg/... depends_on: - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-backend-integration - commands: - yarn run ci:test-frontend @@ -3851,7 +3845,7 @@ steps: - yarn-install environment: TEST_MAX_WORKERS: 50% - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-frontend trigger: ref: @@ -3894,7 +3888,7 @@ services: steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -3909,13 +3903,13 @@ steps: in output.' - CODEGEN_VERIFY=1 make gen-cue depends_on: [] - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - make gen-go depends_on: - verify-gen-cue - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - apt-get update @@ -3931,7 +3925,7 @@ steps: GRAFANA_TEST_DB: postgres PGPASSWORD: grafanatest POSTGRES_HOST: postgres - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: postgres-integration-tests - commands: - apt-get update @@ -3947,7 +3941,7 @@ steps: environment: GRAFANA_TEST_DB: mysql MYSQL_HOST: mysql - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: mysql-integration-tests trigger: ref: @@ -3982,7 +3976,7 @@ steps: name: identify-runner - commands: - $$ProgressPreference = "SilentlyContinue" - - Invoke-WebRequest https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/windows/grabpl.exe + - Invoke-WebRequest https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/windows/grabpl.exe -OutFile grabpl.exe image: grafana/ci-wix:0.1.1 name: windows-init @@ -4030,7 +4024,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -4045,7 +4039,7 @@ steps: environment: GITHUB_TOKEN: from_secret: github_token - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: clone-enterprise - commands: - mv bin/grabpl /tmp/ @@ -4058,25 +4052,25 @@ steps: depends_on: - clone-enterprise environment: {} - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: init-enterprise - commands: - make gen-go depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - yarn install --immutable depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - commands: - ./bin/grabpl gen-version --build-id ${DRONE_BUILD_NUMBER} depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - '# It is required that code generated from Thema/CUE be committed and in sync @@ -4086,14 +4080,14 @@ steps: - CODEGEN_VERIFY=1 make gen-cue depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - ./bin/grabpl build-backend --jobs 8 --edition enterprise --build-id ${DRONE_BUILD_NUMBER} depends_on: - gen-version - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-backend - commands: - ./bin/grabpl build-frontend --jobs 8 --edition enterprise --build-id ${DRONE_BUILD_NUMBER} @@ -4102,7 +4096,7 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend - commands: - ./bin/grabpl build-frontend-packages --jobs 8 --edition enterprise --build-id @@ -4112,7 +4106,7 @@ steps: - yarn-install environment: NODE_OPTIONS: --max_old_space_size=8192 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-frontend-packages - commands: - ./bin/grabpl build-plugins --jobs 8 --edition enterprise @@ -4122,7 +4116,7 @@ steps: environment: GRAFANA_API_KEY: from_secret: grafana_api_key - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-plugins - commands: - ./bin/grabpl build-backend --jobs 8 --edition enterprise2 --build-id ${DRONE_BUILD_NUMBER} @@ -4130,7 +4124,7 @@ steps: depends_on: - gen-version - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-backend-enterprise2 - commands: - ./bin/grabpl package --jobs 8 --edition enterprise --build-id ${DRONE_BUILD_NUMBER} @@ -4150,14 +4144,14 @@ steps: from_secret: gpg_pub_key GRAFANA_API_KEY: from_secret: grafana_api_key - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: package - commands: - ls dist/*.tar.gz* - cp dist/*.tar.gz* packaging/docker/ depends_on: - package - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: copy-packages-for-docker - commands: - ./bin/grabpl build-docker --edition enterprise --shouldSave @@ -4195,7 +4189,7 @@ steps: ARCH: linux-amd64 PORT: 3001 RUNDIR: scripts/grafana-server/tmp-grafana-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: grafana-server - commands: - apt-get install -y netcat @@ -4273,7 +4267,7 @@ steps: - build-frontend-packages environment: NODE_OPTIONS: --max_old_space_size=4096 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: build-storybook - commands: - ./bin/grabpl upload-cdn --edition enterprise @@ -4284,7 +4278,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: upload-cdn-assets when: repo: @@ -4298,7 +4292,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: upload-packages when: repo: @@ -4321,7 +4315,7 @@ steps: from_secret: gpg_pub_key GRAFANA_API_KEY: from_secret: grafana_api_key - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: package-enterprise2 - commands: - ./bin/grabpl upload-cdn --edition enterprise2 @@ -4332,7 +4326,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: upload-cdn-assets-enterprise2 - commands: - ./bin/grabpl upload-packages --edition enterprise2 @@ -4343,7 +4337,7 @@ steps: from_secret: gcp_key PRERELEASE_BUCKET: from_secret: prerelease_bucket - image: grafana/grafana-ci-deploy:1.3.1 + image: grafana/grafana-ci-deploy:1.3.3 name: upload-packages-enterprise2 trigger: ref: @@ -4376,7 +4370,7 @@ services: [] steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -4391,7 +4385,7 @@ steps: environment: GITHUB_TOKEN: from_secret: github_token - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: clone-enterprise - commands: - mv bin/grabpl /tmp/ @@ -4404,25 +4398,25 @@ steps: depends_on: - clone-enterprise environment: {} - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: init-enterprise - commands: - make gen-go depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - yarn install --immutable depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: yarn-install - commands: - ./bin/grabpl gen-version --build-id ${DRONE_BUILD_NUMBER} depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: gen-version - commands: - '# It is required that code generated from Thema/CUE be committed and in sync @@ -4432,7 +4426,7 @@ steps: - CODEGEN_VERIFY=1 make gen-cue depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - |- @@ -4444,7 +4438,7 @@ steps: wan" > words_to_ignore.txt - codespell -I words_to_ignore.txt docs/ - rm words_to_ignore.txt - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: codespell - commands: - make lint-go @@ -4452,7 +4446,7 @@ steps: - wire-install environment: CGO_ENABLED: "1" - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-backend - commands: - yarn run prettier:check @@ -4463,19 +4457,19 @@ steps: - yarn-install environment: TEST_MAX_WORKERS: 50% - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-frontend - commands: - go test -short -covermode=atomic -timeout=30m ./pkg/... depends_on: - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-backend - commands: - go test -run Integration -covermode=atomic -timeout=30m ./pkg/... depends_on: - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-backend-integration - commands: - yarn run ci:test-frontend @@ -4483,7 +4477,7 @@ steps: - yarn-install environment: TEST_MAX_WORKERS: 50% - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-frontend - commands: - make lint-go @@ -4491,13 +4485,13 @@ steps: - wire-install environment: CGO_ENABLED: "1" - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: lint-backend-enterprise2 - commands: - go test -tags=pro -covermode=atomic -timeout=30m ./pkg/... depends_on: - wire-install - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: test-backend-enterprise2 trigger: ref: @@ -4550,7 +4544,7 @@ services: steps: - commands: - mkdir -p bin - - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/grabpl + - curl -fL -o bin/grabpl https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/grabpl - chmod +x bin/grabpl image: byrnedo/alpine-curl:0.1.8 name: grabpl @@ -4565,7 +4559,7 @@ steps: environment: GITHUB_TOKEN: from_secret: github_token - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: clone-enterprise - commands: - mv bin/grabpl /tmp/ @@ -4578,7 +4572,7 @@ steps: depends_on: - clone-enterprise environment: {} - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: init-enterprise - commands: - '# It is required that code generated from Thema/CUE be committed and in sync @@ -4588,13 +4582,13 @@ steps: - CODEGEN_VERIFY=1 make gen-cue depends_on: - init-enterprise - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: verify-gen-cue - commands: - make gen-go depends_on: - verify-gen-cue - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: wire-install - commands: - apt-get update @@ -4610,7 +4604,7 @@ steps: GRAFANA_TEST_DB: postgres PGPASSWORD: grafanatest POSTGRES_HOST: postgres - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: postgres-integration-tests - commands: - apt-get update @@ -4626,7 +4620,7 @@ steps: environment: GRAFANA_TEST_DB: mysql MYSQL_HOST: mysql - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: mysql-integration-tests - commands: - dockerize -wait tcp://redis:6379/0 -timeout 120s @@ -4635,7 +4629,7 @@ steps: - wire-install environment: REDIS_URL: redis://redis:6379/0 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: redis-integration-tests - commands: - dockerize -wait tcp://memcached:11211 -timeout 120s @@ -4644,7 +4638,7 @@ steps: - wire-install environment: MEMCACHED_HOSTS: memcached:11211 - image: grafana/build-container:1.5.7 + image: grafana/build-container:1.5.8 name: memcached-integration-tests trigger: ref: @@ -4683,7 +4677,7 @@ steps: name: identify-runner - commands: - $$ProgressPreference = "SilentlyContinue" - - Invoke-WebRequest https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.52/windows/grabpl.exe + - Invoke-WebRequest https://grafana-downloads.storage.googleapis.com/grafana-build-pipeline/v2.9.54/windows/grabpl.exe -OutFile grabpl.exe - git clone "https://$$env:GITHUB_TOKEN@github.com/grafana/grafana-enterprise.git" - cd grafana-enterprise @@ -4880,6 +4874,6 @@ kind: secret name: gcp_upload_artifacts_key --- kind: signature -hmac: 55383abbbc205824d35aa689a0e00f374e74520d77dc387e354b063e4ade0869 +hmac: fdbc2724cf738ea9a2cd2be46f70d13928c96cc29179a79b7108650af40740ff ... diff --git a/.github/commands.json b/.github/commands.json index 5543c5fb2f3..5357ba7c4f6 100644 --- a/.github/commands.json +++ b/.github/commands.json @@ -138,20 +138,12 @@ "url":"https://github.com/orgs/grafana/projects/112" } }, - { - "type":"label", - "name":"datasource/OpenSearch", - "action":"addToProject", - "addToProject":{ - "url":"https://github.com/orgs/grafana/projects/110" - } - }, { "type":"label", "name":"datasource/Loki", "action":"addToProject", "addToProject":{ - "url":"https://github.com/orgs/grafana/projects/110" + "url":"https://github.com/orgs/grafana/projects/203" } }, { @@ -167,7 +159,7 @@ "name":"datasource/Elasticsearch", "action":"addToProject", "addToProject":{ - "url":"https://github.com/orgs/grafana/projects/110" + "url":"https://github.com/orgs/grafana/projects/203" } }, { diff --git a/CHANGELOG.md b/CHANGELOG.md index 456faeb7272..4e299753e91 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,32 @@ + + +# 9.0.4 (2022-07-20) + +### Features and enhancements + +- **Browse/Search:** Make browser back work properly when visiting Browse or search. [#52271](https://github.com/grafana/grafana/pull/52271), [@torkelo](https://github.com/torkelo) +- **Logs:** Improve getLogRowContext API. [#52130](https://github.com/grafana/grafana/pull/52130), [@gabor](https://github.com/gabor) +- **Loki:** Improve handling of empty responses. [#52397](https://github.com/grafana/grafana/pull/52397), [@gabor](https://github.com/gabor) +- **Plugins:** Always validate root URL if specified in signature manfiest. [#52332](https://github.com/grafana/grafana/pull/52332), [@wbrowne](https://github.com/wbrowne) +- **Preferences:** Get home dashboard from teams. [#52225](https://github.com/grafana/grafana/pull/52225), [@sakjur](https://github.com/sakjur) +- **SQLStore:** Support Upserting multiple rows. [#52228](https://github.com/grafana/grafana/pull/52228), [@joeblubaugh](https://github.com/joeblubaugh) +- **Traces:** Add more template variables in Tempo & Zipkin. [#52306](https://github.com/grafana/grafana/pull/52306), [@joey-grafana](https://github.com/joey-grafana) +- **Traces:** Remove serviceMap feature flag. [#52375](https://github.com/grafana/grafana/pull/52375), [@joey-grafana](https://github.com/joey-grafana) + +### Bug fixes + +- **Access Control:** Fix missing folder permissions. [#52410](https://github.com/grafana/grafana/pull/52410), [@IevaVasiljeva](https://github.com/IevaVasiljeva) +- **Access control:** Fix org user removal for OSS users. [#52473](https://github.com/grafana/grafana/pull/52473), [@IevaVasiljeva](https://github.com/IevaVasiljeva) +- **Alerting:** Fix Slack notification preview. [#50230](https://github.com/grafana/grafana/pull/50230), [@ekrucio](https://github.com/ekrucio) +- **Alerting:** Fix Slack push notifications. [#52391](https://github.com/grafana/grafana/pull/52391), [@grobinson-grafana](https://github.com/grobinson-grafana) +- **Alerting:** Fixes slack push notifications. [#50267](https://github.com/grafana/grafana/pull/50267), [@jgillick](https://github.com/jgillick) +- **Alerting:** Preserve new-lines from custom email templates in rendered email. [#52253](https://github.com/grafana/grafana/pull/52253), [@alexweav](https://github.com/alexweav) +- **Insights:** Fix dashboard and data source insights pages. (Enterprise) +- **Log:** Fix text logging for unsupported types. [#51306](https://github.com/grafana/grafana/pull/51306), [@papagian](https://github.com/papagian) +- **Loki:** Fix `show context` not working in some occasions. [#52458](https://github.com/grafana/grafana/pull/52458), [@svennergr](https://github.com/svennergr) +- **Loki:** Fix incorrect TopK value type in query builder. [#52226](https://github.com/grafana/grafana/pull/52226), [@ivanahuckova](https://github.com/ivanahuckova) + + # 9.0.3 (2022-07-14) diff --git a/Dockerfile b/Dockerfile index 3bee9879f2c..08a7d6f01ad 100644 --- a/Dockerfile +++ b/Dockerfile @@ -20,7 +20,7 @@ COPY emails emails ENV NODE_ENV production RUN yarn build -FROM golang:1.17.11-alpine3.15 as go-builder +FROM golang:1.17.12-alpine3.15 as go-builder RUN apk add --no-cache gcc g++ make diff --git a/Dockerfile.ubuntu b/Dockerfile.ubuntu index fe72f04a8c2..48ef4cc3920 100644 --- a/Dockerfile.ubuntu +++ b/Dockerfile.ubuntu @@ -21,7 +21,7 @@ COPY emails emails ENV NODE_ENV production RUN yarn build -FROM golang:1.17.11 AS go-builder +FROM golang:1.17.12 AS go-builder WORKDIR /src/grafana diff --git a/Makefile b/Makefile index 262dc3e3458..9b6f63cada1 100644 --- a/Makefile +++ b/Makefile @@ -39,8 +39,9 @@ NGALERT_SPEC_TARGET = pkg/services/ngalert/api/tooling/api.json $(NGALERT_SPEC_TARGET): +$(MAKE) -C pkg/services/ngalert/api/tooling api.json -$(MERGED_SPEC_TARGET): $(SPEC_TARGET) $(NGALERT_SPEC_TARGET) ## Merge generated and ngalert API specs - go run pkg/api/docs/merge/merge_specs.go -o=$(MERGED_SPEC_TARGET) $(<) $(NGALERT_SPEC_TARGET) +$(MERGED_SPEC_TARGET): $(SPEC_TARGET) $(NGALERT_SPEC_TARGET) $(SWAGGER) ## Merge generated and ngalert API specs + # known conflicts DsPermissionType, AddApiKeyCommand, Json, Duration (identical models referenced by both specs) + $(SWAGGER) mixin $(SPEC_TARGET) $(NGALERT_SPEC_TARGET) --ignore-conflicts -o $(MERGED_SPEC_TARGET) --swagger-api-spec: $(API_DEFINITION_FILES) $(SWAGGER) ## Generate API Swagger specification SWAGGER_GENERATE_EXTENSION=false $(SWAGGER) generate spec -m -w pkg/server -o public/api-spec.json \ @@ -94,9 +95,30 @@ run-frontend: deps-js ## Fetch js dependencies and watch frontend for rebuild ##@ Testing -test-go: ## Run tests for backend. - @echo "test backend" - $(GO) test -v ./pkg/... +.PHONY: test-go +test-go: test-go-unit test-go-integration + +.PHONY: test-go-unit +test-go-unit: ## Run unit tests for backend with flags. + @echo "test backend unit tests" + $(GO) test -short -covermode=atomic -timeout=30m ./pkg/... + +.PHONY: test-go-integration +test-go-integration: ## Run integration tests for backend with flags. + @echo "test backend integration tests" + $(GO) test -run Integration -covermode=atomic -timeout=30m ./pkg/... + +.PHONY: test-go-integration-postgres +test-go-integration-postgres: devenv-postgres ## Run integration tests for postgres backend with flags. + @echo "test backend integration postgres tests" + $(GO) clean -testcache + $(GO) list './pkg/...' | xargs -I {} sh -c 'GRAFANA_TEST_DB=postgres go test -run Integration -covermode=atomic -timeout=30m {}' + +.PHONY: test-go-integration-mysql +test-go-integration-mysql: devenv-mysql ## Run integration tests for mysql backend with flags. + @echo "test backend integration mysql tests" + $(GO) clean -testcache + $(GO) list './pkg/...' | xargs -I {} sh -c 'GRAFANA_TEST_DB=mysql go test -run Integration -covermode=atomic -timeout=30m {}' test-js: ## Run tests for frontend. @echo "test frontend" @@ -153,6 +175,14 @@ devenv-down: ## Stop optional services. test -f docker-compose.yaml && \ docker-compose down || exit 0; +devenv-postgres: + @cd devenv; \ + sources=postgres_tests + +devenv-mysql: + @cd devenv; \ + sources=mysql_tests + ##@ Helpers # We separate the protobuf generation because most development tasks on diff --git a/conf/defaults.ini b/conf/defaults.ini index 02093ab900c..e06be50e952 100644 --- a/conf/defaults.ini +++ b/conf/defaults.ini @@ -467,6 +467,8 @@ api_url = https://api.github.com/user allowed_domains = team_ids = allowed_organizations = +role_attribute_path = +role_attribute_strict = false #################################### GitLab Auth ######################### [auth.gitlab] @@ -806,6 +808,9 @@ global_session = -1 # global limit of alerts global_alert_rule = -1 +# global limit of files uploaded to the SQL DB +global_file = 1000 + #################################### Unified Alerting #################### [unified_alerting] # Enable the Unified Alerting sub-system and interface. When enabled we'll migrate all of your alert rules and notification channels to the new system. New alert rules will be created and your notification channels will be converted into an Alertmanager configuration. Previous data is preserved to enable backwards compatibility but new data is removed when switching. When this configuration section and flag are not defined, the state is defined at runtime. See the documentation for more details. diff --git a/contribute/style-guides/frontend.md b/contribute/style-guides/frontend.md index 6794894f252..c4691401ad7 100644 --- a/contribute/style-guides/frontend.md +++ b/contribute/style-guides/frontend.md @@ -351,7 +351,7 @@ static defaultProps: Partial = { ... } We recommend using named regular functions when creating a new react functional component. ```typescript -export function Component(props: Props): ReactElement { ... } +export function Component(props: Props) { ... } ``` ## State management diff --git a/docs/sources/administration/service-accounts/_index.md b/docs/sources/administration/service-accounts/_index.md index 1187a4ddeaa..6f2aea2d4b9 100644 --- a/docs/sources/administration/service-accounts/_index.md +++ b/docs/sources/administration/service-accounts/_index.md @@ -16,13 +16,7 @@ weight: 800 # Service accounts -You can use service accounts to run automated or compute workloads. - -{{< section >}} - -## About service accounts - -A service account can be used to run automated workloads in Grafana, like dashboard provisioning, configuration, or report generation. Create service accounts and tokens to authenticate applications like Terraform with the Grafana API. +You can use a service account to run automated workloads in Grafana, such as dashboard provisioning, configuration, or report generation. Create service accounts and tokens to authenticate applications, such as Terraform, with the Grafana API. > **Note:** Service accounts will eventually replace [API keys]({{< relref "../api-keys/" >}}) as the primary way to authenticate applications that interact with Grafana. diff --git a/docs/sources/alerting/contact-points/notifiers/_index.md b/docs/sources/alerting/contact-points/notifiers/_index.md index 164a74e93a3..4f588ad3e71 100644 --- a/docs/sources/alerting/contact-points/notifiers/_index.md +++ b/docs/sources/alerting/contact-points/notifiers/_index.md @@ -18,25 +18,25 @@ weight: 130 The following table lists the notifiers (contact point types) supported by Grafana. -| Name | Type | Grafana Alertmanager | Other Alertmanagers | -| --------------------------------------------- | ------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------- | -| [DingDing](#dingdingdingtalk) | `dingding` | Supported | N/A | -| [Discord](#discord) | `discord` | Supported | N/A | -| [Email](#email) | `email` | Supported | Supported | -| [Google Hangouts Chat](#google-hangouts-chat) | `googlechat` | Supported | N/A | -| [Kafka](#kafka) | `kafka` | Supported | N/A | -| Line | `line` | Supported | N/A | -| Microsoft Teams | `teams` | Supported | N/A | -| [Opsgenie](#opsgenie) | `opsgenie` | Supported | Supported | -| [Pagerduty](#pagerduty) | `pagerduty` | Supported | Supported | -| Prometheus Alertmanager | `prometheus-alertmanager` | Supported | N/A | -| [Pushover](#pushover) | `pushover` | Supported | Supported | -| Sensu | `sensu` | Supported | N/A | -| [Sensu Go](#sensu-go) | `sensugo` | Supported | N/A | -| [Slack](#slack) | `slack` | Supported | Supported | -| Telegram | `telegram` | Supported | N/A | -| Threema | `threema` | Supported | N/A | -| VictorOps | `victorops` | Supported | Supported | -| [Webhook](#webhook) | `webhook` | Supported | Supported ([different format](https://prometheus.io/docs/alerting/latest/configuration/#webhook_config)) | -| [WeCom](#wecom) | `wecom` | Supported | N/A | -| [Zenduty](#zenduty) | `webhook` | Supported | N/A | +| Name | Type | Grafana Alertmanager | Other Alertmanagers | +| ------------------------------------------------ | ------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------- | +| [DingDing](https://www.dingtalk.com/en) | `dingding` | Supported | N/A | +| [Discord](https://discord.com/) | `discord` | Supported | N/A | +| [Email](#email) | `email` | Supported | Supported | +| [Google Hangouts](https://hangouts.google.com/) | `googlechat` | Supported | N/A | +| [Kafka](https://kafka.apache.org/) | `kafka` | Supported | N/A | +| [Line](https://line.me/en/) | `line` | Supported | N/A | +| [Microsoft Teams](https://teams.microsoft.com/) | `teams` | Supported | N/A | +| [Opsgenie](https://atlassian.com/opsgenie/) | `opsgenie` | Supported | Supported | +| [Pagerduty](https://www.pagerduty.com/) | `pagerduty` | Supported | Supported | +| [Prometheus Alertmanager](https://prometheus.io) | `prometheus-alertmanager` | Supported | N/A | +| [Pushover](https://pushover.net/) | `pushover` | Supported | Supported | +| [Sensu](https://sensu.io/) | `sensu` | Supported | N/A | +| [Sensu Go](https://docs.sensu.io/sensu-go/) | `sensugo` | Supported | N/A | +| [Slack](https://slack.com/) | `slack` | Supported | Supported | +| [Telegram](https://telegram.org/) | `telegram` | Supported | N/A | +| [Threema](https://threema.ch/) | `threema` | Supported | N/A | +| [VictorOps](https://help.victorops.com/) | `victorops` | Supported | Supported | +| [Webhook](#webhook) | `webhook` | Supported | Supported ([different format](https://prometheus.io/docs/alerting/latest/configuration/#webhook_config)) | +| [WeCom](#wecom) | `wecom` | Supported | N/A | +| [Zenduty](https://www.zenduty.com/) | `webhook` | Supported | N/A | diff --git a/docs/sources/alerting/migrating-alerts/_index.md b/docs/sources/alerting/migrating-alerts/_index.md index 83b714edd6a..8e7c2ce778c 100644 --- a/docs/sources/alerting/migrating-alerts/_index.md +++ b/docs/sources/alerting/migrating-alerts/_index.md @@ -13,7 +13,7 @@ weight: 101 Grafana Alerting is enabled by default for new installations or existing installations whether or not legacy alerting is configured. -> **Note**: We recommend that Grafana Enterprise customers with more than a dozen Grafana dashboard alert rules do not upgrade and remain on legacy alerting for now by [opting out]({{< relref "opt-out/" >}}). If you do want to upgrade to Grafana Alerting, contact customer support. +> **Note**: When upgrading, your dashboard alerts are migrated to a new format. This migration can be rolled back easily by [opting out]({{< relref "opt-out/" >}}). If you have any questions regarding this migration, please contact us. Existing installations that do not use legacy alerting will have Grafana Alerting enabled by default unless alerting is disabled in the configuration. diff --git a/docs/sources/dashboards/_index.md b/docs/sources/dashboards/_index.md index 7e04cf4a60c..1c4e9d1ef2b 100644 --- a/docs/sources/dashboards/_index.md +++ b/docs/sources/dashboards/_index.md @@ -18,6 +18,7 @@ Before you begin, ensure that you have configured a data source. See also: - [Dashboard folders]({{< relref "dashboard-folders/" >}}) - [Add and organize panels]({{< relref "add-organize-panels/" >}}) - [Manage dashboards]({{< relref "dashboard-manage/" >}}) +- [Public dashboards]({{< relref "dashboard-public/" >}}) - [Annotations]({{< relref "annotations/" >}}) - [Playlist]({{< relref "playlist/" >}}) - [Reporting]({{< relref "reporting/" >}}) diff --git a/docs/sources/dashboards/add-organize-panels.md b/docs/sources/dashboards/add-organize-panels.md index 52854224f1c..b48598903fd 100644 --- a/docs/sources/dashboards/add-organize-panels.md +++ b/docs/sources/dashboards/add-organize-panels.md @@ -35,11 +35,7 @@ This section describes the areas of the Grafana panel editor. - **Transform tab -** Apply data transformations. For more information, refer to [Transform data]({{< relref "../panels/transform-data/" >}}). - **Alert tab -** Write alert rules. For more information, refer to [Overview of Grafana 8 alerting]({{< relref "../alerting/" >}}). -1. Panel display options: The display options section contains tabs where you configure almost every aspect of your data visualization, including: - - - [Apply color to series and fields]({{< relref "../panels/working-with-panels/apply-color-to-series/" >}}) - - [Format a standard field]({{< relref "../panels/working-with-panels/format-standard-fields/" >}}) - - [Add a title and description to a panel]({{< relref "../panels/working-with-panels/add-title-and-description/" >}}) +1. Panel display options: The display options section contains tabs where you configure almost every aspect of your data visualization. > Not all options are available for each visualization. @@ -101,7 +97,7 @@ Dashboards and panels allow you to show your data in visual form. Each panel nee - [Visualization-specific options]({{< relref "../visualizations/" >}}) - [Override field values]({{< relref "../panels/override-field-values/about-field-overrides/" >}}) - [Configure thresholds]({{< relref "../panels/configure-thresholds/" >}}) - - [Apply color to series and fields]({{< relref "../panels/working-with-panels/apply-color-to-series/" >}}) + - [Configure standard options]({{< relref "../panels/configure-standard-options/" >}}) 1. Add a note to describe the visualization (or describe your changes) and then click **Save** in the upper-right corner of the page. diff --git a/docs/sources/dashboards/dashboard-public.md b/docs/sources/dashboards/dashboard-public.md new file mode 100644 index 00000000000..22be16e39e7 --- /dev/null +++ b/docs/sources/dashboards/dashboard-public.md @@ -0,0 +1,55 @@ +--- +aliases: + - /docs/grafana/latest/dashboards/dashboard-manage/ + - /docs/grafana/latest/features/dashboard/dashboards/ +title: Public dashboards +weight: 8 +--- + +## Public dashboards + +> **Note:** This is an opt-in alpha feature. + +> **Caution:** Making your dashboard public could result in a large number of queries to the datasources used by your dashboard. +> This can be mitigated by utilizing the enterprise [caching](https://grafana.com/docs/grafana/latest/enterprise/query-caching/) and/or rate limiting features. + +Public dashboards allow you to share your Grafana dashboard with anyone. This is useful when you want to expose your +dashboard to the world. + +#### Security implications of making your dashboard public + +- Anyone with the URL can access the dashboard. +- Public dashboards are read-only. +- Arbitrary queries **cannot** be run against your datasources through public dashboards. Public dashboards can only execute the + queries stored on the original dashboard. + +#### Enable the feature + +Add the `publicDashboards` feature toggle to your `custom.ini` file. + +> **Note:** For Grafana Cloud, you will need to contact support to have the feature enabled. + +#### Make a dashboard public + +- Click on the sharing icon to the right of the dashboard title. +- Click on the Public Dashboard tab. +- Acknowledge the implications of making the dashboard public by checking all the checkboxes. +- Turn on the Enabled toggle. +- Click `Save Sharing Configuration` to make the dashboard public and make your link live. +- Copy the public dashboard link if you'd like to share it. You can always come back later for it. + +#### Revoke access + +- Click on the sharing icon to the right of the dashboard title. +- Click on the Public Dashboard tab. +- Turn off the Enabled toggle. +- Click `Save Sharing Configuration` to save your changes. +- Anyone with the link will not be able to access the dashboard publicly anymore. + +#### Limitations + +- Panels that use frontend datasources will fail to fetch data. +- Template variables are currently not supported, but are planned to be in the future. +- The time range is permanently set to the default time range on the dashboard. If you update the default time range for a dashboard, it will be reflected in the public dashboard. + +We are excited to share this enhancement with you and we’d love your feedback! Please check out the [Github](https://github.com/grafana/grafana/discussions/49253) discussion and join the conversation. diff --git a/docs/sources/datasources/mssql.md b/docs/sources/datasources/mssql.md index 9a41a65ac80..f6dd2725d8c 100644 --- a/docs/sources/datasources/mssql.md +++ b/docs/sources/datasources/mssql.md @@ -182,7 +182,7 @@ A time series query result is returned in a [wide data frame format]({{< relref > For backward compatibility, there's an exception to the above rule for queries that return three columns including a string column named metric. Instead of transforming the metric column into field labels, it becomes the field name, and then the series name is formatted as the value of the metric column. See the example with the metric column below. -To optionally customize the default series name formatting, refer to [Standard field definitions]({{< relref "../panels/standard-field-definitions/#display-name" >}}). +To optionally customize the default series name formatting, refer to [Standard options definitions]({{< relref "../panels/configure-standard-options/#display-name" >}}). **Example with `metric` column:** @@ -226,7 +226,7 @@ GROUP BY ORDER BY 1 ``` -Given the data frame result in the following example and using the graph panel, you will get two series named _value 10.0.1.1_ and _value 10.0.1.2_. To render the series with a name of _10.0.1.1_ and _10.0.1.2_ , use a [Standard field definition]({{< relref "../panels/standard-field-definitions/#display-name" >}}) display name value of `${__field.labels.hostname}`. +Given the data frame result in the following example and using the graph panel, you will get two series named _value 10.0.1.1_ and _value 10.0.1.2_. To render the series with a name of _10.0.1.1_ and _10.0.1.2_ , use a [Standard options definitions]({{< relref "../panels/configure-standard-options/#display-name" >}}) display name value of `${__field.labels.hostname}`. Data frame result: diff --git a/docs/sources/datasources/mysql.md b/docs/sources/datasources/mysql.md index 41967f9f1d3..d712f8a9ebe 100644 --- a/docs/sources/datasources/mysql.md +++ b/docs/sources/datasources/mysql.md @@ -191,7 +191,7 @@ A time series query result is returned in a [wide data frame format]({{< relref > For backward compatibility, there's an exception to the above rule for queries that return three columns including a string column named metric. Instead of transforming the metric column into field labels, it becomes the field name, and then the series name is formatted as the value of the metric column. See the example with the metric column below. -To optionally customize the default series name formatting, refer to [Standard field definitions]({{< relref "../panels/standard-field-definitions/#display-name" >}}). +To optionally customize the default series name formatting, refer to [Standard options definitions]({{< relref "../panels/configure-standard-options/#display-name" >}}). **Example with `metric` column:** @@ -233,7 +233,7 @@ GROUP BY time, hostname ORDER BY time ``` -Given the data frame result in the following example and using the graph panel, you will get two series named _value 10.0.1.1_ and _value 10.0.1.2_. To render the series with a name of _10.0.1.1_ and _10.0.1.2_ , use a [Standard field definition]({{< relref "../panels/standard-field-definitions/#display-name" >}}) display value of `${__field.labels.hostname}`. +Given the data frame result in the following example and using the graph panel, you will get two series named _value 10.0.1.1_ and _value 10.0.1.2_. To render the series with a name of _10.0.1.1_ and _10.0.1.2_ , use a [[Standard options definitions]({{< relref "../panels/configure-standard-options/#display-name" >}}) display value of `${__field.labels.hostname}`. Data frame result: diff --git a/docs/sources/datasources/postgres.md b/docs/sources/datasources/postgres.md index 1f3a7881bc1..c2d5d3e6349 100644 --- a/docs/sources/datasources/postgres.md +++ b/docs/sources/datasources/postgres.md @@ -196,7 +196,7 @@ A time series query result is returned in a [wide data frame format]({{< relref > For backward compatibility, there's an exception to the above rule for queries that return three columns including a string column named metric. Instead of transforming the metric column into field labels, it becomes the field name, and then the series name is formatted as the value of the metric column. See the example with the metric column below. -To optionally customize the default series name formatting, refer to [Standard field definitions]({{< relref "../panels/standard-field-definitions/#display-name" >}}). +To optionally customize the default series name formatting, refer to [Standard options definitions]({{< relref "../panels/configure-standard-options/#display-name" >}}). **Example with `metric` column:** @@ -238,7 +238,7 @@ GROUP BY time, hostname ORDER BY time ``` -Given the data frame result in the following example and using the graph panel, you will get two series named _value 10.0.1.1_ and _value 10.0.1.2_. To render the series with a name of _10.0.1.1_ and _10.0.1.2_ , use a [Standard field definition]({{< relref "../panels/standard-field-definitions/#display-name" >}}) display value of `${__field.labels.hostname}`. +Given the data frame result in the following example and using the graph panel, you will get two series named _value 10.0.1.1_ and _value 10.0.1.2_. To render the series with a name of _10.0.1.1_ and _10.0.1.2_ , use a [Standard options definitions]({{< relref "../panels/configure-standard-options/#display-name" >}}) display value of `${__field.labels.hostname}`. Data frame result: diff --git a/docs/sources/developers/http_api/access_control.md b/docs/sources/developers/http_api/access_control.md index 6984524a9e4..3910975dd8b 100644 --- a/docs/sources/developers/http_api/access_control.md +++ b/docs/sources/developers/http_api/access_control.md @@ -21,7 +21,7 @@ title: RBAC HTTP API The API can be used to create, update, delete, get, and list roles. -To check which basic or fixed roles have the required permissions, refer to [RBAC role definitions]({{< ref "../../enterprise/access-control/rbac-fixed-basic-role-definitions.md" >}}). +To check which basic or fixed roles have the required permissions, refer to [RBAC role definitions]({{< ref "../../administration/roles-and-permissions/access-control/rbac-fixed-basic-role-definitions.md" >}}). ## Get status @@ -222,7 +222,7 @@ Content-Type: application/json; charset=UTF-8 `POST /api/access-control/roles` -Creates a new custom role and maps given permissions to that role. Note that roles with the same prefix as [Fixed roles]({{< relref "../../enterprise/access-control/about-rbac/#fixed-roles" >}}) can't be created. +Creates a new custom role and maps given permissions to that role. Note that roles with the same prefix as [Fixed roles]({{< relref "../../administration/roles-and-permissions/access-control/#fixed-roles" >}}) can't be created. #### Required permissions @@ -260,24 +260,24 @@ Content-Type: application/json #### JSON body schema -| Field Name | Date Type | Required | Description | -| ----------- | ---------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| uid | string | No | UID of the role. If not present, the UID will be automatically created for you and returned in response. Refer to the [Custom roles]({{< relref "../../enterprise/access-control/about-rbac/#custom-roles" >}}) for more information. | -| global | boolean | No | A flag indicating if the role is global or not. If set to `false`, the default org ID of the authenticated user will be used from the request. | -| version | number | No | Version of the role. If not present, version 0 will be assigned to the role and returned in the response. Refer to the [Custom roles]({{< relref "../../enterprise/access-control/about-rbac/#custom-roles" >}}) for more information. | -| name | string | Yes | Name of the role. Refer to [Custom roles]({{< relref "../../enterprise/access-control/about-rbac/#custom-roles" >}}) for more information. | -| description | string | No | Description of the role. | -| displayName | string | No | Display name of the role, visible in the UI. | -| group | string | No | The group name the role belongs to. | -| hidden | boolean | No | Specify whether the role is hidden or not. If set to `true`, then the role does not show in the role picker. It will not be listed by API endpoints unless explicitly specified. | -| permissions | Permission | No | If not present, the role will be created without any permissions. | +| Field Name | Date Type | Required | Description | +| ----------- | ---------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| uid | string | No | UID of the role. If not present, the UID will be automatically created for you and returned in response. Refer to the [Custom roles]({{< relref "../../administration/roles-and-permissions/access-control/#custom-roles" >}}) for more information. | +| global | boolean | No | A flag indicating if the role is global or not. If set to `false`, the default org ID of the authenticated user will be used from the request. | +| version | number | No | Version of the role. If not present, version 0 will be assigned to the role and returned in the response. Refer to the [Custom roles]({{< relref "../../administration/roles-and-permissions/access-control/#custom-roles" >}}) for more information. | +| name | string | Yes | Name of the role. Refer to [Custom roles]({{< relref "../../administration/roles-and-permissions/access-control/#custom-roles" >}}) for more information. | +| description | string | No | Description of the role. | +| displayName | string | No | Display name of the role, visible in the UI. | +| group | string | No | The group name the role belongs to. | +| hidden | boolean | No | Specify whether the role is hidden or not. If set to `true`, then the role does not show in the role picker. It will not be listed by API endpoints unless explicitly specified. | +| permissions | Permission | No | If not present, the role will be created without any permissions. | **Permission** -| Field Name | Data Type | Required | Description | -| ---------- | --------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| action | string | Yes | Refer to [Custom role actions and scopes]({{< relref "../../enterprise/access-control/custom-role-actions-scopes/" >}}) for full list of available actions. | -| scope | string | No | If not present, no scope will be mapped to the permission. Refer to [[Custom role actions and scopes]({{< relref "../../enterprise/access-control/custom-role-actions-scopes/" >}}) for full list of available scopes. | +| Field Name | Data Type | Required | Description | +| ---------- | --------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| action | string | Yes | Refer to [Custom role actions and scopes]({{< relref "../../administration/roles-and-permissions/access-control/custom-role-actions-scopes/" >}}) for full list of available actions. | +| scope | string | No | If not present, no scope will be mapped to the permission. Refer to [Custom role actions and scopes]({{< relref "../../administration/roles-and-permissions/access-control/custom-role-actions-scopes/" >}}) for full list of available scopes. | #### Example response @@ -375,10 +375,10 @@ Content-Type: application/json **Permission** -| Field Name | Data Type | Required | Description | -| ---------- | --------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| action | string | Yes | Refer to [Custom role actions and scopes]({{< relref "../../enterprise/access-control/custom-role-actions-scopes/" >}}) for full list of available actions. | -| scope | string | No | If not present, no scope will be mapped to the permission. Refer to [Custom role actions and scopes]({{< relref "../../enterprise/access-control/custom-role-actions-scopes/" >}}) for full list of available scopes. | +| Field Name | Data Type | Required | Description | +| ---------- | --------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| action | string | Yes | Refer to [Custom role actions and scopes]({{< relref "../../administration/roles-and-permissions/access-control/custom-role-actions-scopes/" >}}) for full list of available actions. | +| scope | string | No | If not present, no scope will be mapped to the permission. Refer to [Custom role actions and scopes]({{< relref "../../administration/roles-and-permissions/access-control/custom-role-actions-scopes/" >}}) for full list of available scopes. | #### Example response @@ -448,10 +448,10 @@ Accept: application/json #### Query parameters -| Param | Type | Required | Description | -| ------ | ------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| force | boolean | No | When set to `true`, the role will be deleted with all it's assignments. | -| global | boolean | No | A flag indicating if the role is global or not. If set to false, the default org ID of the authenticated user will be used from the request. Refer to the [About RBAC]({{< relref "../../enterprise/access-control/about-rbac/" >}}) for more information. | +| Param | Type | Required | Description | +| ------ | ------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| force | boolean | No | When set to `true`, the role will be deleted with all it's assignments. | +| global | boolean | No | A flag indicating if the role is global or not. If set to false, the default org ID of the authenticated user will be used from the request. Refer to the [About RBAC]({{< relref "../../administration/roles-and-permissions/access-control/" >}}) for more information. | #### Example response diff --git a/docs/sources/developers/http_api/admin.md b/docs/sources/developers/http_api/admin.md index e83c7c941eb..ed91ffe75a1 100644 --- a/docs/sources/developers/http_api/admin.md +++ b/docs/sources/developers/http_api/admin.md @@ -18,7 +18,7 @@ The Admin HTTP API does not currently work with an API Token. API Tokens are cur the permission of server admin, only users can be given that permission. So in order to use these API calls you will have to use Basic Auth and the Grafana user must have the Grafana Admin permission. (The default admin user is called `admin` and has permission to use this API.) -> If you are running Grafana Enterprise, for some endpoints you'll need to have specific permissions. Refer to [Role-based access control permissions]({{< relref "../../enterprise/access-control/custom-role-actions-scopes/" >}}) for more information. +> If you are running Grafana Enterprise, for some endpoints you'll need to have specific permissions. Refer to [Role-based access control permissions]({{< relref "../../administration/roles-and-permissions/access-control/custom-role-actions-scopes/" >}}) for more information. ## Fetch settings @@ -718,11 +718,7 @@ Content-Type: application/json `POST /api/admin/encryption/rotate-data-keys` -Rotates data encryption keys, so all the active keys are disabled -and no longer used for encryption but kept for decryption operations. - -Secrets encrypted with one of the deactivated keys need to be re-encrypted -to actually stop using those keys for both encryption and decryption. +[Rotates]({{< relref "../../setup-grafana/configure-security/configure-database-encryption/#rotate-data-keys" >}}) data encryption keys. **Example Request**: @@ -738,3 +734,66 @@ Content-Type: application/json HTTP/1.1 204 Content-Type: application/json ``` + +## Re-encrypt data encryption keys + +`POST /api/admin/encryption/reencrypt-data-keys` + +[Re-encrypts]({{< relref "../../setup-grafana/configure-security/configure-database-encryption/#re-encrypt-data-keys" >}}) data encryption keys. + +**Example Request**: + +```http +POST /api/admin/encryption/reencrypt-data-keys HTTP/1.1 +Accept: application/json +Content-Type: application/json +``` + +**Example Response**: + +```http +HTTP/1.1 204 +Content-Type: application/json +``` + +## Re-encrypt secrets + +`POST /api/admin/encryption/reencrypt-secrets` + +[Re-encrypts]({{< relref "../../setup-grafana/configure-security/configure-database-encryption/#re-encrypt-secrets" >}}) secrets. + +**Example Request**: + +```http +POST /api/admin/encryption/reencrypt-secrets HTTP/1.1 +Accept: application/json +Content-Type: application/json +``` + +**Example Response**: + +```http +HTTP/1.1 204 +Content-Type: application/json +``` + +## Roll back secrets + +`POST /api/admin/encryption/rollback-secrets` + +[Rolls back]({{< relref "../../setup-grafana/configure-security/configure-database-encryption/#roll-back-secrets" >}}) secrets. + +**Example Request**: + +```http +POST /api/admin/encryption/rollback-secrets HTTP/1.1 +Accept: application/json +Content-Type: application/json +``` + +**Example Response**: + +```http +HTTP/1.1 204 +Content-Type: application/json +``` diff --git a/docs/sources/developers/http_api/serviceaccount.md b/docs/sources/developers/http_api/serviceaccount.md index a2c5d6fbfae..41ad0787b0f 100644 --- a/docs/sources/developers/http_api/serviceaccount.md +++ b/docs/sources/developers/http_api/serviceaccount.md @@ -115,7 +115,7 @@ Requires basic authentication and that the authenticated user is a Grafana Admin **Example Response**: ```http -HTTP/1.1 200 +HTTP/1.1 201 Content-Type: application/json { @@ -140,9 +140,9 @@ Content-Type: application/json See note in the [introduction]({{< ref "#service-account-api" >}}) for an explanation. -| Action | Scope | -| -------------------- | ------------------ | -| serviceaccounts:read | serviceaccounts:\* | +| Action | Scope | +| -------------------- | -------------------- | +| serviceaccounts:read | serviceaccounts:id:1 | **Example Request**: @@ -183,14 +183,14 @@ Content-Type: application/json See note in the [introduction]({{< ref "#service-account-api" >}}) for an explanation. -| Action | Scope | -| --------------------- | ------------------ | -| serviceaccounts:write | serviceaccounts:\* | +| Action | Scope | +| --------------------- | -------------------- | +| serviceaccounts:write | serviceaccounts:id:1 | **Example Request**: ```http -PUT /api/serviceaccounts/2 HTTP/1.1 +PATCH /api/serviceaccounts/2 HTTP/1.1 Accept: application/json Content-Type: application/json Authorization: Basic YWRtaW46YWRtaW4= @@ -235,9 +235,9 @@ Content-Type: application/json See note in the [introduction]({{< ref "#service-account-api" >}}) for an explanation. -| Action | Scope | -| -------------------- | ------------------ | -| serviceaccounts:read | serviceaccounts:\* | +| Action | Scope | +| -------------------- | -------------------- | +| serviceaccounts:read | serviceaccounts:id:1 | **Example Request**: @@ -277,9 +277,9 @@ Content-Type: application/json See note in the [introduction]({{< ref "#service-account-api" >}}) for an explanation. -| Action | Scope | -| --------------------- | ------------------ | -| serviceaccounts:write | serviceaccounts:\* | +| Action | Scope | +| --------------------- | -------------------- | +| serviceaccounts:write | serviceaccounts:id:1 | **Example Request**: @@ -318,9 +318,9 @@ Content-Type: application/json See note in the [introduction]({{< ref "#service-account-api" >}}) for an explanation. -| Action | Scope | -| --------------------- | ------------------ | -| serviceaccounts:write | serviceaccounts:\* | +| Action | Scope | +| --------------------- | -------------------- | +| serviceaccounts:write | serviceaccounts:id:1 | **Example Request**: diff --git a/docs/sources/developers/plugins/plugin.schema.json b/docs/sources/developers/plugins/plugin.schema.json index 41fe4dabaf3..358c159a590 100644 --- a/docs/sources/developers/plugins/plugin.schema.json +++ b/docs/sources/developers/plugins/plugin.schema.json @@ -14,12 +14,12 @@ "id": { "type": "string", "description": "Unique name of the plugin. If the plugin is published on grafana.com, then the plugin id has to follow the naming conventions.", - "pattern": "^[0-9a-z]+\\-([0-9a-z]+\\-)?(app|panel|datasource)$" + "pattern": "^[0-9a-z]+\\-([0-9a-z]+\\-)?(app|panel|datasource|secretsmanager)$" }, "type": { "type": "string", "description": "Plugin type.", - "enum": ["app", "datasource", "panel"] + "enum": ["app", "datasource", "panel", "secretsmanager"] }, "name": { "type": "string", @@ -68,7 +68,7 @@ }, "type": { "type": "string", - "enum": ["dashboard", "page", "panel", "datasource"] + "enum": ["dashboard", "page", "panel", "datasource", "secretsmanager"] }, "name": { "type": "string" @@ -159,11 +159,11 @@ "properties": { "id": { "type": "string", - "pattern": "^[0-9a-z]+\\-([0-9a-z]+\\-)?(app|panel|datasource)$" + "pattern": "^[0-9a-z]+\\-([0-9a-z]+\\-)?(app|panel|datasource|secretsmanager)$" }, "type": { "type": "string", - "enum": ["app", "datasource", "panel"] + "enum": ["app", "datasource", "panel", "secretsmanager"] }, "name": { "type": "string" diff --git a/docs/sources/enterprise/_index.md b/docs/sources/enterprise/_index.md index 46de4238d4b..5663c08a927 100644 --- a/docs/sources/enterprise/_index.md +++ b/docs/sources/enterprise/_index.md @@ -66,6 +66,7 @@ Grafana Enterprise adds the following features: - [Custom branding]({{< relref "../setup-grafana/configure-grafana/configure-custom-branding/" >}}) to customize Grafana from the brand and logo to the footer links. - [Usage insights]({{< relref "usage-insights/" >}}) to understand how your Grafana instance is used. - [Vault integration]({{< relref "../setup-grafana/configure-security/configure-database-encryption/integrate-with-hashicorp-vault/" >}}) to manage your configuration or provisioning secrets with Vault. +- [AWS Secrets Manager integration]({{< relref "../setup-grafana/configure-security/configure-database-encryption/store-secrets-using-aws-secrets-manager-plugin/" >}}) to store datasource secrets in AWS Secrets Manager. - [Auditing]({{< relref "../setup-grafana/configure-security/audit-grafana/" >}}) tracks important changes to your Grafana instance to help you manage and mitigate suspicious activity and meet compliance requirements. - [Request security]({{< relref "../setup-grafana/configure-security/configure-request-security/" >}}) makes it possible to restrict outgoing requests from the Grafana server. - [Settings updates at runtime]({{< relref "settings-updates/" >}}) allows you to update Grafana settings at runtime without requiring a restart. diff --git a/docs/sources/enterprise/query-caching.md b/docs/sources/enterprise/query-caching.md index 6cd0fbeb8db..ae0461edb6d 100644 --- a/docs/sources/enterprise/query-caching.md +++ b/docs/sources/enterprise/query-caching.md @@ -15,7 +15,7 @@ weight: 300 When query caching is enabled, Grafana temporarily stores the results of data source queries. When you or another user submit the exact same query again, the results will come back from the cache instead of from the data source (like Splunk or ServiceNow) itself. -Query caching works for all backend data sources, and queries sent through the data source proxy. You can enable the cache globally and configure the cache duration (also called Time to Live, or TTL). +Query caching works for all backend data sources. You can enable the cache globally and configure the cache duration (also called Time to Live, or TTL). > **Note:** Available in [Grafana Enterprise]({{< relref "../enterprise/" >}}) and [Grafana Cloud Pro and Advanced]({{< ref "/grafana-cloud" >}}). diff --git a/docs/sources/introduction/grafana-enterprise.md b/docs/sources/introduction/grafana-enterprise.md index d5f84945499..9d956e4f90a 100644 --- a/docs/sources/introduction/grafana-enterprise.md +++ b/docs/sources/introduction/grafana-enterprise.md @@ -57,6 +57,7 @@ Grafana Enterprise adds the following features: - [Custom branding]({{< relref "../setup-grafana/configure-grafana/configure-custom-branding/" >}}) to customize Grafana from the brand and logo to the footer links. - [Usage insights]({{< relref "../enterprise/usage-insights/" >}}) to understand how your Grafana instance is used. - [Vault integration]({{< relref "../setup-grafana/configure-security/configure-database-encryption/encrypt-secrets-using-hashicorp-key-vault/" >}}) to manage your configuration or provisioning secrets with Vault. +- [AWS Secrets Manager integration]({{< relref "../setup-grafana/configure-security/configure-database-encryption/store-secrets-using-aws-secrets-manager-plugin/" >}}) to store datasource secrets in AWS Secrets Manager. - [Auditing]({{< relref "../setup-grafana/configure-security/audit-grafana/" >}}) tracks important changes to your Grafana instance to help you manage and mitigate suspicious activity and meet compliance requirements. - [Request security]({{< relref "../setup-grafana/configure-security/configure-request-security/" >}}) makes it possible to restrict outgoing requests from the Grafana server. - [Settings updates at runtime]({{< relref "../enterprise/settings-updates.md" >}}) allows you to update Grafana settings at runtime without requiring a restart. diff --git a/docs/sources/panels/standard-field-definitions.md b/docs/sources/panels/configure-standard-options/index.md similarity index 53% rename from docs/sources/panels/standard-field-definitions.md rename to docs/sources/panels/configure-standard-options/index.md index 3128a6edfe8..e523a28e6fb 100644 --- a/docs/sources/panels/standard-field-definitions.md +++ b/docs/sources/panels/configure-standard-options/index.md @@ -1,15 +1,39 @@ --- aliases: + - /docs/grafana/latest/panels/working-with-panels/format-standard-fields/ - /docs/grafana/latest/panels/reference-standard-field-definitions/ - /docs/grafana/latest/panels/standard-field-definitions/ - - /docs/sources/panels/reference-standard-field-definitions/ -title: Standard field definitions -weight: 1200 +title: Configure standard options +menuTitle: Configure standard options +weight: 40 +keywords: + - xxx + - xxx --- -# Reference: Standard field definitions +# Configure standard options -This section explains all available standard options. They are listed in alphabetical order. +The data model used in Grafana, namely the [data frame]({{< relref "../../developers/plugins/data-frames/" >}}), is a columnar-oriented table structure that unifies both time series and table query results. Each column within this structure is called a _field_. A field can represent a single time series or table column. + +Field options allow you to change how the data is displayed in your visualizations. Options and overrides that you apply do not change the data, they change how Grafana displays the data. When you change an option, it is applied to all fields, meaning all series or columns. For example, if you change the unit to percentage, then all fields with numeric values are displayed in percentages. + +For a complete list of field formatting options, refer to [Standard options definitions]({{< relref "#standard-options-definitions" >}}). + +> You can apply standard options to most built-in Grafana panels. Some older panels and community panels that have not updated to the new panel and data model will be missing either all or some of these field options. + +1. Open a dashboard, click the panel title, and click **Edit**. + +1. In the panel display options pane, locate the **Standard options** section. + +1. Select the standard options you want to apply. + + For more information about standard options, refer to [Standard options definitions]({{< relref "#standard-options-definitions" >}}). + +1. To preview your change, click outside of the field option box you are editing or press **Enter**. + +## Standard options definitions + +This section explains all available standard options. You can apply standard options to most built-in Grafana panels. Some older panels and community panels that have not updated to the new panel and data model will be missing either all or some of these field options. @@ -17,53 +41,11 @@ Most field options will not affect the visualization until you click outside of > **Note:** We are constantly working to add and expand options for all visualization, so all options might not be available for all visualizations. -## Decimals - -Number of decimals to render value with. Leave empty for Grafana to use the number of decimals provided by the data source. - -To change this setting, type a number in the field and then click outside the field or press Enter. - -## Data links - -Lets you control the URL to which a value or visualization link. - -For more information and instructions, refer to [Data links]({{< relref "./configure-data-links/#data-links" >}}). - -## Display name - -Lets you set the display title of all fields. You can use [variables]({{< relref "../variables/" >}}) in the field title. - -When multiple stats, fields, or series are shown, this field controls the title in each stat. You can use expressions like `${__field.name}` to use only the series name or the field name in title. - -Given a field with a name of Temp, and labels of {"Loc"="PBI", "Sensor"="3"} - -| Expression syntax | Example | Renders to | Explanation | -| ---------------------------- | ----------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `${__field.displayName}` | Same as syntax | `Temp {Loc="PBI", Sensor="3"}` | Displays the field name, and labels in `{}` if they are present. If there is only one label key in the response, then for the label portion, Grafana displays the value of the label without the enclosing braces. | -| `${__field.name}` | Same as syntax | `Temp` | Displays the name of the field (without labels). | -| `${__field.labels}` | Same as syntax | `Loc="PBI", Sensor="3"` | Displays the labels without the name. | -| `${__field.labels.X}` | `${__field.labels.Loc}` | `PBI` | Displays the value of the specified label key. | -| `${__field.labels.__values}` | Same as Syntax | `PBI, 3` | Displays the values of the labels separated by a comma (without label keys). | - -If the value is an empty string after rendering the expression for a particular field, then the default display method is used. - -## Max - -Lets you set the maximum value used in percentage threshold calculations. Leave blank for auto calculation based on all series and fields - -## Min - -Lets you set the minimum value used in percentage threshold calculations. Leave blank for auto calculation based on all series and fields - -## No value - -Enter what Grafana should display if the field value is empty or null. The default value is a hyphen (-). - -## Unit +### Unit Lets you choose what unit a field should use. Click in the **Unit** field, then drill down until you find the unit you want. The unit you select is applied to all fields except time. -### Custom units +#### Custom units You can use the unit dropdown to also specify custom units, custom prefix or suffix and date time formats. @@ -81,6 +63,67 @@ You can also paste a native emoji in the unit picker and pick it as a custom uni {{< figure src="/static/img/docs/v66/custom_unit_burger2.png" max-width="600px" caption="Custom unit emoji" >}} -### String units +#### String units Grafana can sometime be too aggressive in parsing strings and displaying them as numbers. To make Grafana show the original string create a field override and add a unit property with the `string` unit. + +### Min + +Lets you set the minimum value used in percentage threshold calculations. Leave blank for auto calculation based on all series and fields. + +### Max + +Lets you set the maximum value used in percentage threshold calculations. Leave blank for auto calculation based on all series and fields. + +### Decimals + +Number of decimals to render value with. Leave empty for Grafana to use the number of decimals provided by the data source. + +To change this setting, type a number in the field and then click outside the field or press Enter. + +### Display name + +Lets you set the display title of all fields. You can use [variables]({{< relref "../../variables/" >}}) in the field title. + +When multiple stats, fields, or series are shown, this field controls the title in each stat. You can use expressions like `${__field.name}` to use only the series name or the field name in title. + +Given a field with a name of Temp, and labels of {"Loc"="PBI", "Sensor"="3"} + +| Expression syntax | Example | Renders to | Explanation | +| ---------------------------- | ----------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `${__field.displayName}` | Same as syntax | `Temp {Loc="PBI", Sensor="3"}` | Displays the field name, and labels in `{}` if they are present. If there is only one label key in the response, then for the label portion, Grafana displays the value of the label without the enclosing braces. | +| `${__field.name}` | Same as syntax | `Temp` | Displays the name of the field (without labels). | +| `${__field.labels}` | Same as syntax | `Loc="PBI", Sensor="3"` | Displays the labels without the name. | +| `${__field.labels.X}` | `${__field.labels.Loc}` | `PBI` | Displays the value of the specified label key. | +| `${__field.labels.__values}` | Same as Syntax | `PBI, 3` | Displays the values of the labels separated by a comma (without label keys). | + +If the value is an empty string after rendering the expression for a particular field, then the default display method is used. + +### Color scheme + +The color options and their effect on the visualization depends on the visualization you are working with. Some visualizations have different color options. + +You can specify a single color, or select a continuous (gradient) color schemes, based on a value. +Continuous color interpolates a color using the percentage of a value relative to min and max. + +Select one of the following palettes: + +
+ +| Color mode | Description | +| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **Single color** | Specify a single color, useful in an override rule | +| **From thresholds** | Informs Grafana to take the color from the matching threshold | +| **Classic palette** | Grafana will assign color by looking up a color in a palette by series index. Useful for Graphs and pie charts and other categorical data visualizations | +| **Green-Yellow-Red (by value)** | Continuous color scheme | +| **Blue-Yellow-Red (by value)** | Continuous color scheme | +| **Blues (by value)** | Continuous color scheme (panel background to blue) | +| **Reds (by value)** | Continuous color scheme (panel background color to blue) | +| **Greens (by value)** | Continuous color scheme (panel background color to blue) | +| **Purple (by value)** | Continuous color scheme (panel background color to blue) | + +{{< figure src="/static/img/docs/v73/color_scheme_dropdown.png" max-width="350px" caption="Color scheme" >}} + +### No value + +Enter what Grafana should display if the field value is empty or null. The default value is a hyphen (-). diff --git a/docs/sources/panels/working-with-panels/apply-color-to-series.md b/docs/sources/panels/working-with-panels/apply-color-to-series.md deleted file mode 100644 index 26e30345905..00000000000 --- a/docs/sources/panels/working-with-panels/apply-color-to-series.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -aliases: - - /docs/grafana/latest/panels/working-with-panels/apply-color-to-series/ - - /docs/sources/panels/working-with-panels/apply-color-to-series/ -title: Apply color to series and fields -weight: 50 ---- - -# Apply color to series and fields - -In addition to specifying color based on thresholds, you can configure the color of series and field data. The color options and their effect on the visualization depends on the visualization you are working with. Some visualizations have different color options. - -You can specify a single color, or select a continuous (gradient) color schemes, based on a value. -Continuous color interpolates a color using the percentage of a value relative to min and max. - -1. In panel display options, scroll to the **Standard options** or **override** section. - -1. Click the **Standard options Color scheme** drop-down, and select one of the following palettes: - -
- -| Color mode | Description | -| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | -| **Single color** | Specify a single color, useful in an override rule | -| **From thresholds** | Informs Grafana to take the color from the matching threshold | -| **Classic palette** | Grafana will assign color by looking up a color in a palette by series index. Useful for Graphs and pie charts and other categorical data visualizations | -| **Green-Yellow-Red (by value)** | Continuous color scheme | -| **Blue-Yellow-Red (by value)** | Continuous color scheme | -| **Blues (by value)** | Continuous color scheme (panel background to blue) | -| **Reds (by value)** | Continuous color scheme (panel background color to blue) | -| **Greens (by value)** | Continuous color scheme (panel background color to blue) | -| **Purple (by value)** | Continuous color scheme (panel background color to blue) | . | - -{{< figure src="/static/img/docs/v73/color_scheme_dropdown.png" max-width="350px" caption="Color scheme" class="pull-right" >}} diff --git a/docs/sources/panels/working-with-panels/format-standard-fields.md b/docs/sources/panels/working-with-panels/format-standard-fields.md deleted file mode 100644 index ee0404ac817..00000000000 --- a/docs/sources/panels/working-with-panels/format-standard-fields.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: - - /docs/grafana/latest/panels/working-with-panels/format-standard-fields/ - - /docs/sources/panels/working-with-panels/format-standard-fields/ -title: Format a standard field -weight: 40 ---- - -# Format a standard field - -The data model used in Grafana, namely the [data frame]({{< relref "../../developers/plugins/data-frames/" >}}), is a columnar-oriented table structure that unifies both time series and table query results. Each column within this structure is called a _field_. A field can represent a single time series or table column. - -Field options allow you to change how the data is displayed in your visualizations. Options and overrides that you apply do not change the data, they change how Grafana displays the data. When you change an option, it is applied to all fields, meaning all series or columns. For example, if you change the unit to percentage, then all fields with numeric values are displayed in percentages. - -For a complete list of field formatting options, refer to [Standard field definitions]({{< relref "../standard-field-definitions/" >}}). - -> You can apply standard options to most built-in Grafana panels. Some older panels and community panels that have not updated to the new panel and data model will be missing either all or some of these field options. - -1. Open a dashboard, click the panel title, and click **Edit**. - -1. In the panel display options pane, locate the **Standard options** section. - -1. Select the standard options you want to apply. - - For more information about standard options, refer to [Standard field definitions]({{< relref "../standard-field-definitions/" >}}). - -1. To preview your change, click outside of the field option box you are editing or press **Enter**. diff --git a/docs/sources/release-notes/_index.md b/docs/sources/release-notes/_index.md index 07acfe2ae68..0d860f6698c 100644 --- a/docs/sources/release-notes/_index.md +++ b/docs/sources/release-notes/_index.md @@ -10,6 +10,7 @@ weight: 10000 Here you can find detailed release notes that list everything that is included in every release as well as notices about deprecations, breaking changes as well as changes that relate to plugin development. +- [Release notes for 9.0.4]({{< relref "release-notes-9-0-4" >}}) - [Release notes for 9.0.3]({{< relref "release-notes-9-0-3" >}}) - [Release notes for 9.0.2]({{< relref "release-notes-9-0-2" >}}) - [Release notes for 9.0.1]({{< relref "release-notes-9-0-1" >}}) diff --git a/docs/sources/release-notes/release-notes-9-0-4.md b/docs/sources/release-notes/release-notes-9-0-4.md new file mode 100644 index 00000000000..46e1d4aa4a9 --- /dev/null +++ b/docs/sources/release-notes/release-notes-9-0-4.md @@ -0,0 +1,32 @@ ++++ +title = "Release notes for Grafana 9.0.4" +hide_menu = true ++++ + + + +# Release notes for Grafana 9.0.4 + +### Features and enhancements + +- **Browse/Search:** Make browser back work properly when visiting Browse or search. [#52271](https://github.com/grafana/grafana/pull/52271), [@torkelo](https://github.com/torkelo) +- **Logs:** Improve getLogRowContext API. [#52130](https://github.com/grafana/grafana/pull/52130), [@gabor](https://github.com/gabor) +- **Loki:** Improve handling of empty responses. [#52397](https://github.com/grafana/grafana/pull/52397), [@gabor](https://github.com/gabor) +- **Plugins:** Always validate root URL if specified in signature manfiest. [#52332](https://github.com/grafana/grafana/pull/52332), [@wbrowne](https://github.com/wbrowne) +- **Preferences:** Get home dashboard from teams. [#52225](https://github.com/grafana/grafana/pull/52225), [@sakjur](https://github.com/sakjur) +- **SQLStore:** Support Upserting multiple rows. [#52228](https://github.com/grafana/grafana/pull/52228), [@joeblubaugh](https://github.com/joeblubaugh) +- **Traces:** Add more template variables in Tempo & Zipkin. [#52306](https://github.com/grafana/grafana/pull/52306), [@joey-grafana](https://github.com/joey-grafana) +- **Traces:** Remove serviceMap feature flag. [#52375](https://github.com/grafana/grafana/pull/52375), [@joey-grafana](https://github.com/joey-grafana) + +### Bug fixes + +- **Access Control:** Fix missing folder permissions. [#52410](https://github.com/grafana/grafana/pull/52410), [@IevaVasiljeva](https://github.com/IevaVasiljeva) +- **Access control:** Fix org user removal for OSS users. [#52473](https://github.com/grafana/grafana/pull/52473), [@IevaVasiljeva](https://github.com/IevaVasiljeva) +- **Alerting:** Fix Slack notification preview. [#50230](https://github.com/grafana/grafana/pull/50230), [@ekrucio](https://github.com/ekrucio) +- **Alerting:** Fix Slack push notifications. [#52391](https://github.com/grafana/grafana/pull/52391), [@grobinson-grafana](https://github.com/grobinson-grafana) +- **Alerting:** Fixes slack push notifications. [#50267](https://github.com/grafana/grafana/pull/50267), [@jgillick](https://github.com/jgillick) +- **Alerting:** Preserve new-lines from custom email templates in rendered email. [#52253](https://github.com/grafana/grafana/pull/52253), [@alexweav](https://github.com/alexweav) +- **Insights:** Fix dashboard and data source insights pages. (Enterprise) +- **Log:** Fix text logging for unsupported types. [#51306](https://github.com/grafana/grafana/pull/51306), [@papagian](https://github.com/papagian) +- **Loki:** Fix `show context` not working in some occasions. [#52458](https://github.com/grafana/grafana/pull/52458), [@svennergr](https://github.com/svennergr) +- **Loki:** Fix incorrect TopK value type in query builder. [#52226](https://github.com/grafana/grafana/pull/52226), [@ivanahuckova](https://github.com/ivanahuckova) diff --git a/docs/sources/setup-grafana/configure-security/configure-authentication/github.md b/docs/sources/setup-grafana/configure-security/configure-authentication/github.md index 889768001f9..557ef871282 100644 --- a/docs/sources/setup-grafana/configure-security/configure-authentication/github.md +++ b/docs/sources/setup-grafana/configure-security/configure-authentication/github.md @@ -101,6 +101,35 @@ allow_sign_up = true allowed_organizations = github google ``` +### Map roles + +You can use GitHub OAuth to map roles. During mapping, Grafana checks for the presence of a role using the [JMESPath](http://jmespath.org/examples.html) specified via the `role_attribute_path` configuration option. + +For the path lookup, Grafana uses JSON obtained from querying GitHub's API [`/api/user`](https://docs.github.com/en/rest/users/users#get-the-authenticated-user=) endpoint and a `groups` key containing all of the user's teams (retrieved from `/api/user/teams`). + +The result of evaluating the `role_attribute_path` JMESPath expression must be a valid Grafana role, for example, `Viewer`, `Editor` or `Admin`. For more information about roles and permissions in Grafana, refer to [Roles and permissions]({{< relref "../../../administration/roles-and-permissions/" >}}). + +An example Query could look like the following: + +```bash +role_attribute_path = [login==octocat] && 'Admin' || 'Viewer' +``` + +This allows the user with login "octocat" to be mapped to the `Admin` role, +but all other users to be mapped to the `Viewer` role. + +#### Map roles using teams + +Teams can also be used to map roles. For instance, +if you have a team called 'example-group' you can use the following snippet to +ensure those members inherit the role 'Editor'. + +```bash +role_attribute_path = contains(groups[*], '@github/example-group') && 'Editor' || 'Viewer' +``` + +Note: If a match is found in other fields, teams will be ignored. + ### Team Sync (Enterprise only) > Only available in Grafana Enterprise v6.3+ diff --git a/docs/sources/setup-grafana/configure-security/configure-authentication/gitlab.md b/docs/sources/setup-grafana/configure-security/configure-authentication/gitlab.md index 7a37e83e12e..0638161f0e0 100644 --- a/docs/sources/setup-grafana/configure-security/configure-authentication/gitlab.md +++ b/docs/sources/setup-grafana/configure-security/configure-authentication/gitlab.md @@ -122,7 +122,7 @@ role_attribute_path = is_admin && 'Admin' || 'Viewer' You can use GitLab OAuth to map roles. During mapping, Grafana checks for the presence of a role using the [JMESPath](http://jmespath.org/examples.html) specified via the `role_attribute_path` configuration option. -For the path lookup, Grafana uses JSON obtained from querying GitLab's API [`/api/v4/user`](https://docs.gitlab.com/ee/api/users.html#list-current-user-for-normal-users) endpoint. The result of evaluating the `role_attribute_path` JMESPath expression must be a valid Grafana role, for example, `Viewer`, `Editor` or `Admin`. For more information about roles and permissions in Grafana, refer to [Roles and permissions]({{< relref "../../../administration/roles-and-permissions/" >}}). +For the path lookup, Grafana uses JSON obtained from querying GitLab's API [`/api/v4/user`](https://docs.gitlab.com/ee/api/users.html#list-current-user-for-normal-users) endpoint and a `groups` key containing all of the user's teams. The result of evaluating the `role_attribute_path` JMESPath expression must be a valid Grafana role, for example, `Viewer`, `Editor` or `Admin`. For more information about roles and permissions in Grafana, refer to [Roles and permissions]({{< relref "../../../administration/roles-and-permissions/" >}}). An example Query could look like the following: @@ -132,6 +132,19 @@ role_attribute_path = is_admin && 'Admin' || 'Viewer' This allows every GitLab Admin to be an Admin in Grafana. +#### Map roles using groups + +Groups can also be used to map roles. Group name (lowercased and unique) is used instead of display name for identifying groups + +For instance, if you have a group with display name 'Example-Group' you can use the following snippet to +ensure those members inherit the role 'Editor'. + +```bash +role_attribute_path = contains(groups[*], 'example-group') && 'Editor' || 'Viewer' +``` + +Note: If a match is found in other fields, groups will be ignored. + ### Team Sync (Enterprise only) > Only available in Grafana Enterprise v6.4+ diff --git a/docs/sources/setup-grafana/configure-security/configure-database-encryption/_index.md b/docs/sources/setup-grafana/configure-security/configure-database-encryption/_index.md index 21251774e37..48864deb65f 100644 --- a/docs/sources/setup-grafana/configure-security/configure-database-encryption/_index.md +++ b/docs/sources/setup-grafana/configure-security/configure-database-encryption/_index.md @@ -18,7 +18,7 @@ Grafana encrypts these secrets before they are written to the database, by using Since Grafana v9.0, it uses [envelope encryption](#envelope-encryption) by default, which adds a layer of indirection to the encryption process that represents an [**implicit breaking change**](#implicit-breaking-change) for older versions of Grafana. -For further details about how to operate a Grafana instance with envelope encryption, see the [Operational work]({{< relref "/#operational-work" >}}) section below. +For further details about how to operate a Grafana instance with envelope encryption, see the [Operational work](#operational-work) section below. > **Note:** In Grafana Enterprise, you can also choose to [encrypt secrets in AES-GCM mode]({{< relref "#changing-your-encryption-mode-to-aes-gcm" >}}) instead of AES-CFB. @@ -31,7 +31,7 @@ Instead of encrypting all secrets with a single key, Grafana uses a set of keys encrypt them. These data encryption keys are themselves encrypted with a single key encryption key (KEK), configured through the `secret_key` attribute in your [Grafana configuration]({{< relref "../../configure-grafana/#secret_key" >}}) or with a -[KMS integration](#kms-integration). +[KMS integration](#encrypting-your-database-with-a-key-from-a-key-management-system-kms). ## Implicit breaking change @@ -67,7 +67,8 @@ Secrets re-encryption can be performed when a Grafana administrator wants to eit - Re-encrypt secrets after a [data keys rotation](#rotate-data-keys). > **Note:** This operation is available through Grafana CLI by running `grafana-cli admin secrets-migration re-encrypt` -> command. It's safe to run more than once. Recommended to run under maintenance mode. +> command and through Grafana [Admin API]({{< relref "../../../developers/http_api/admin/#re-encrypt-secrets" >}}). +> It's safe to run more than once. Recommended to run under maintenance mode. ## Roll back secrets @@ -75,16 +76,18 @@ Used to roll back secrets encrypted with envelope encryption to legacy encryptio a Grafana version earlier than Grafana v9.0 after an unsuccessful upgrade. > **Note:** This operation is available through Grafana CLI by running `grafana-cli admin secrets-migration rollback` -> command. It's safe to run more than once. Recommended to run under maintenance mode. +> command and through Grafana [Admin API]({{< relref "../../../developers/http_api/admin/#roll-back-secrets" >}}). +> It's safe to run more than once. Recommended to run under maintenance mode. ## Re-encrypt data keys Used to re-encrypt data keys encrypted with a specific key encryption key (KEK). It can be used to either re-encrypt -existing data keys with a new key encryption key version (see [KMS integration](#kms-integration) rotation) or to +existing data keys with a new key encryption key version (see [KMS integration](#encrypting-your-database-with-a-key-from-a-key-management-system-kms) rotation) or to re-encrypt them with a completely different key encryption key. > **Note:** This operation is available through Grafana CLI by running `grafana-cli admin secrets-migration re-encrypt-data-keys` -> command. It's safe to run more than once. Recommended to run under maintenance mode. +> command and through Grafana [Admin API]({{< relref "../../../developers/http_api/admin/#re-encrypt-data-encryption-keys" >}}). +> It's safe to run more than once. Recommended to run under maintenance mode. ## Rotate data keys diff --git a/docs/sources/setup-grafana/configure-security/configure-database-encryption/store-secrets-using-aws-secrets-manager-plugin.md b/docs/sources/setup-grafana/configure-security/configure-database-encryption/store-secrets-using-aws-secrets-manager-plugin.md new file mode 100644 index 00000000000..ec2008d8f71 --- /dev/null +++ b/docs/sources/setup-grafana/configure-security/configure-database-encryption/store-secrets-using-aws-secrets-manager-plugin.md @@ -0,0 +1,123 @@ +--- +aliases: + - /docs/grafana/latest/setup-grafana/configure-security/configure-database-encryption/store-secrets-using-aws-secrets=manager-plugin/ +description: 'Learn how to use AWS Secrets Manager plugin to store Grafana secrets.' +keywords: + - grafana + - secrets + - secretsmanager + - aws + - backend +title: Store secrets using AWS Secrets Manager plugin +menuTitle: Store Secrets in AWS Secrets Manager +weight: 2000 +--- + +# Store secrets using AWS Secrets Manager plugin + +By default, Grafana stores all encrypted secrets in its own SQL database. To store secrets in [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/), use the AWS Secrets Manager plugin. This is limited to datasource secrets as of Grafana version 9.1, but future versions will include all secrets, such as user credentials. + +You can configure options in the plugin to determine secret storage behavior in AWS Secrets Manager, and also migrate secrets from existing Grafana instances to AWS Secrets Manager. We also provide backward compatibility so that the plugin can be safely uninstalled, with some [limitations](#limitations). + +> **Note:** Available only in [Grafana Enterprise]({{< relref "../../../enterprise/" >}}). + +## Install the plugin + +You can install the plugin using [Grafana CLI]({{< relref "../../../cli/" >}}): + +```sh +grafana-cli plugins install grafana-aws-secretsmanager +``` + +After you install the plugin, you must enable it. + +1. Open the Grafana **custom.ini** file. +1. Locate or create the `[secrets]` section. +1. Set the key `use_plugin` to `true`. +1. Save your changes and restart the Grafana server. + +``` +[secrets] +use_plugin = true +``` + +If you have enabled the plugin correctly, you will see the plugin listed in the [plugin catalog]({{< relref "../../../administration/plugin-management/#plugin-catalog" >}}) with the badges `Installed` and `Signed`. + +## Authenticate with AWS + +By default, the plugin attempts to authenticate with AWS and select a region using parameters read from the runtime environment. For more details, see the [AWS CLI](https://aws.amazon.com/cli/) setup documentation. + +Alternatively, you can configure authentication and region selection explicitly through Grafana's configuration. For a full list of available options, see [Configure the plugin](#configure-the-plugin). For more information on configuring Grafana, see [Configure Grafana]({{< relref "../../configure-grafana/" >}}). + +## Configure the plugin + +1. Open the **custom.ini** file. +1. Create a configuration section file called `[plugin.grafana-aws-secretsmanager]`. +1. Place the following optional configuration settings in the new section. + +| Setting | Description | Example | Default | +| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | ------------------------------- | +| `aws_access_key_id` | IAM user’s Access Key ID | AKIAIOSFODNN7EXAMPLE | _Read from runtime environment_ | +| `aws_secret_access_key` | IAM user’s Secret Access Key | wJalrXUtnFEMI/K7MDENG/
bPxRfiCYEXAMPLEKEY | _Read from runtime environment_ | +| `aws_region` | AWS instance region | us-east-1 | _Read from runtime environment_ | +| `kms_key_id` | AWS Key Management System access key, used for secret encryption | 82065da4-3e2b-4372
-87bf-664d1e488244 | _none_ | +| `secret_name_prefix` | String prepended to each AWS Secret Manager secret name. Use this to avoid secret name conflicts in large organizations running multiple Grafana instances. | metrics-team | _none_ | +| `secret_description` | Description applied to every secret in AWS Secrets Manager. Use only for bookkeeping purposes. | Metrics team datasource | _none_ | + +### Sample configuration + +Here is a sample **config.ini** to configure the plugin and [enable migration](#migrate-your-secrets-to-the-plugin). + +```ini +[secrets] +use_plugin = true +migrate_to_plugin = true + +[plugin.grafana-aws-secretsmanager] +aws_access_key_id = AKIAIOSFODNN7EXAMPLE +aws_secret_access_key = wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY +aws_region = us-east-1 +kms_key_id = 82065da4-3e2b-4372-87bf-664d1e488244 +secret_name_prefix = my-org +secret_description = My description +``` + +## Migrate your secrets to the plugin + +You can configure Grafana to migrate your existing secrets from Grafana to the plugin on startup. This migration is a one-time blocking operation that runs on Grafana startup, meaning Grafana will not be usable until migration is complete. + +> **Note:** The speed of this migration is contingent on the number of secrets and system performance, and can run at a rate as low as two secrets per second. + +Once migration to the plugin has completed, the plugin must remain installed for Grafana to start unless backward compatibility is enabled. If the plugin is uninstalled unexpectedly, or if it fails to start for any reason, Grafana will also fail to start. + +> **Note:** Because we have not yet implemented migrations from the plugin back to Grafana's database, we strongly recommend keeping backward compatibility enabled, as is the default. + +### Initiate the migration + +To initiate secret migration from Grafana to the plugin, enable the `migrate_to_plugin` setting in the `secrets` section of the Grafana **custom.ini** file: + +```ini +[secrets] +migrate_to_plugin = true +``` + +The plugin migrates secrets individually. If backward compatibility is disabled, it also deletes them from the Grafana database. + +## Backward compatibility + +After the plugin is installed and enabled, secrets are stored by default in both AWS Secrets Manager **and** in a legacy location in the Grafana database. + +To stop storing secrets in the legacy table while the secrets plugin is enabled, disable backward compatibility by adding a [feature toggle]({{< relref "../../configure-grafana/#feature_toggles" >}}) called `disableSecretsCompatibility`: + +```ini +[feature_toggles] +enabled = disableSecretsCompatibility +``` + +While secrets will not be read from this legacy table while the plugin is active, backward compatibility allows you to uninstall the secrets plugin without losing access to all of your secrets. + +> **Note:** We have not yet implemented migrations from the plugin back to Grafana's database. Disabling backward compatibility and uninstalling the plugin can cause Grafana to fail to start. We strongly recommend keeping backward compatibility enabled, as is the default. + +## Limitations + +If your AWS Secrets Manager instance uses secret rotation, the backward compatibility feature will not be a sufficient fallback for plugin errors, because legacy secrets will not be kept up to date with AWS Secrets Manager automatically. If you plan to implement secret rotation, we recommend that you avoid installing this plugin until we implement migration from the plugin back to Grafana's database. diff --git a/docs/sources/setup-grafana/upgrade-grafana.md b/docs/sources/setup-grafana/upgrade-grafana.md index 56c5d583696..0f3cad22cf9 100644 --- a/docs/sources/setup-grafana/upgrade-grafana.md +++ b/docs/sources/setup-grafana/upgrade-grafana.md @@ -17,7 +17,7 @@ weight: 500 We recommend that you upgrade Grafana often to stay up to date with the latest fixes and enhancements. In order to make this a reality, Grafana upgrades are backward compatible and the upgrade process is simple and quick. -Upgrading is generally safe (between many minor and one major version) and dashboards and graphs will look the same. There may be minor breaking changes in some edge cases, which are outlined in the [Release Notes](https://community.grafana.com/c/releases) and [Changelog](https://github.com/grafana/grafana/blob/main/CHANGELOG.md) +Upgrading is generally safe (between many minor and one major version) and dashboards and graphs will look the same. There may be minor breaking changes in some edge cases, which are outlined in the [Release Notes](https://grafana.com/docs/grafana/latest/release-notes/) and [Changelog](https://github.com/grafana/grafana/blob/main/CHANGELOG.md) ## Backup @@ -246,7 +246,7 @@ change the `[security]` setting `cookie_secure` to `true` and use HTTPS when `co ### PhantomJS removed -PhantomJS was deprecated in [Grafana v6.4]({{< relref "../whatsnew/whats-new-in-v6-4/#phantomjs-deprecation" >}}) and starting from Grafana v7.0.0, all PhantomJS support has been removed. This means that Grafana no longer ships with a built-in image renderer, and we advise you to install the [Grafana Image Renderer plugin](https://grafana.com/grafana/plugins/grafana-image-renderer). +PhantomJS was deprecated in Grafana v6.4 and starting from Grafana v7.0.0, all PhantomJS support has been removed. This means that Grafana no longer ships with a built-in image renderer, and we advise you to install the [Grafana Image Renderer plugin](https://grafana.com/grafana/plugins/grafana-image-renderer). ### Dashboard minimum refresh interval enforced @@ -374,7 +374,7 @@ ORDER BY time There are two possible workarounds to resolve this problem: 1. In Grafana v8.0.3, use an alias of the string column selected as `metric`. for example, `hostname as metric`. -2. Use the [Standard field definitions' display name]({{< relref "../panels/standard-field-definitions/#display-name" >}}) to format the alias. For the preceding example query, you would use `${__field.labels.hostname}` option. +2. Use the [Standard field definitions' display name]({{< relref "../panels/configure-standard-options/#display-name" >}}) to format the alias. For the preceding example query, you would use `${__field.labels.hostname}` option. For more information, refer to the our relational databases documentation of [Postgres]({{< relref "../datasources/postgres/#time-series-queries" >}}), [MySQL]({{< relref "../datasources/mysql/#time-series-queries" >}}), [Microsoft SQL Server]({{< relref "../datasources/mssql/#time-series-queries" >}}). diff --git a/docs/sources/visualizations/bar-chart.md b/docs/sources/visualizations/bar-chart.md index 0dd277840b3..b03d53d07b8 100644 --- a/docs/sources/visualizations/bar-chart.md +++ b/docs/sources/visualizations/bar-chart.md @@ -157,4 +157,4 @@ Set a **Soft min** or **soft max** option for better control of Y-axis limits. B **Soft min** and **soft max** settings can prevent blips from turning into mountains when the data is mostly flat, and hard min or max derived from standard min and max field options can prevent intermittent spikes from flattening useful detail by clipping the spikes past a defined point. -You can set standard min/max options to define hard limits of the Y-axis. For more information, refer to [Standard field definitions]({{< relref "../panels/standard-field-definitions/#max" >}}). +You can set standard min/max options to define hard limits of the Y-axis. For more information, refer to [Standard options definitions]({{< relref "../panels/configure-standard-options/#max" >}}). diff --git a/docs/sources/visualizations/histogram.md b/docs/sources/visualizations/histogram.md index ae2c36d49d2..071b23fccca 100644 --- a/docs/sources/visualizations/histogram.md +++ b/docs/sources/visualizations/histogram.md @@ -50,7 +50,7 @@ Controls the fill opacity bars. ### Gradient mode -Set the mode of the gradient fill. Fill gradient is based on the line color. To change the color, use the standard [color scheme]({{< relref "../panels/working-with-panels/apply-color-to-series/" >}}) field option. +Set the mode of the gradient fill. Fill gradient is based on the line color. To change the color, use the standard [color scheme]({{< relref "../panels/configure-standard-options/#color-scheme" >}}) field option. Gradient display is influenced by the **Fill opacity** setting. diff --git a/docs/sources/visualizations/state-timeline.md b/docs/sources/visualizations/state-timeline.md index 31c76b22099..b6295cf0cf4 100644 --- a/docs/sources/visualizations/state-timeline.md +++ b/docs/sources/visualizations/state-timeline.md @@ -60,6 +60,6 @@ The panel can be used with time series data as well. In this case, the threshold ## Legend options -When the legend option is enabled it can show either the value mappings or the threshold brackets. To show the value mappings in the legend, it's important that the `Color scheme` as referenced in [Apply color to a series and fields]({{< relref "../panels/working-with-panels/apply-color-to-series/" >}}) is set to `Single color` or `Classic palette`. To see the threshold brackets in the legend set the `Color scheme` to `From thresholds`. +When the legend option is enabled it can show either the value mappings or the threshold brackets. To show the value mappings in the legend, it's important that the `Color scheme` as referenced in [Color scheme]({{< relref "../panels/configure-standard-options/#color-scheme" >}}) is set to `Single color` or `Classic palette`. To see the threshold brackets in the legend set the `Color scheme` to `From thresholds`. {{< docs/shared "visualizations/legend-mode.md" >}} diff --git a/docs/sources/visualizations/status-history.md b/docs/sources/visualizations/status-history.md index da78aa1a420..0a9429de24d 100644 --- a/docs/sources/visualizations/status-history.md +++ b/docs/sources/visualizations/status-history.md @@ -57,6 +57,6 @@ use gradient color schemes to color values. ## Legend options -When the legend option is enabled it can show either the value mappings or the threshold brackets. To show the value mappings in the legend, it's important that the `Color scheme` as referenced in [Apply color to a series and fields]({{< relref "../panels/working-with-panels/apply-color-to-series/" >}}) is set to `Single color` or `Classic palette`. To see the threshold brackets in the legend set the `Color scheme` to `From thresholds`. +When the legend option is enabled it can show either the value mappings or the threshold brackets. To show the value mappings in the legend, it's important that the `Color scheme` as referenced in [Color scheme]({{< relref "../panels/configure-standard-options/#color-scheme" >}}) is set to `Single color` or `Classic palette`. To see the threshold brackets in the legend set the `Color scheme` to `From thresholds`. {{< docs/shared "visualizations/legend-mode.md" >}} diff --git a/docs/sources/visualizations/time-series/change-axis-display.md b/docs/sources/visualizations/time-series/change-axis-display.md index cb87d3c2154..8f31bc2c191 100644 --- a/docs/sources/visualizations/time-series/change-axis-display.md +++ b/docs/sources/visualizations/time-series/change-axis-display.md @@ -70,7 +70,7 @@ Set a **Soft min** or **soft max** option for better control of Y-axis limits. B **Soft min** and **soft max** settings can prevent blips from turning into mountains when the data is mostly flat, and hard min or max derived from standard min and max field options can prevent intermittent spikes from flattening useful detail by clipping the spikes past a defined point. -You can set standard min/max options to define hard limits of the Y-axis. For more information, refer to [Standard field definitions]({{< relref "../../panels/standard-field-definitions/#max" >}}). +You can set standard min/max options to define hard limits of the Y-axis. For more information, refer to [Configure standard options]({{< relref "../../panels/configure-standard-options/#max" >}}). ![Label example](/static/img/docs/time-series-panel/axis-soft-min-max-7-4.png) diff --git a/docs/sources/visualizations/time-series/graph-color-scheme.md b/docs/sources/visualizations/time-series/graph-color-scheme.md index 78692b8005f..1dc9cb688fa 100644 --- a/docs/sources/visualizations/time-series/graph-color-scheme.md +++ b/docs/sources/visualizations/time-series/graph-color-scheme.md @@ -16,7 +16,7 @@ weight: 400 # Graph and color schemes -To set the graph and color schemes, refer to [Apply color to series and fields]({{< relref "../../panels/working-with-panels/apply-color-to-series/" >}}). +To set the graph and color schemes, refer to [Color scheme]({{< relref "../../panels/configure-standard-options/#color-scheme" >}}). ## Classic palette diff --git a/docs/sources/visualizations/time-series/graph-time-series-as-bars.md b/docs/sources/visualizations/time-series/graph-time-series-as-bars.md index aeb0ea82af0..c7afbba7cdc 100644 --- a/docs/sources/visualizations/time-series/graph-time-series-as-bars.md +++ b/docs/sources/visualizations/time-series/graph-time-series-as-bars.md @@ -83,7 +83,7 @@ Fill opacity set to 95: ### Gradient mode -Set the mode of the gradient fill. Fill gradient is based on the line color. To change the color, use the standard color scheme field option. For more information, refer to [Apply color to series and fields]({{< relref "../../panels/working-with-panels/apply-color-to-series/" >}}). +Set the mode of the gradient fill. Fill gradient is based on the line color. To change the color, use the standard color scheme field option. For more information, refer to [Color scheme]({{< relref "../../panels/configure-standard-options/#color-scheme" >}}). Gradient appearance is influenced by the **Fill opacity** setting. In the screenshots below, **Fill opacity** is set to 50. @@ -107,7 +107,7 @@ Gradient color is generated based on the hue of the line color. #### Scheme -In this mode the whole bar will use a color gradient defined by your Color scheme. For more information, refer to [Apply color to series and fields]({{< relref "../../panels/working-with-panels/apply-color-to-series/" >}}). There is more information on this option in [Graph and color scheme]({{< relref "graph-color-scheme/" >}}). +In this mode the whole bar will use a color gradient defined by your color scheme. For more information, refer to [Color scheme]({{< relref "../../panels/configure-standard-options/#color-scheme" >}}). There is more information on this option in [Graph and color scheme]({{< relref "graph-color-scheme/" >}}). {{< figure src="/static/img/docs/time-series-panel/gradient_mode_scheme_bars.png" max-width="1200px" caption="Gradient color scheme mode" >}} diff --git a/docs/sources/visualizations/time-series/graph-time-series-as-lines.md b/docs/sources/visualizations/time-series/graph-time-series-as-lines.md index d35f40b3bb2..c7e65b37093 100644 --- a/docs/sources/visualizations/time-series/graph-time-series-as-lines.md +++ b/docs/sources/visualizations/time-series/graph-time-series-as-lines.md @@ -89,7 +89,7 @@ Fill opacity set to 95: ### Gradient mode -Set the mode of the gradient fill. Fill gradient is based on the line color. To change the color, use the standard color scheme field option. For more information, refer to [Apply color to series and fields]({{< relref "../../panels/working-with-panels/apply-color-to-series/" >}}) . +Set the mode of the gradient fill. Fill gradient is based on the line color. To change the color, use the standard color scheme field option. For more information, refer to [Color scheme]({{< relref "../../panels/configure-standard-options/#color-scheme" >}}). Gradient appearance is influenced by the **Fill opacity** setting. In the screenshots below, **Fill opacity** is set to 50. @@ -113,13 +113,13 @@ Gradient color is generated based on the hue of the line color. #### Scheme -In this mode the whole line will use a color gradient defined by your Color scheme. For more information, refer to [Apply color to series and fields]({{< relref "../../panels/working-with-panels/apply-color-to-series/" >}}). There is more information on this option in [Graph and color scheme]({{< relref "graph-color-scheme/" >}}). +In this mode the whole line will use a color gradient defined by your Color scheme. For more information, refer to [Color scheme]({{< relref "../../panels/configure-standard-options/#color-scheme" >}}). There is more information on this option in [Graph and color scheme]({{< relref "graph-color-scheme/" >}}). {{< figure src="/static/img/docs/time-series-panel/gradient_mode_scheme_line.png" max-width="1200px" caption="Gradient mode scheme" >}} ### Line style -Set the style of the line. To change the color, use the standard color scheme field option. For more information, refer to [Apply color to series and fields]({{< relref "../../panels/working-with-panels/apply-color-to-series/" >}}) +Set the style of the line. To change the color, use the standard color scheme field option. For more information, refer to [Color scheme]({{< relref "../../panels/configure-standard-options/#color-scheme" >}}). Line style appearance is influenced by the **Line width** and **Fill opacity** settings. In the screenshots below, **Line width** is set to 3 and **Fill opacity** is set to 20. diff --git a/docs/sources/whatsnew/_index.md b/docs/sources/whatsnew/_index.md index 37a8c807c8e..34970d95552 100644 --- a/docs/sources/whatsnew/_index.md +++ b/docs/sources/whatsnew/_index.md @@ -2,11 +2,63 @@ aliases: - /docs/grafana/latest/guides/ - /docs/grafana/latest/whatsnew/ + - /docs/grafana/latest/guides/whats-new-in-v2/ + - /docs/grafana/latest/whatsnew/whats-new-in-v2-0/ + - /docs/grafana/latest/guides/whats-new-in-v2-1/ + - /docs/grafana/latest/whatsnew/whats-new-in-v2-1/ + - /docs/grafana/latest/guides/whats-new-in-v2-5/ + - /docs/grafana/latest/whatsnew/whats-new-in-v2-5/ + - /docs/grafana/latest/guides/whats-new-in-v2-6/ + - /docs/grafana/latest/whatsnew/whats-new-in-v2-6/ + - /docs/grafana/latest/guides/whats-new-in-v3/ + - /docs/grafana/latest/whatsnew/whats-new-in-v3-0/ + - /docs/grafana/latest/guides/whats-new-in-v3-1/ + - /docs/grafana/latest/whatsnew/whats-new-in-v3-1/ + - /docs/grafana/latest/guides/whats-new-in-v4/ + - /docs/grafana/latest/whatsnew/whats-new-in-v4-0/ + - /docs/grafana/latest/guides/whats-new-in-v4-1/ + - /docs/grafana/latest/whatsnew/whats-new-in-v4-1/ + - /docs/grafana/latest/guides/whats-new-in-v4-2/ + - /docs/grafana/latest/whatsnew/whats-new-in-v4-2/ + - /docs/grafana/latest/guides/whats-new-in-v4-3/ + - /docs/grafana/latest/whatsnew/whats-new-in-v4-3/ + - /docs/grafana/latest/guides/whats-new-in-v4-4/ + - /docs/grafana/latest/whatsnew/whats-new-in-v4-4/ + - /docs/grafana/latest/guides/whats-new-in-v4-5/ + - /docs/grafana/latest/whatsnew/whats-new-in-v4-5/ + - /docs/grafana/latest/guides/whats-new-in-v4-6/ + - /docs/grafana/latest/whatsnew/whats-new-in-v4-6/ + - /docs/grafana/latest/guides/whats-new-in-v5/ + - /docs/grafana/latest/whatsnew/whats-new-in-v5-0/ + - /docs/grafana/latest/guides/whats-new-in-v5-1/ + - /docs/grafana/latest/whatsnew/whats-new-in-v5-1/ + - /docs/grafana/latest/guides/whats-new-in-v5-2/ + - /docs/grafana/latest/whatsnew/whats-new-in-v5-2/ + - /docs/grafana/latest/guides/whats-new-in-v5-3/ + - /docs/grafana/latest/whatsnew/whats-new-in-v5-3/ + - /docs/grafana/latest/guides/whats-new-in-v5-4/ + - /docs/grafana/latest/whatsnew/whats-new-in-v5-4/ + - /docs/grafana/latest/guides/whats-new-in-v6-0/ + - /docs/grafana/latest/whatsnew/whats-new-in-v6-0/ + - /docs/grafana/latest/guides/whats-new-in-v6-1/ + - /docs/grafana/latest/whatsnew/whats-new-in-v6-1/ + - /docs/grafana/latest/guides/whats-new-in-v6-2/ + - /docs/grafana/latest/whatsnew/whats-new-in-v6-2/ + - /docs/grafana/latest/guides/whats-new-in-v6-3/ + - /docs/grafana/latest/whatsnew/whats-new-in-v6-3/ + - /docs/grafana/latest/guides/whats-new-in-v6-4/ + - /docs/grafana/latest/whatsnew/whats-new-in-v6-4/ + - /docs/grafana/latest/guides/whats-new-in-v6-5/ + - /docs/grafana/latest/whatsnew/whats-new-in-v6-5/ + - /docs/grafana/latest/guides/whats-new-in-v6-6/ + - /docs/grafana/latest/whatsnew/whats-new-in-v6-6/ + - /docs/grafana/latest/guides/whats-new-in-v6-7/ + - /docs/grafana/latest/whatsnew/whats-new-in-v6-7/ title: What's new weight: 1 --- -# What's new Grafana +# What's new in Grafana Grafana is changing all the time. For release highlights checkout links below, if you want a complete list of every change, as well as info on deprecations, breaking changes and plugin development read the [release notes]({{< relref "../release-notes/" >}}). @@ -32,22 +84,3 @@ as info on deprecations, breaking changes and plugin development read the [relea - [What's new in 7.2]({{< relref "whats-new-in-v7-2/" >}}) - [What's new in 7.1]({{< relref "whats-new-in-v7-1/" >}}) - [What's new in 7.0]({{< relref "whats-new-in-v7-0/" >}}) - -## Grafana 6 - -- [What's new in 6.7]({{< relref "whats-new-in-v6-7/" >}}) -- [What's new in 6.6]({{< relref "whats-new-in-v6-6/" >}}) -- [What's new in 6.5]({{< relref "whats-new-in-v6-5/" >}}) -- [What's new in 6.4]({{< relref "whats-new-in-v6-4/" >}}) -- [What's new in 6.3]({{< relref "whats-new-in-v6-3/" >}}) -- [What's new in 6.2]({{< relref "whats-new-in-v6-2/" >}}) -- [What's new in 6.1]({{< relref "whats-new-in-v6-1/" >}}) -- [What's new in 6.0]({{< relref "whats-new-in-v6-0/" >}}) - -## Grafana 5 - -- [What's new in 5.4]({{< relref "whats-new-in-v5-4/" >}}) -- [What's new in 5.3]({{< relref "whats-new-in-v5-3/" >}}) -- [What's new in 5.2]({{< relref "whats-new-in-v5-2/" >}}) -- [What's new in 5.1]({{< relref "whats-new-in-v5-1/" >}}) -- [What's new in 5.0]({{< relref "whats-new-in-v5-0/" >}}) diff --git a/docs/sources/whatsnew/whats-new-in-v2-0.md b/docs/sources/whatsnew/whats-new-in-v2-0.md deleted file mode 100644 index ad6dab1fc8c..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v2-0.md +++ /dev/null @@ -1,185 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v2/ - - /docs/grafana/latest/whatsnew/whats-new-in-v2-0/ -description: Feature and improvement highlights for Grafana v2.0 -keywords: - - grafana - - new - - documentation - - '2.0' - - release notes -title: What's new in Grafana v2.0 -weight: -1 ---- - -# What's new in Grafana v2.0 - -Grafana 2.0 represents months of work by the Grafana team and the community. We are pleased to be able to -release the Grafana 2.0 beta. This is a guide that describes some of changes and new features that can -be found in Grafana V2.0. - -If you are interested in how to migrate from Grafana V1.x to V2.0, please read our [Migration Guide](../installation/migrating_to2.md) - -## New backend server - -Grafana now ships with its own required backend server. Also completely open-source, it's written in Go and has a full HTTP API. - -In addition to new features, the backend server makes it much easier to set up and enjoy Grafana. Grafana 2.0 now ships as cross platform binaries with no dependencies. Authentication is built in, and Grafana is now capable of proxying connections to Data Sources. There are no longer any CORS (Cross Origin Resource Sharing) issues requiring messy workarounds. Elasticsearch is no longer required just to store dashboards. - -## User and Organization permissions - -All Dashboards and Data Sources are linked to an Organization (not to a User). Users are linked to -Organizations via a role. That role can be: - -- `Viewer`: Can only view dashboards, not save / create them. -- `Editor`: Can view, update and create dashboards. -- `Admin`: Everything an Editor can plus edit and add data sources and organization users. - -> **Note:** A `Viewer` can still view all metrics exposed through a data source, not only -> the metrics used in already existing dashboards. That is because there are not -> per series permissions in Graphite, InfluxDB or OpenTSDB. - -There are currently no permissions on individual dashboards. - -Read more about Grafana's new user model on the [Admin section](../reference/admin/) - -## Dashboard Snapshot sharing - -A Dashboard Snapshot is an easy way to create and share a URL for a stripped down, point-in-time version of any Dashboard. -You can give this URL to anyone or everyone, and they can view the Snapshot even if they're not a User of your Grafana instance. - -You can set an expiration time for any Snapshots you create. When you create a Snapshot, we strip sensitive data, like -panel metric queries, annotation and template queries and panel links. The data points displayed on -screen for that specific time period in your Dashboard is saved in the JSON of the Snapshot itself. - -Sharing a Snapshot is similar to sharing a link to a screenshot of your dashboard, only way better (they'll look great at any screen resolution, you can hover over series, -even zoom in). Also they are fast to load as they aren't actually connected to any live Data Sources in any way. - -They're a great way to communicate about a particular incident with specific people who aren't users of your Grafana instance. You can also use them to show off your dashboards over the Internet. - -![](/static/img/docs/v2/dashboard_snapshot_dialog.png) - -### Publish snapshots - -You can publish snapshots locally or to [snapshots.raintank.io](https://snapshots.raintank.io). snapshots.raintank.io is a free service provided by [Grafana Labs](https://grafana.com) for hosting external Grafana snapshots. - -Either way, anyone with the link (and access to your Grafana instance for local snapshots) can view it. - -## Panel time overrides and timeshift - -In Grafana v2.x you can now override the relative time range for individual panels, causing them to be different than what is selected in the Dashboard time picker in the upper right. You can also add a time shift to individual panels. This allows you to show metrics from different time periods or days at the same time. - -![](/static/img/docs/v2/panel_time_override.jpg) - -You control these overrides in panel editor mode and the new tab `Time Range`. - -![](/static/img/docs/v2/time_range_tab.jpg) - -When you zoom or change the Dashboard time to a custom absolute time range, all panel overrides will be disabled. The panel relative time override is only active when the dashboard time is also relative. The panel timeshift override however is always active, even when the dashboard time is absolute. - -The `Hide time override info` option allows you to hide the override info text that is by default shown in the -upper right of a panel when overridden time range options. - -Currently you can only override the dashboard time with relative time ranges, not absolute time ranges. - -## Panel iframe embedding - -You can embed a single panel on another web page or your own application using the panel share dialog. - -Below you should see an iframe with a graph panel (taken from a Dashboard snapshot at [snapshots.raintank.io](http://snapshots.raintank.io). - -Try hovering or zooming on the panel below! - - - -This feature makes it easy to include interactive visualizations from your Grafana instance anywhere you want. - -## New dashboard top header - -The top header has gotten a major streamlining in Grafana V2.0. - - - -1. `Side menubar toggle` Toggle the side menubar on or off. This allows you to focus on the data presented on the Dashboard. The side menubar provides access to features unrelated to a Dashboard such as Users, Organizations, and Data Sources. -1. `Dashboard dropdown` The main dropdown shows you which Dashboard you are currently viewing, and allows you to easily switch to a new Dashboard. From here you can also create a new Dashboard, Import existing Dashboards, and manage the Playlist. -1. `Star Dashboard`: Star (or un-star) the current Dashboard. Starred Dashboards will show up on your own Home Dashboard by default, and are a convenient way to mark Dashboards that you're interested in. -1. `Share Dashboard`: Share the current dashboard by creating a link or create a static Snapshot of it. Make sure the Dashboard is saved before sharing. -1. `Save dashboard`: Save the current Dashboard with the current name. -1. `Settings`: Manage Dashboard settings and features such as Templating, Annotations and the name. - -> **Note:** In Grafana v2.0 when you change the title of a dashboard and then save it, it will no -> longer create a new Dashboard. It will just change the name for the current Dashboard. -> To change name and create a new Dashboard use the `Save As...` menu option - -### New Side menubar - -The new side menubar provides access to features such as User Preferences, Organizations, and Data Sources. - -If you have multiple Organizations, you can easily switch between them here. - -The side menubar will become more useful as we build out additional functionality in Grafana 2.x - -You can easily collapse or re-open the side menubar at any time by clicking the Grafana icon in the top left. We never want to get in the way of the data. - -## New search view and starring dashboards - -![](/static/img/docs/v2/dashboard_search.jpg) - -The dashboard search view has gotten a big overhaul. You can now see and filter by which dashboard you have personally starred. - -## Logarithmic scale - -The Graph panel now supports 3 logarithmic scales, `log base 10`, `log base 32`, `log base 1024`. Logarithmic y-axis scales are very useful when rendering many series of different order of magnitude on the same scale (eg. -latency, network traffic, and storage) - -![](/static/img/docs/v2/graph_logbase10_ms.png) - -## Dashlist panel - -![](/static/img/docs/v2/dashlist_starred.png) - -The dashlist is a new panel in Grafana v2.0. It allows you to show your personal starred dashboards, as well as do custom searches based on search strings or tags. - -dashlist is used on the new Grafana Home screen. It is included as a reference Panel and is useful to provide basic linking between Dashboards. - -## Data Source proxy and admin views - -Data sources in Grafana v2.0 are no longer defined in a config file. Instead, they are added through the UI or the HTTP API. - -The backend can now proxy data from Data Sources, which means that it is a lot easier to get started using Grafana with Graphite or OpenTSDB without having to spend time with CORS (Cross origin resource sharing) work-arounds. - -In addition, connections to Data Sources can be better controlled and secured, and authentication information no longer needs to be exposed to the browser. - -## Dashboard "now delay" - -A commonly reported problem has been graphs dipping to zero at the end, because metric data for the last interval has yet to be written to the Data Source. These graphs then "self correct" once the data comes in, but can look deceiving or alarming at times. - -You can avoid this problem by adding a `now delay` in `Dashboard Settings` > `Time Picker` tab. This new feature will cause Grafana to ignore the most recent data up to the set delay. -![](/static/img/docs/v2/timepicker_now_delay.jpg) - -The delay that may be necessary depends on how much latency you have in your collection pipeline. - -## Dashboard overwrite protection - -Grafana v2.0 protects Users from accidentally overwriting each others Dashboard changes. Similar protections are in place if you try to create a new Dashboard with the same name as an existing one. - -![](/static/img/docs/v2/overwrite_protection.jpg) - -These protections are only the first step; we will be building out additional capabilities around dashboard versioning and management in future versions of Grafana. - -## User preferences - -If you open side menu (by clicking on the Grafana icon in the top header) you can access your Profile Page. - -Here you can update your user details, UI Theme, and change your password. - -## Server-side Panel rendering - -Grafana now supports server-side PNG rendering. From the Panel share dialog you now have access to a link that will render a particular Panel to a PNG image. - -> **Note:** This requires that your Data Source is accessible from your Grafana instance. - -![](/static/img/docs/v2/share_dialog_image_highlight.jpg) diff --git a/docs/sources/whatsnew/whats-new-in-v2-1.md b/docs/sources/whatsnew/whats-new-in-v2-1.md deleted file mode 100644 index 043e4e4910b..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v2-1.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v2-1/ - - /docs/grafana/latest/whatsnew/whats-new-in-v2-1/ -description: Feature and improvement highlights for Grafana v2.1 -keywords: - - grafana - - new - - documentation - - '2.1' - - release notes -title: What's new in Grafana v2.1 -weight: -2 ---- - -# What's new in Grafana v2.1 - -Grafana 2.1 brings improvements in three core areas: dashboarding, authentication, and data sources. -As with every Grafana release, there is a whole slew of new features, enhancements, and bug fixes. - -## More Dynamic Dashboards - -The Templating system is one of the most powerful and well-used features of Grafana. -The 2.1 release brings numerous improvements that make dashboards more dynamic than ever before. - -### Multi-Value Template Variables - -A template variable with Multi-Value enabled allows for the selection of multiple values at the same time. -These variables can then be used in any Panel to make them more dynamic, and to give you the perfect view of your data. -Multi-Value variables are also enabling the new `row repeat` and `panel repeat` feature described below. - -![Multi-Value Select](/static/img/docs/v2/multi-select.gif 'Multi-Value Select') -

- -### Repeating Rows and Panels - -It’s now possible to create a dashboard that automatically adds (or removes) both rows and panels based -on selected variable values. Any row or any panel can be configured to repeat (duplicate itself) based -on a multi-value template variable.

- -![Repeating Rows and Panels](/static/img/docs/v2/panel-row-repeat.gif 'Repeating Rows and Panels') -

- -### Dashboard Links and Navigation - -To support better navigation between dashboards, it's now possible to create custom and dynamic links from individual -panels to appropriate Dashboards. You also have the ability to create flexible top-level links on any -given dashboard thanks to the new dashboard navigation bar feature. - -![Dashboard Links](/static/img/docs/v2/dash_links.png 'Dashboard Links') - -Dashboard links can be added under dashboard settings. Either defined as static URLs with a custom icon or as dynamic -dashboard links or dropdowns based on custom dashboard search query. These links appear in the same -row under the top menu where template variables appear. - ---- - -### Better local Dashboard support - -Grafana can now index Dashboards saved locally as JSON from a given directory. These file based dashboards -will appear in the regular dashboard search along regular DB dashboards. - -> **Note:** Saving local dashboards back the folder is not supported; this feature is meant for statically generated JSON dashboards. - ---- - -## New Authentication Options - -New authentication methods add numerous options to manage users, roles and organizations. - -### LDAP support - -This highly requested feature now allows your Grafana users to login with their LDAP credentials. -You can also specify mappings between LDAP group memberships and Grafana Organization user roles. - -### Basic Auth Support - -You can now authenticate against the Grafana API utilizing a simple username and password with basic HTTP authentication. - -> **Note:** This can be useful for provisioning and configuring management systems that need -> to utilize the API without having to create an API key. - -### Auth Proxy Support - -You can now authenticate utilizing a header (eg. X-Authenticated-User, or X-WEBAUTH-USER) - -> **Note:** this can be useful in situations with reverse proxies. - -### New “Read-only Editor” User Role - -There is a new User role available in this version of Grafana: “Read-only Editor”. This role behaves just -like the Viewer role does in Grafana 2.0. That is you can edit graphs and queries but not save dashboards. -The Viewer role has been modified in Grafana 2.1 so that users assigned this role can no longer edit panels. - ---- - -## Data source Improvements - -### InfluxDB 0.9 Support - -Grafana 2.1 now comes with full support for InfluxDB 0.9. There is a new query editor designed from scratch -for the new features InfluxDB 0.9 enables. - -![InfluxDB Editor](/static/img/docs/v2/influx_09_editor_anim.gif 'InfluxDB Editor') - -
- -### OpenTSDB Improvements - -Grafana OpenTSDB data source now supports template variable values queries. This means you can create -template variables that fetches the values from OpenTSDB (for example metric names, tag names, or tag values). -The query editor is also enhanced to limiting tags by metric. - -> **Note:** OpenTSDB config option tsd.core.meta.enable_realtime_ts must enabled for OpenTSDB lookup API) - -### New Data Source: KairosDB - -The Cassandra backed time series database KairosDB is now supported in Grafana out of the box. Thank you to -masaori335 for his hard work in getting it to this point. - ---- - -## Panel Improvements - -Grafana 2.1 gives you even more flexibility customizing how individual panels render. -Overriding the colors of specific series using regular expressions, changing how series stack, -and allowing string values will help you better understand your data at a glance. - -### Graph Panel - -Define series color using regex rule. This is useful when you have templated graphs with series names -that change depending selected template variables. Using a regex style override rule you could -for example make all series that contain the word **CPU** `red` and assigned to the second y axis. - -![Define series color using regex rule](/static/img/docs/v2/regex_color_override.png 'Define series color using regex rule') - -New series style override, negative-y transform and stack groups. Negative y transform is -very useful if you want to plot a series on the negative y scale without affecting the legend values like min or max or -the values shown in the hover tooltip. - -![Negative-y Transform](/static/img/docs/v2/negative-y.png 'Negative-y Transform') - -![Negative-y Transform](/static/img/docs/v2/negative-y-form.png 'Negative-y Transform') - -### Singlestat Panel - -Now support string values. Useful for time series database like InfluxDB that supports -string values. - -### Changelog - -For a detailed list and link to github issues for everything included in the 2.1 release please -view the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file. diff --git a/docs/sources/whatsnew/whats-new-in-v2-5.md b/docs/sources/whatsnew/whats-new-in-v2-5.md deleted file mode 100644 index 599e1fbff75..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v2-5.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v2-5/ - - /docs/grafana/latest/whatsnew/whats-new-in-v2-5/ -description: Feature and improvement highlights for Grafana v2.5 -keywords: - - grafana - - new - - documentation - - '2.5' - - release notes -title: What's new in Grafana v2.5 -weight: -3 ---- - -# What's new in Grafana v2.5 - -## Release highlights - -This is an exciting release, and we want to share some of the highlights. The release includes many -fixes and enhancements to all areas of Grafana, like new Data Sources, a new and improved timepicker, user invites, panel -resize handles and improved InfluxDB and OpenTSDB support. - -### New time range controls - -New Time picker - -A new timepicker with room for more quick ranges as well as new types of relative ranges, like `Today`, -`The day so far` and `This day last week`. Also an improved time and calendar picker that now works -correctly in UTC mode. - -### Elasticsearch - -Elasticsearch example -
- -This release brings a fully featured query editor for Elasticsearch. You will now be able to visualize -logs or any kind of data stored in Elasticsearch. The query editor allows you to build both simple -and complex queries for logs or metrics. - -- Compute metrics from your documents, supported Elasticsearch aggregations: - - Count, Avg, Min, Max, Sum - - Percentiles, Std Dev, etc. -- Group by multiple terms or filters - - Specify group by options like Top 5 based on Avg @value -- Auto completion for field names -- Query only relevant indices based on time pattern -- Alias patterns for short readable series names - -Try the new Elasticsearch query editor on the [play.grafana.org](https://play.grafana.org/dashboard/db/elasticsearch-metrics) site. - -### CloudWatch - -Cloudwatch editor - -Grafana 2.5 ships with a new CloudWatch data source that will allow you to query and visualize CloudWatch -metrics directly from Grafana. - -- Rich editor with auto completion for metric names, namespaces and dimensions -- Templating queries for generic dashboards -- Alias patterns for short readable series names - -### Prometheus - -Prometheus editor - -Grafana 2.5 ships with a new Prometheus data source that will allow you to query and visualize data -stored in Prometheus. - -### Mix different data sources - -Mix data sources in the same dashboard or in the same graph! - -In previous releases you have been able to mix different data sources on the same dashboard. In v2.5 you -will be able to mix then on the same graph! You can enable this by selecting the built in `-- Mixed --` data source. -When selected this will allow you to specify data source on a per query basis. This will, for example, allow you -to plot metrics from different Graphite servers on the same Graph or plot data from Elasticsearch alongside -data from Prometheus. Mixing different data sources on the same graph works for any data source, even custom ones. - -### Panel Resize handles - - - -This release adds resize handles to the bottom right corners of panels making it easy to resize both width and height. - -### User invites - - - -This version also brings some new features for user management. - -- Organization admins can now invite new users (via email or manually via invite link) -- Users can signup using invite link and get automatically added to invited organization -- User signup workflow can (if enabled) contain an email verification step. -- Check out [#2353](https://github.com/grafana/grafana/issues/2353) for more info. - -### Miscellaneous improvements - -- InfluxDB query editor now supports math and AS expressions -- InfluxDB query editor now supports custom group by interval -- Panel drilldown link is easier to reach -- LDAP improvements (can now search for group membership if your LDAP server does not support memberOf attribute) -- More units for graph and singlestat panel (Length, Volume, Temperature, Pressure, Currency) -- Admin page for all organizations (remove / edit) - -### Breaking changes - -There have been some changes to the data source plugin API. If you are using a custom plugin check that there is an update for it before you upgrade. Also -the new time picker does not currently support custom quick ranges like the last one did. This will likely be added in a -future release. - -### Changelog - -For a detailed list and link to github issues for everything included in the 2.5 release please -view the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file. - ---- - -### Download Grafana 2.5 now diff --git a/docs/sources/whatsnew/whats-new-in-v2-6.md b/docs/sources/whatsnew/whats-new-in-v2-6.md deleted file mode 100644 index 880ee853bf5..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v2-6.md +++ /dev/null @@ -1,144 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v2-6/ - - /docs/grafana/latest/whatsnew/whats-new-in-v2-6/ -description: Feature and improvement highlights for Grafana v2.6 -keywords: - - grafana - - new - - documentation - - '2.6' - - release notes -title: What's new in Grafana v2.6 -weight: -4 ---- - -# What's new in Grafana v2.6 - -## Release highlights - -The release includes a new Table panel, a new InfluxDB query editor, support for Elasticsearch Pipeline Metrics and -support for multiple Cloudwatch credentials. - -## Table Panel - - - -The new table panel is very flexible, supporting both multiple modes for time series as well as for -table, annotation and raw JSON data. It also provides date formatting and value formatting and coloring options. - -### Time series to rows - -In the most simple mode you can turn time series to rows. This means you get a `Time`, `Metric` and a `Value` column. -Where `Metric` is the name of the time series. - - - -### Table Transform - -Above you see the options tab for the **Table Panel**. The most important option is the `To Table Transform`. -This option controls how the result of the metric/data query is turned into a table. - -### Column Styles - -The column styles allow you control how dates and numbers are formatted. - -### Time series to columns - -This transform allows you to take multiple time series and group them by time. Which will result in a `Time` column -and a column for each time series. - - - -In the screenshot above you can see how the same time series query as in the previous example can be transformed into -a different table by changing the `To Table Transform` to `Time series to columns`. - -### Time series to aggregations - -This transform works very similar to the legend values in the Graph panel. Each series gets its own row. In the Options -tab you can select which aggregations you want using the plus button the Columns section. - - - -You have to think about how accurate the aggregations will be. It depends on what aggregation is used in the time series query, -how many data points are fetched, etc. The time series aggregations are calculated by Grafana after aggregation is performed -by the time series database. - -### Raw logs queries - -If you want to show documents from Elasticsearch pick `Raw Document` as the first metric. - - - -This in combination with the `JSON Data` table transform will allow you to pick which fields in the document -you want to show in the table. - - - -### Elasticsearch aggregations - -You can also make Elasticsearch aggregation queries without a `Date Histogram`. This allows you to -use Elasticsearch metric aggregations to get accurate aggregations for the selected time range. - - - -### Annotations - -The table can also show any annotations you have enabled in the dashboard. - - - -## The New InfluxDB Editor - -The new InfluxDB editor is a lot more flexible and powerful. It supports nested functions, like `derivative`. -It also uses the same technique as the Graphite query editor in that it presents nested functions as chain of function -transformations. It tries to simplify and unify the complicated nature of InfluxDB's query language. - - - -In the `SELECT` row you can specify what fields and functions you want to use. If you have a -group by time you need an aggregation function. Some functions like derivative require an aggregation function. - -The editor tries simplify and unify this part of the query. For example: - -![](/static/img/docs/influxdb/select_editor.png) - -The above will generate the following InfluxDB `SELECT` clause: - -```sql -SELECT derivative(mean("value"), 10s) /10 AS "REQ/s" FROM .... -``` - -### Select multiple fields - -Use the plus button and select Field > field to add another SELECT clause. You can also -specify an asterix `*` to select all fields. - -### Group By - -To group by a tag click the plus icon at the end of the GROUP BY row. Pick a tag from the dropdown that appears. -You can remove the group by by clicking on the `tag` and then click on the x icon. - -The new editor also allows you to remove group by time and select `raw` table data. Which is very useful -in combination with the new Table panel to show raw log data stored in InfluxDB. - - - -## Pipeline metrics - -If you have Elasticsearch 2.x and Grafana 2.6 or above then you can use pipeline metric aggregations like -**Moving Average** and **Derivative**. Elasticsearch pipeline metrics require another metric to be based on. Use the eye icon next to the metric -to hide metrics from appearing in the graph. - -![](/static/img/docs/elasticsearch/pipeline_metrics_editor.png) - -## Changelog - -For a detailed list and link to github issues for everything included in the 2.6 release please -view the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file. - ---- - -Download Grafana 2.6 now diff --git a/docs/sources/whatsnew/whats-new-in-v3-0.md b/docs/sources/whatsnew/whats-new-in-v3-0.md deleted file mode 100644 index a0bb5c8a1e9..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v3-0.md +++ /dev/null @@ -1,236 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v3/ - - /docs/grafana/latest/whatsnew/whats-new-in-v3-0/ -description: Feature and improvement highlights for Grafana v3.0 -keywords: - - grafana - - new - - documentation - - '3.0' - - release notes -title: What's new in Grafana v3.0 -weight: -5 ---- - -# What's new in Grafana v3.0 - -## Commercial Support - -Commercial Support subscriptions for Grafana are now [generally available](https://grafana.com/support/plans/). - -Raintank is committed to a 100% open-source strategy for Grafana. We -do not want to go down the “open core” route. If your organization -finds Grafana valuable, please consider purchasing a subscription. Get -direct support, bug fixes, and training from the core Grafana team. - -## Plugins - -With the popularity of Grafana continuing to accelerate, it has been -challenging to keep up with all the requests for new features, new -panels, new data sources, and new functionality. Saying “no” so often -has been frustrating, especially for an open source project with such -a vibrant community. - -The team felt that it was time to dramatically improve extensibility -through plugin support. Grafana 3.0 comes with a completely revamped -plugin SDK / API. - -We’ve refactored our **Data Source** plugin architecture and added -two new plugin types: - -- **Panel** plugins let you add new panel types for your Dashboards. -- **App** plugins bundle **Panels** plugins, **Data Sources** plugins, - Dashboards, and Grafana **Pages**. Apps are a great way to provide an - entire experience right within Grafana. - -## Grafana.com - - - -[Grafana.com](https://grafana.com) offers a central repository where the community can come together to discover, create and -share plugins (data sources, panels, apps) and dashboards. - -We are also working on a hosted Graphite-compatible data source that will be optimized for use with Grafana. -It’ll be easy to combine your existing data source(s) with this OpenSaaS option. Finally, Grafana.com can -also be a hub to manage all your Grafana instances. You’ll be able to monitor their health and availability, -perform dashboard backups, and more. - -We are also working on a hosted Graphite-compatible Data Source that -will be optimized for use with Grafana. It’ll be easy to combine your -existing Data Source(s) with this OpenSaaS option. - -Finally, Grafana.com will also be a hub to manage all your Grafana -instances. You’ll be able to monitor their health and availability, -perform Dashboard backups, and more. - -Grafana.net will officially launch along with the stable version of -Grafana 3.0, but go to and check out the preview -and sign up for an account in the meantime. - -## grafana-cli - -Grafana 3.0 comes with a new command line tool called grafana-cli. You -can easily install plugins from Grafana.net with it. For -example: - -``` -grafana-cli install grafana-pie-chart-panel -``` - -## Personalization and Preferences - -The home dashboard, timezone and theme can now be customized on Organization -and user Profile level. Grafana can also track recently viewed dashboards, which -can then be displayed in the dashboard list panel. - -## Improved Playlists - -You can now save Playlists, and start them by using a Playlist URL. If -you update a running Playlist, it will update after its next cycle. - -This is powerful as it allows you to remote control Grafana. If you -have a big TV display showing Grafana in your company lobby, create a -playlist named Lobby, and start it on the computer connected to the -Lobby TV. - -You can now change the Lobby playlist and have the dashboards shown in -the Lobby update accordingly, automatically. - -The playlist does not even have to contain multiple Dashboards; you -can use this feature to reload the whole Dashboard (and Grafana) -periodically and remotely. - -You can also make Playlists dynamic by using Dashboard **tags** to -define the Playlist. - - - -## Improved UI - -We’ve always tried to focus on a good looking, usable, and responsive -UI. We’ve continued to pay a lot of attention to these areas in this -release. - -Grafana 3.0 has a dramatically updated UI that not only looks better -but also has a number of usability improvements. The side menu now -works as a dropdown that you can pin to the side. The Organization / -Profile / Sign out side menu links have been combined into an on hover -slide out menu. - -In addition, all the forms and the layouts of all pages have been -updated to look and flow better, and be much more consistent. There -are literally hundreds of UI improvements and refinements. - -Here’s the new side menu in action: - - - -And here's the new look for Dashboard settings: - - - -Check out the Play -Site to get a feel for some of the UI changes. - -## Improved Annotations - -It is now possible to define a link in each annotation. You can hover -over the link and click the annotation text. This feature is very -useful for linking to particular commits or tickets where more -detailed information can be presented to the user. - - - -## Data source variables - -This has been a top requested feature for very long we are excited to finally provide -this feature. You can now add a new `Data source` type variable. That will -automatically be filled with instance names of your data sources. - - - -You can then use this variable as the panel data source: - - - -This will allow you to quickly change data source server and reuse the -same dashboard for different instances of your metrics backend. For example -you might have Graphite running in multiple data centers or environments. - -## Prometheus, InfluxDB, and OpenTSDB improvements - -All three of these popular included Data Sources have seen a variety -of improvements in this release. Here are some highlights: - -### Prometheus - -The Prometheus Data Source now supports annotations. - -### InfluxDB - -You can now select the InfluxDB policy from the query editor. - - -Grafana 3.0 also comes with support for InfluxDB 0.11 and InfluxDB 0.12. - -### OpenTSDB - -OpenTSDB 2.2 is better supported and now supports millisecond precision. - -## Breaking changes - -Dashboards from v2.6 are compatible; no manual updates should be necessary. There could -be some edge case scenarios where dashboards using templating could stop working. -If that is the case just enter the edit view for the template variable and hit Update button. -This is due to a simplification of the variable format system where template variables are -now stored without any formatting (glob/regex/etc), this is done on the fly when the -variable is interpolated. - -- Plugin API: The plugin API has changed so if you are using a custom - data source (or panel) they need to be updated as well. - -- InfluxDB 0.8: This data source is no longer included in releases, - you can still install manually from [Grafana.com](https://grafana.com) - -- KairosDB: This data source has also no longer shipped with Grafana, - you can install it manually from [Grafana.com](https://grafana.com) - -## Plugin showcase - -Discovering and installing plugins is very quick and easy with Grafana 3.0 and [Grafana.com](https://grafana.com). Here -are a couple that I encourage you try! - -#### [Clock Panel](https://grafana.com/plugins/grafana-clock-panel) - -Support's both current time and count down mode. - - -#### [Pie Chart Panel](https://grafana.com/plugins/grafana-piechart-panel) - -A simple pie chart panel is now available as an external plugin. - - -#### [WorldPing App](https://grafana.com/plugins/raintank-worldping-app) - -This is full blown Grafana App that adds new panels, data sources and pages to give -feature rich global performance monitoring directly from your on-prem Grafana. - - - -#### [Zabbix App](https://grafana.com/plugins/alexanderzobnin-zabbix-app) - -This app contains the already very pouplar Zabbix data source plugin, 2 dashboards and a triggers panel. It is -created and maintained by [Alexander Zobnin](https://github.com/alexanderzobnin/grafana-zabbix). - - - -Check out the full list of plugins on [Grafana.com](https://grafana.com/plugins) - -## CHANGELOG - -For a detailed list and link to github issues for everything included -in the 3.0 release please view the -[CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file. diff --git a/docs/sources/whatsnew/whats-new-in-v3-1.md b/docs/sources/whatsnew/whats-new-in-v3-1.md deleted file mode 100644 index ba9c07cfbf7..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v3-1.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v3-1/ - - /docs/grafana/latest/whatsnew/whats-new-in-v3-1/ -description: Feature and improvement highlights for Grafana v3.1 -keywords: - - grafana - - new - - documentation - - '3.1' - - release notes -title: What's new in Grafana v3.1 -weight: -6 ---- - -# What's new in Grafana v3.1 - -## Dashboard Export and Import - -The export feature is now accessed from the share menu. - - - -Dashboards exported from Grafana 3.1 are now more portable and easier for others to import than before. The export process extracts information data source types used by panels and adds these to a new `inputs` section in the dashboard json. So when you or another person tries to import the dashboard they will be asked to select data source and optional metric prefix options. - - - -The above screenshot shows the new import modal that gives you 3 options for how to import a dashboard. One notable new addition here is the ability to import directly from Dashboards shared on [Grafana.com](https://grafana.com). - -The next step in the import process: - - - -Here you can change the name of the dashboard and also pick what data sources you want the dashboard to use. The above screenshot shows a CollectD dashboard for Graphite that requires a metric prefix be specified. - -## Discover Dashboards - -On [Grafana.com](https://grafana.com) you can now browse and search for dashboards. We have already added a few but more are being uploaded every day. To import a dashboard just copy the dashboard URL and head back to Grafana, then Dashboard Search -> Import -> Paste Grafana.com Dashboard URL. - - - -## Constant template variables - -We added a new template variable named constant that makes it easier to share and export dashboard that have custom prefixes. - -## Dashboard URLs - -Having current time range and template variable value always sync with the URL makes it possible to always copy your current Grafana URL to share with a colleague without having to use the Share modal. - -## Internal metrics - -Do you want metrics about viewing metrics? Of course you do! In this release we added support for sending metrics about Grafana to graphite. You can configure interval and server in the config file. - -## Logging - -Switched logging framework to log15 to enable key value per logging and filtering based on different log levels. It's now possible to configure different log levels for different modules. - -### Breaking changes - -- **Logging** format have been changed to improve log filtering. -- **Graphite PNG** Graphite PNG support dropped from Graph panel (use Grafana native PNG instead). -- **Migration** No longer possible to migrate dashboards from 1.x (Stored in ES or Influx 0.8). - -## CHANGELOG - -For a detailed list and link to github issues for everything included in the 3.1 release please view the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file. diff --git a/docs/sources/whatsnew/whats-new-in-v4-0.md b/docs/sources/whatsnew/whats-new-in-v4-0.md deleted file mode 100644 index 8d175914f15..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v4-0.md +++ /dev/null @@ -1,184 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v4/ - - /docs/grafana/latest/whatsnew/whats-new-in-v4-0/ -description: Feature and improvement highlights for Grafana v4.0 -keywords: - - grafana - - new - - documentation - - '4.0' - - release notes -title: What's new in Grafana v4.0 -weight: -7 ---- - -# What's new in Grafana v4.0 - -As usual this release contains a ton of minor new features, fixes and improved UX. But on top of the usual new goodies -is a core new feature: Alerting! Read on below for a detailed description of what's new in v4.0. - -## Alerting - -{{< figure class="float-right" max-width="40%" src="/static/img/docs/v4/drag_handles_gif.gif" caption="Alerting overview" >}} - -Alerting is a really revolutionary feature for Grafana. It transforms Grafana from a -visualization tool into a truly mission critical monitoring tool. The alert rules are very easy to -configure using your existing graph panels and threshold levels can be set simply by dragging handles to -the right side of the graph. The rules will continually be evaluated by grafana-server and -notifications will be sent out when the rule conditions are met. - -This feature has been worked on for over a year with many iterations and rewrites -just to make sure the foundations are really solid. We are really proud to finally release it! -Since the alerting execution is processed in the backend not all data source plugins are supported. -Right now Graphite, Prometheus, InfluxDB and OpenTSDB are supported. Elasticsearch is being worked -on but will be not ready for v4 release. - -
- -### Rules - -{{< figure class="float-right" max-width="40%" src="/static/img/docs/v4/alerting_conditions.png" caption="Alerting Conditions" >}} - -The rule configuration allows you to specify a name, how often the rule should be evaluated and a series -of conditions that all need to be true for the alert to fire. - -Currently the only condition type that exists is a `Query` condition that allows you to -specify a query letter, time range and an aggregation function. The letter refers to -a query you already have added in the **Metrics** tab. The result from the -query and the aggregation function is a single value that is then used in the threshold check. - -We plan to add other condition types in the future, like `Other Alert`, where you can include the state -of another alert in your conditions, and `Time Of Day`. - -### Notifications - -{{< figure class="float-right" max-width="40%" src="/static/img/docs/v4/slack_notification.png" caption="Alerting Slack Notification" >}} - -Alerting would not be very useful if there was no way to send notifications when rules trigger and change state. You -can set up notifications of different types. We currently have `Slack`, `PagerDuty`, `Email` and `Webhook` with more in the -pipe that will be added during beta period. The notifications can then be added to your alert rules. -If you have configured an external image store in the grafana.ini config file (s3, webdav, and azure_blob options available) -you can get very rich notifications with an image of the graph and the metric -values all included in the notification. - -### Annotations - -Alert state changes are recorded in a new annotation store that is built into Grafana. This store -currently only supports storing annotations in Grafana's own internal database (mysql, postgres or sqlite). -The Grafana annotation storage is currently only used for alert state changes but we hope to add the ability for users -to add graph comments in the form of annotations directly from within Grafana in a future release. - -### Alert List Panel - -{{< figure class="float-right" max-width="30%" src="/static/img/docs/v4/alert_list_panel.png" caption="Alert List Panel" >}} - -This new panel allows you to show alert rules or a history of alert rule state changes. You can filter based on states you are -interested in. This panel is very useful for overview style dashboards. - -
- -## Ad-hoc filter variable - -{{< figure class="float-right" max-width="30%" src="/static/img/docs/v4/adhoc_filters.gif" caption="Ad-hoc filters variable" >}} - -This is a new and very different type of template variable. It will allow you to create new key/value filters on the fly -with autocomplete for both key and values. The filter condition will be automatically applied to all -queries that use that data source. This feature opens up more exploratory dashboards. In the gif animation to the right -you have a dashboard for Elasticsearch log data. It uses one query variable that allow you to quickly change how the data -is grouped, and an interval variable for controlling the granularity of the time buckets. What was missing -was a way to dynamically apply filters to the log query. With the `Ad-Hoc Filters` variable you can -dynamically add filters to any log property! - -## UX Improvements - -We always try to bring some UX/UI refinements and polish in every release. - -### TV-mode and Kiosk mode - -
-
-

- Grafana is so often used on wall mounted TVs that we figured a clean TV mode would be - really nice. In TV mode the top navbar, row and panel controls will all fade to transparent. -

- -

- This happens automatically after one minute of user inactivity but can also be toggled manually - with the d v sequence shortcut. Any mouse movement or keyboard action will - restore navbar and controls. -

- -

- Another feature is the kiosk mode. This can be enabled with d k - shortcut or by adding &kiosk to the URL when you load a dashboard. - In kiosk mode the navbar is completely hidden/removed from view. -

- -
-
- {{< figure src="/static/img/docs/v4/tvmode.png" caption="TV mode" >}} - -
-
- -### New row menu and add panel experience - -{{< figure class="float-right" max-width="50%" src="/static/img/docs/v4/add_panel.gif" caption="Add Panel flow" >}} - -We spent a lot of time improving the dashboard building experience to make it both -more efficient and easier for beginners. After many good but not great experiments -with a `build mode` we eventually decided to just improve the green row menu and -continue work on a `build mode` for a future release. - -The new row menu automatically slides out when you mouse over the edge of the row. You no longer need -to hover over the small green icon and then click it to expand the row menu. - -There are some minor improvements to drag and drop behavior. Now when dragging a panel from one row -to another you will insert the panel and Grafana will automatically make room for it. -When you drag a panel within a row you will simply reorder the panels. - -If you look at the animation to the right you can see that you can drag and drop a new panel. This is not -required, you can also just click the panel type and it will be inserted at the end of the row -automatically. Dragging a new panel has an advantage in that you can insert a new panel where ever you want -not just at the end of the row. - -We plan to further improve dashboard building in the future with a more rich grid and layout system. - -### Keyboard shortcuts - -{{< figure class="float-right" max-width="40%" src="/static/img/docs/v4/shortcuts.png" caption="Shortcuts" >}} - -Grafana v4 introduces a number of really powerful keyboard shortcuts. You can now focus a panel -by hovering over it with your mouse. With a panel focused you can simply hit `e` to toggle panel -edit mode, or `v` to toggle fullscreen mode. `p r` removes the panel. `p s` opens share -modal. - -Some nice navigation shortcuts are: - -- `g h` for go to home dashboard -- `s s` open search with starred pre-selected -- `s t` open search in tags list view - -
- -## Upgrade and Breaking changes - -There are no breaking changes. Old dashboards and features should work the same. Grafana-server will automatically upgrade its db -schema on restart. It's advisable to do a backup of Grafana's database before updating. - -If you are using plugins make sure to update your plugins as some might not work perfectly v4. - -You can update plugins using grafana-cli - - grafana-cli plugins update-all - -## Changelog - -Check out the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file for a complete list -of new features, changes, and bug fixes. diff --git a/docs/sources/whatsnew/whats-new-in-v4-1.md b/docs/sources/whatsnew/whats-new-in-v4-1.md deleted file mode 100644 index da51f5185bb..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v4-1.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v4-1/ - - /docs/grafana/latest/whatsnew/whats-new-in-v4-1/ -description: Feature and improvement highlights for Grafana v4.1 -keywords: - - grafana - - new - - documentation - - 4.1.0 - - release notes -title: What's new in Grafana v4.1 -weight: -8 ---- - -## What's new in Grafana v4.1 - -- **Graph**: Support for shared tooltip on all graphs as you hover over one graph. [#1578](https://github.com/grafana/grafana/pull/1578), [#6274](https://github.com/grafana/grafana/pull/6274) -- **Victorops**: Add VictorOps notification integration [#6411](https://github.com/grafana/grafana/issues/6411), thx [@ichekrygin](https://github.com/ichekrygin) -- **Opsgenie**: Add OpsGenie notification integratiion [#6687](https://github.com/grafana/grafana/issues/6687), thx [@kylemcc](https://github.com/kylemcc) -- **Cloudwatch**: Make it possible to specify access and secret key on the data source configuration page [#6697](https://github.com/grafana/grafana/issues/6697) -- **Elasticsearch**: Added support for Elasticsearch 5.x [#5740](https://github.com/grafana/grafana/issues/5740), thx [@lpic10](https://github.com/lpic10) -- **Panel**: Added help text for panels. [#4079](https://github.com/grafana/grafana/issues/4079), thx [@utkarshcmu](https://github.com/utkarshcmu) -- [Full changelog](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) - -### Shared tooltip - -{{< figure class="float-right" max-width="60%" src="/static/img/docs/v41/shared_tooltip.gif" caption="Shared tooltip" >}} - -Showing the tooltip on all panels at the same time has been a long standing request in Grafana and we are really happy to finally be able to release it. -You can enable/disable the shared tooltip from the dashboard settings menu or cycle between default, shared tooltip and shared crosshair by pressing Ctrl/Cmd+O. - -
- -### Help text for panel - -{{< figure class="float-right" max-width="60%" src="/static/img/docs/v41/helptext_for_panel_settings.png" caption="Hovering help text" >}} - -You can set a help text in the general tab on any panel. The help text is using Markdown to enable better formatting and linking to other sites that can provide more information. - -
- -{{< figure class="float-right" max-width="60%" src="/static/img/docs/v41/helptext_hover.png" caption="Hovering help text" >}} - -Panels with a help text available have a little indicator in the top left corner. You can show the help text by hovering the icon. - -
- -### Easier Cloudwatch configuration - -{{< figure class="float-right" max-width="60%" src="/static/img/docs/v41/cloudwatch_settings.png" caption="Cloudwatch configuration" >}} - -In Grafana 4.1.0 you can configure your Cloudwatch data source with `access key` and `secret key` directly in the data source configuration page. -This enables people to use the Cloudwatch data source without having access to the filesystem where Grafana is running. - -Once the `access key` and `secret key` have been saved the user will no longer be able to view them. - -
- -## Upgrade and Breaking changes - -Elasticsearch 1.x is no longer supported. Please upgrade to Elasticsearch 2.x or 5.x. Otherwise Grafana 4.1.0 contains no breaking changes. - -## Changelog - -Check out the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file for a complete list -of new features, changes, and bug fixes. - -## Download - -Head to [v4.1 download page](/download/4_1_0/) for download links and instructions. - -## Thanks - -A big thanks to all the Grafana users who contribute by submitting PRs, bug reports and feedback! diff --git a/docs/sources/whatsnew/whats-new-in-v4-2.md b/docs/sources/whatsnew/whats-new-in-v4-2.md deleted file mode 100644 index f9edad7d673..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v4-2.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v4-2/ - - /docs/grafana/latest/whatsnew/whats-new-in-v4-2/ -description: Feature and improvement highlights for Grafana v4.2 -keywords: - - grafana - - new - - documentation - - 4.2.0 - - release notes -title: What's new in Grafana v4.2 -weight: -9 ---- - -## What's new in Grafana v4.2 - -Grafana v4.2 Beta is now [available for download](https://grafana.com/grafana/download/4.2.0). -Just like the last release this one contains lots bug fixes and minor improvements. -We are very happy to say that 27 of 40 issues was closed by pull requests from the community. -Big thumbs up! - -## Release Highlights - -- **Hipchat**: Adds support for sending alert notifications to hipchat [#6451](https://github.com/grafana/grafana/issues/6451), thx [@jregovic](https://github.com/jregovic) -- **Telegram**: Added Telegram alert notifier [#7098](https://github.com/grafana/grafana/pull/7098), thx [@leonoff](https://github.com/leonoff) -- **LINE**: Add LINE as alerting notification channel [#7301](https://github.com/grafana/grafana/pull/7301), thx [@huydx](https://github.com/huydx) -- **Templating**: Make $**interval and $**interval_ms global built in variables that can be used in by any data source (in panel queries), closes [#7190](https://github.com/grafana/grafana/issues/7190), closes [#6582](https://github.com/grafana/grafana/issues/6582) -- **Alerting**: Adds deduping of alert notifications [#7632](https://github.com/grafana/grafana/pull/7632) -- **Alerting**: Better information about why an alert triggered [#7035](https://github.com/grafana/grafana/issues/7035) -- **Orgs**: Sharing dashboards using Grafana share feature will now redirect to correct org. [#6948](https://github.com/grafana/grafana/issues/6948) -- [Full changelog](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) - -### New alert notification channels - -This release adds **five** new alert notifications channels, all of them contributed by the community. - -- Hipchat -- Telegram -- LINE -- Pushover -- Threema - -### Templating - -We added two new global built in variables in grafana. `$__interval` and `$__interval_ms` are now reserved template names in grafana and can be used by any data source. -We might add more global built in variables in the future and if we do we will prefix them with `$__`. So please avoid using that in your template variables. - -### Dedupe alert notifications when running multiple servers - -In this release we will dedupe alert notifications when you are running multiple servers. -This makes it possible to run alerting on multiple servers and only get one notification. - -We currently solve this with sql transactions which puts some limitations for how many servers you can use to execute the same rules. -3-5 servers should not be a problem but as always, it depends on how many alerts you have and how frequently they execute. - -Next up for a better HA situation is to add support for workload balancing between Grafana servers. - -### Alerting more info - -You can now see the reason why an alert triggered in the alert history. Its also easier to detect when an alert is set to `alerting` due to the `no_data` option. - -### Improved support for multi-org setup - -When loading dashboards we now set an query parameter called orgId. So we can detect from which org an user shared a dashboard. -This makes it possible for users to share dashboards between orgs without changing org first. - -We aim to introduce [dashboard groups](https://github.com/grafana/grafana/issues/1611) sometime in the future which will introduce access control and user groups within one org. -Making it possible to have users in multiple groups and have detailed access control. - -## Upgrade and Breaking changes - -If you're using HTTPS in grafana we now force you to use TLS 1.2 and the most secure ciphers. -We think its better to be secure by default rather then making it configurable. -If you want to run HTTPS with lower versions of TLS we suggest you put a reserve proxy in front of grafana. - -If you have template variables name `$__interval` or `$__interval_ms` they will no longer work since these keywords -are reserved as global built in variables. We might add more global built in variables in the future and if we do, we will prefix them with `$__`. So please avoid using that in your template variables. - -## Changelog - -Check out the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file for a complete list -of new features, changes, and bug fixes. - -## Download - -Head to [v4.2-beta download page](/download/4_2_0/) for download links and instructions. - -## Thanks - -A big thanks to all the Grafana users who contribute by submitting PRs, bug reports and feedback! diff --git a/docs/sources/whatsnew/whats-new-in-v4-3.md b/docs/sources/whatsnew/whats-new-in-v4-3.md deleted file mode 100644 index 00ce76ba40c..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v4-3.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v4-3/ - - /docs/grafana/latest/whatsnew/whats-new-in-v4-3/ -description: Feature and improvement highlights for Grafana v4.3 -keywords: - - grafana - - new - - documentation - - 4.3.0 - - release notes -title: What's new in Grafana v4.3 -weight: -10 ---- - -## What's new in Grafana v4.3 - -Grafana v4.3 Beta is now [available for download](https://grafana.com/grafana/download/4.3.0-beta1). - -## Release Highlights - -- New [Heatmap Panel](http://docs.grafana.org/features/panels/heatmap/) -- Graph Panel Histogram Mode -- Elasticsearch Histogram Aggregation -- Prometheus Table data format -- New [MySQL Data Source](http://docs.grafana.org/features/datasources/mysql/) (alpha version to get some early feedback) -- 60+ small fixes and improvements, most of them contributed by our fantastic community! - -Check out the [New Features in v4.3 Dashboard](https://play.grafana.org/dashboard/db/new-features-in-v4-3?orgId=1) on the Grafana Play site for a showcase of these new features. - -## Histogram Support - -A Histogram is a kind of bar chart that groups numbers into ranges, often called buckets or bins. Taller bars show that more data falls in that range. - -The Graph Panel now supports Histograms. - -![](/static/img/docs/v43/heatmap_histogram.png) - -## Histogram Aggregation Support for Elasticsearch - -Elasticsearch is the only supported data source that can return pre-bucketed data (data that is already grouped into ranges). With other data sources there is a risk of returning inaccurate data in a histogram due to using already aggregated data rather than raw data. This release adds support for Elasticsearch pre-bucketed data that can be visualized with the new [Heatmap Panel](http://docs.grafana.org/features/panels/heatmap/). - -## Heatmap Panel - -The Histogram support in the Graph Panel does not show changes over time - it aggregates all the data together for the chosen time range. To visualize a histogram over time, we have built a new [Heatmap Panel](http://docs.grafana.org/features/panels/heatmap/). - -Every column in a Heatmap is a histogram snapshot. Instead of visualizing higher values with higher bars, a heatmap visualizes higher values with color. The histogram shown above is equivalent to one column in the heatmap shown below. - -![](/static/img/docs/v43/heatmap_histogram_over_time.png) - -The Heatmap panel also works with Elasticsearch Histogram Aggregations for more accurate server side bucketing. - -![](/assets/img/blog/v4/elastic_heatmap.jpg) - -## MySQL Data Source (alpha) - -This release includes a [new core data source for MySQL](http://docs.grafana.org/features/datasources/mysql/). You can write any possible MySQL query and format it as either Time Series or Table Data allowing it be used with the Graph Panel, Table Panel and SingleStat Panel. - -We are still working on the MySQL data source. As it's missing some important features, like templating and macros and future changes could be breaking, we are -labeling the state of the data source as Alpha. Instead of holding up the release of v4.3 we are including it in its current shape to get some early feedback. So please try it out and let us know what you think on [twitter](https://twitter.com/intent/tweet?text=.%40grafana&source=4_3_beta_blog&related=blog) or on our [community forum](https://community.grafana.com/c/releases). Is this a feature that you would use? How can we make it better? - -**The query editor can show the generated and interpolated SQL that is sent to the MySQL server.** - -![](/static/img/docs/v43/mysql_table_query.png) - -**The query editor will also show any errors that resulted from running the query (very useful when you have a syntax error!).** - -![](/static/img/docs/v43/mysql_query_error.png) - -## Health Check Endpoint - -Now you can monitor the monitoring with the Health Check Endpoint! The new `/api/health` endpoint returns HTTP 200 OK if everything is up and HTTP 503 Error if the Grafana database cannot be pinged. - -## Lazy Load Panels - -Grafana now delays loading panels until they become visible (scrolled into view). This means panels out of view are not sending requests thereby reducing the load on your time series database. - -## Prometheus - Table Data (column per label) - -The Prometheus data source now supports the Table Data format by automatically assigning a column to a label. This makes it really easy to browse data in the table panel. - -![](/static/img/docs/v43/prom_table_cols_as_labels.png) - -## Other Highlights From The Changelog - -Changes: - -- **Table**: Support to change column header text [#3551](https://github.com/grafana/grafana/issues/3551) -- **InfluxDB**: influxdb query builder support for ORDER BY and LIMIT (allows TOPN queries) [#6065](https://github.com/grafana/grafana/issues/6065) Support influxdb's SLIMIT Feature [#7232](https://github.com/grafana/grafana/issues/7232) thx [@thuck](https://github.com/thuck) -- **Graph**: Support auto grid min/max when using log scale [#3090](https://github.com/grafana/grafana/issues/3090), thx [@bigbenhur](https://github.com/bigbenhur) -- **Prometheus**: Make Prometheus query field a textarea [#7663](https://github.com/grafana/grafana/issues/7663), thx [@hagen1778](https://github.com/hagen1778) -- **Server**: Support listening on a Unix socket [#4030](https://github.com/grafana/grafana/issues/4030), thx [@mitjaziv](https://github.com/mitjaziv) - -Fixes: - -- **MySQL**: 4-byte UTF8 not supported when using MySQL database (allows Emojis in Dashboard Names) [#7958](https://github.com/grafana/grafana/issues/7958) -- **Dashboard**: Description tooltip is not fully displayed [#7970](https://github.com/grafana/grafana/issues/7970) - -Lots more enhancements and fixes can be found in the [Changelog](https://github.com/grafana/grafana/blob/master/CHANGELOG.md). - -## Download - -Head to the [v4.3 download page](https://grafana.com/grafana/download) for download links and instructions. - -## Thanks - -A big thanks to all the Grafana users who contribute by submitting PRs, bug reports, helping out on our [community site](https://community.grafana.com/) and providing feedback! diff --git a/docs/sources/whatsnew/whats-new-in-v4-4.md b/docs/sources/whatsnew/whats-new-in-v4-4.md deleted file mode 100644 index e2bc015c9ae..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v4-4.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v4-4/ - - /docs/grafana/latest/whatsnew/whats-new-in-v4-4/ -description: Feature and improvement highlights for Grafana v4.4 -keywords: - - grafana - - new - - documentation - - 4.4.0 - - release notes -title: What's new in Grafana v4.4 -weight: -11 ---- - -## What's new in Grafana v4.4 - -Grafana v4.4 is now [available for download](https://grafana.com/grafana/download/4.4.0). - -**Highlights**: - -- Dashboard History - version control for dashboards. - -## New Features - -**Dashboard History**: View dashboard version history, compare any two versions (summary and json diffs), restore to old version. This big feature -was contributed by **Walmart Labs**. Big thanks to them for this massive contribution! -Initial feature request: [#4638](https://github.com/grafana/grafana/issues/4638) -Pull Request: [#8472](https://github.com/grafana/grafana/pull/8472) - -## Enhancements - -- **Elasticsearch**: Added filter aggregation label [#8420](https://github.com/grafana/grafana/pull/8420), thx [@tianzk](github.com/tianzk) -- **Sensu**: Added option for source and handler [#8405](https://github.com/grafana/grafana/pull/8405), thx [@joemiller](github.com/joemiller) -- **CSV**: Configurable csv export datetime format [#8058](https://github.com/grafana/grafana/issues/8058), thx [@cederigo](github.com/cederigo) -- **Table Panel**: Column style that preserves formatting/indentation (like pre tag) [#6617](https://github.com/grafana/grafana/issues/6617) -- **DingDing**: Add DingDing Alert Notifier [#8473](https://github.com/grafana/grafana/pull/8473) thx [@jiamliang](https://github.com/jiamliang) - -## Minor Enhancements - -- **Elasticsearch**: Add option for result set size in raw_document [#3426](https://github.com/grafana/grafana/issues/3426) [#8527](https://github.com/grafana/grafana/pull/8527), thx [@mk-dhia](github.com/mk-dhia) - -## Bug Fixes - -- **Graph**: Bug fix for negative values in histogram mode [#8628](https://github.com/grafana/grafana/issues/8628) - -## Download - -Head to the [v4.4 download page](https://grafana.com/grafana/download) for download links and instructions. - -## Thanks - -A big thanks to all the Grafana users who contribute by submitting PRs, bug reports, helping out on our [community site](https://community.grafana.com/) and providing feedback! diff --git a/docs/sources/whatsnew/whats-new-in-v4-5.md b/docs/sources/whatsnew/whats-new-in-v4-5.md deleted file mode 100644 index d62a0c88fdc..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v4-5.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v4-5/ - - /docs/grafana/latest/whatsnew/whats-new-in-v4-5/ -description: Feature and improvement highlights for Grafana v4.5 -keywords: - - grafana - - new - - documentation - - '4.5' - - release notes -title: What's new in Grafana v4.5 -weight: -12 ---- - -# What's new in Grafana v4.5 - -## Highlights - -### New prometheus query editor - -The new query editor has full syntax highlighting. As well as auto complete for metrics, functions, and range vectors. There are also integrated function docs right from the query editor! - -{{< figure src="/static/img/docs/v45/prometheus_query_editor_still.png" class="docs-image--block" animated-gif="/static/img/docs/v45/prometheus_query_editor.gif" >}} - -### Elasticsearch: Add ad-hoc filters from the table panel - -{{< figure src="/static/img/docs/v45/elastic_ad_hoc_filters.png" class="docs-image--block" >}} - -### Table cell links! - -Create column styles that turn cells into links that use the value in the cell (or other row values) to generate a URL to another dashboard or system: -![](/static/img/docs/v45/table_links.jpg) - -### Query Inspector - -Query Inspector is a new feature that shows query requests and responses. This can be helpful if a graph is not shown or shows something very different than what you expected. -For more information about query inspector, refer to [using grafanas query inspector to troubleshoot issues](https://community.grafana.com/t/using-grafanas-query-inspector-to-troubleshoot-issues/2630). -![](/static/img/docs/v45/query_inspector.png) - -## Changelog - -### New Features - -- **Table panel**: Render cell values as links that can have an URL template that uses variables from current table row. [#3754](https://github.com/grafana/grafana/issues/3754) -- **Elasticsearch**: Add ad hoc filters directly by clicking values in table panel [#8052](https://github.com/grafana/grafana/issues/8052). -- **MySQL**: New rich query editor with syntax highlighting -- **Prometheus**: New rich query editor with syntax highlighting, metric and range auto complete and integrated function docs. [#5117](https://github.com/grafana/grafana/issues/5117) - -### Enhancements - -- **GitHub OAuth**: Support for GitHub organizations with 100+ teams. [#8846](https://github.com/grafana/grafana/issues/8846), thx [@skwashd](https://github.com/skwashd) -- **Graphite**: Calls to Graphite API /metrics/find now include panel or dashboard time range (from and until) in most cases, [#8055](https://github.com/grafana/grafana/issues/8055) -- **Graphite**: Added new graphite 1.0 functions, available if you set version to 1.0.x in data source settings. New Functions: mapSeries, reduceSeries, isNonNull, groupByNodes, offsetToZero, grep, weightedAverage, removeEmptySeries, aggregateLine, averageOutsidePercentile, delay, exponentialMovingAverage, fallbackSeries, integralByInterval, interpolate, invert, linearRegression, movingMin, movingMax, movingSum, multiplySeriesWithWildcards, pow, powSeries, removeBetweenPercentile, squareRoot, timeSlice, closes [#8261](https://github.com/grafana/grafana/issues/8261) -- **Elasticsearch**: Ad-hoc filters now use query phrase match filters instead of term filters, works on non keyword/raw fields [#9095](https://github.com/grafana/grafana/issues/9095). - -### Breaking change - -- **InfluxDB/Elasticsearch**: The panel and data source option named "Group by time interval" is now named "Min time interval" and does now always define a lower limit for the auto group by time. Without having to use `>` prefix (that prefix still works). This should in theory have close to zero actual impact on existing dashboards. It does mean that if you used this setting to define a hard group by time interval of, say "1d", if you zoomed to a time range wide enough the time range could increase above the "1d" range as the setting is now always considered a lower limit. - -This option is now renamed (and moved to Options sub section above your queries): -![image|519x120](upload://ySjHOVpavV6yk9LHQxL9nq2HIsT.png) - -Data source selection and options and help are now above your metric queries. -![image|690x179](upload://5kNDxKgMz1BycOKgG3iWYLsEVXv.png) - -### Minor Changes - -- **InfluxDB**: Change time range filter for absolute time ranges to be inclusive instead of exclusive [#8319](https://github.com/grafana/grafana/issues/8319), thx [@Oxydros](https://github.com/Oxydros) -- **InfluxDB**: Added parenthesis around tag filters in queries [#9131](https://github.com/grafana/grafana/pull/9131) - -## Bug Fixes - -- **Modals**: Maintain scroll position after opening/leaving modal [#8800](https://github.com/grafana/grafana/issues/8800) -- **Templating**: You cannot select data source variables as data source for other template variables [#7510](https://github.com/grafana/grafana/issues/7510) diff --git a/docs/sources/whatsnew/whats-new-in-v4-6.md b/docs/sources/whatsnew/whats-new-in-v4-6.md deleted file mode 100644 index aadce439fe9..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v4-6.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v4-6/ - - /docs/grafana/latest/whatsnew/whats-new-in-v4-6/ -description: Feature and improvement highlights for Grafana v4.6 -keywords: - - grafana - - new - - documentation - - '4.6' - - release notes -title: What's new in Grafana v4.6 -weight: -13 ---- - -# What's new in Grafana v4.6 - -Grafana v4.6 brings many enhancements to Annotations, Cloudwatch and Prometheus. It also adds support for Postgres as metric and table data source! - -### Annotations - -{{< figure src="/static/img/docs/v46/add_annotation_region.png" max-width= "800px" >}} - -You can now add annotation events and regions right from the graph panel! Just hold Ctrl/Cmd+Click or drag region to open the **Add Annotation** view. The -[Annotations]({{< relref "../dashboards/annotations/" >}}) documentation is updated to include details on this new exciting feature. - -### Cloudwatch - -Cloudwatch now supports alerting. Set up alert rules for any Cloudwatch metric! - -{{< figure src="/static/img/docs/v46/cloudwatch_alerting.png" max-width= "800px" >}} - -### Postgres - -Grafana v4.6 now ships with a built-in data source plugin for Postgres. Have logs or metric data in Postgres? You can now visualize that data and -define alert rules on it like any of our other data sources. - -{{< figure src="/static/img/docs/v46/postgres_table_query.png" max-width= "800px" >}} - -### Prometheus - -New enhancements include support for **instant queries** and improvements to query editor in the form of autocomplete for label names and label values. -This makes exploring and filtering Prometheus data much easier. - -## Changelog - -### New Features - -- **GCS**: Adds support for Google Cloud Storage [#8370](https://github.com/grafana/grafana/issues/8370) thx [@chuhlomin](https://github.com/chuhlomin) -- **Prometheus**: Adds /metrics endpoint for exposing Grafana metrics. [#9187](https://github.com/grafana/grafana/pull/9187) -- **Graph**: Add support for local formatting in axis. [#1395](https://github.com/grafana/grafana/issues/1395), thx [@m0nhawk](https://github.com/m0nhawk) -- **Jaeger**: Add support for open tracing using jaeger in Grafana. [#9213](https://github.com/grafana/grafana/pull/9213) -- **Unit types**: New date and time unit types added, useful in singlestat to show dates and times. [#3678](https://github.com/grafana/grafana/issues/3678), [#6710](https://github.com/grafana/grafana/issues/6710), [#2764](https://github.com/grafana/grafana/issues/2764) -- **CLI**: Make it possible to install plugins from any URL [#5873](https://github.com/grafana/grafana/issues/5873) -- **Prometheus**: Add support for instant queries [#5765](https://github.com/grafana/grafana/issues/5765), thx [@mtanda](https://github.com/mtanda) -- **Cloudwatch**: Add support for alerting using the cloudwatch data source [#8050](https://github.com/grafana/grafana/pull/8050), thx [@mtanda](https://github.com/mtanda) -- **Pagerduty**: Include triggering series in pagerduty notification [#8479](https://github.com/grafana/grafana/issues/8479), thx [@rickymoorhouse](https://github.com/rickymoorhouse) -- **Timezone**: Time ranges like Today and Yesterday now work correctly when timezone setting is set to UTC [#8916](https://github.com/grafana/grafana/issues/8916), thx [@ctide](https://github.com/ctide) -- **Prometheus**: Align $\_\_interval with the step parameters. [#9226](https://github.com/grafana/grafana/pull/9226), thx [@alin-amana](https://github.com/alin-amana) -- **Prometheus**: Autocomplete for label name and label value [#9208](https://github.com/grafana/grafana/pull/9208), thx [@mtanda](https://github.com/mtanda) -- **Postgres**: New Postgres data source [#9209](https://github.com/grafana/grafana/pull/9209), thx [@svenklemm](https://github.com/svenklemm) -- **Data sources**: closes [#9371](https://github.com/grafana/grafana/issues/9371), [#5334](https://github.com/grafana/grafana/issues/5334), [#8812](https://github.com/grafana/grafana/issues/8812), thx [@mattbostock](https://github.com/mattbostock) - -### Minor Changes - -- **SMTP**: Make it possible to set specific EHLO for SMTP client. [#9319](https://github.com/grafana/grafana/issues/9319) -- **Dataproxy**: Allow Grafana to renegotiate TLS connection [#9250](https://github.com/grafana/grafana/issues/9250) -- **HTTP**: set net.Dialer.DualStack to true for all HTTP clients [#9367](https://github.com/grafana/grafana/pull/9367) -- **Alerting**: Add diff and percent diff as series reducers [#9386](https://github.com/grafana/grafana/pull/9386), thx [@shanhuhai5739](https://github.com/shanhuhai5739) -- **Slack**: Allow images to be uploaded to slack when Token is present [#7175](https://github.com/grafana/grafana/issues/7175), thx [@xginn8](https://github.com/xginn8) -- **Opsgenie**: Use their latest API instead of old version [#9399](https://github.com/grafana/grafana/pull/9399), thx [@cglrkn](https://github.com/cglrkn) -- **Table**: Add support for displaying the timestamp with milliseconds [#9429](https://github.com/grafana/grafana/pull/9429), thx [@s1061123](https://github.com/s1061123) -- **Hipchat**: Add metrics, message and image to hipchat notifications [#9110](https://github.com/grafana/grafana/issues/9110), thx [@eloo](https://github.com/eloo) -- **Postgres**: modify group by time macro so it can be used in select clause [#9527](https://github.com/grafana/grafana/pull/9527), thanks [@svenklemm](https://github.com/svenklemm) - -### Tech - -- **Go**: Grafana is now built using golang 1.9 diff --git a/docs/sources/whatsnew/whats-new-in-v5-0.md b/docs/sources/whatsnew/whats-new-in-v5-0.md deleted file mode 100644 index 9f28601180d..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v5-0.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v5/ - - /docs/grafana/latest/whatsnew/whats-new-in-v5-0/ -description: Feature and improvement highlights for Grafana v5.0 -keywords: - - grafana - - new - - documentation - - '5.0' - - release notes -title: What's new in Grafana v5.0 -weight: -14 ---- - -# What's new in Grafana v5.0 - -This is the most substantial update that Grafana has ever seen. This article will detail the major new features and enhancements. - -- [New Dashboard Layout Engine]({{< relref "#new-dashboard-layout-engine" >}}) enables a much easier drag, drop and resize experience and new types of layouts. -- [New UX]({{< relref "#new-ux-layout-engine" >}}). The UI has big improvements in both look and function. -- [New Light Theme]({{< relref "#new-light-theme" >}}) is now looking really nice. -- [Dashboard Folders]({{< relref "#dashboard-folders" >}}) helps you keep your dashboards organized. -- [Permissions]({{< relref "#dashboard-folders" >}}) on folders and dashboards helps manage larger Grafana installations. -- [Group users into teams]({{< relref "#teams" >}}) and use them in the new permission system. -- [Data source provisioning]({{< relref "#data-sources" >}}) makes it possible to set up data sources via config files. -- [Dashboard provisioning]({{< relref "#dashboards" >}}) makes it possible to set up dashboards via config files. -- [Persistent dashboard URL's]({{< relref "#dashboard-model-persistent-url-s-and-api-changes" >}}) makes it possible to rename dashboards without breaking links. -- [Graphite Tags and Integrated Function Docs]({{< relref "#graphite-tags-integrated-function-docs" >}}). - -### Video showing new features - - -
- -## New Dashboard Layout Engine - -{{< figure src="/static/img/docs/v50/new_grid.png" max-width="1000px" class="docs-image--right">}} - -The new dashboard layout engine allows for much easier movement and sizing of panels, as other panels now move out of the way in -a very intuitive way. Panels are sized independently, so rows are no longer necessary to create layouts. This opens -up many new types of layouts where panels of different heights can be aligned easily. Check out the new grid in the video -above or on the [play site](https://play.grafana.org). All your existing dashboards will automatically migrate to the -new position system and look close to identical. The new panel position makes dashboards saved in v5.0 incompatible -with older versions of Grafana. - -
- -## New UX - -{{< figure src="/static/img/docs/v50/new_ux_nav.png" max-width="1000px" class="docs-image--right" >}} - -Almost every page has seen significant UX improvements. All pages (except dashboard pages) have a new tab-based layout that improves navigation between pages. The side menu has also changed quite a bit. You can still hide the side menu completely if you click on the Grafana logo. - -
- -## Dashboard Settings - -{{< figure src="/static/img/docs/v50/dashboard_settings.png" max-width="1000px" class="docs-image--right" >}} -Dashboard pages have a new header toolbar where buttons and actions are now all moved to the right. All the dashboard -settings views have been combined with a side nav which allows you to easily move between different setting categories. - -
- -## New Light Theme - -{{< figure src="/static/img/docs/v50/new_white_theme.png" max-width="1000px" class="docs-image--right" >}} - -This theme has not seen a lot of love in recent years and we felt it was time to give it a major overhaul. We are very happy with the result. - -
- -## Dashboard Folders - -{{< figure src="/static/img/docs/v50/new_search.png" max-width="1000px" class="docs-image--right" >}} - -The big new feature that comes with Grafana v5.0 is dashboard folders. Now you can organize your dashboards in folders, -which is very useful if you have a lot of dashboards or multiple teams. - -- New search design adds expandable sections for each folder, starred and recently viewed dashboards. -- New manage dashboard pages enable batch actions and views for folder settings and permissions. -- Set permissions on folders and have dashboards inherit the permissions. - -## Teams - -A team is a new concept in Grafana v5. They are simply a group of users that can be used in the new permission system for dashboards and folders. Only an admin can create teams. -We hope to do more with teams in future releases like integration with LDAP and a team landing page. - -## Permissions - -{{< figure src="/static/img/docs/v50/folder_permissions.png" max-width="1000px" class="docs-image--right" >}} - -You can assign permissions to folders and dashboards. The default user role-based permissions can be removed and -replaced with specific teams or users enabling more control over what a user can see and edit. - -Dashboard permissions only limits what dashboards and folders a user can view and edit not which -data sources a user can access nor what queries a user can issue. - -
- -## Provisioning from configuration - -In previous versions of Grafana, you could only use the API for provisioning data sources and dashboards. -But that required the service to be running before you started creating dashboards and you also needed to -set up credentials for the HTTP API. In v5.0 we decided to improve this experience by adding a new active -provisioning system that uses config files. This will make GitOps more natural as data sources and dashboards can -be defined via files that can be version controlled. We hope to extend this system to later add support for users, orgs -and alerts as well. - -### Data sources - -Data sources can now be set up using config files. These data sources are by default not editable from the Grafana GUI. -It's also possible to update and delete data sources from the config file. More info in the [data source provisioning docs](/administration/provisioning/#datasources). - -### Dashboards - -We also deprecated the `[dashboard.json]` in favor of our new dashboard provisioner that keeps dashboards on disk -in sync with dashboards in Grafana's database. The dashboard provisioner has multiple advantages over the old -`[dashboard.json]` feature. Instead of storing the dashboard in memory we now insert the dashboard into the database, -which makes it possible to star them, use one as the home dashboard, set permissions and other features in Grafana that -expects the dashboards to exist in the database. More info in the [dashboard provisioning docs]({{< relref "../administration/provisioning/" >}}) - -## Graphite Tags and Integrated Function Docs - -{{< figure src="/static/img/docs/v50/graphite_tags.png" max-width="1000px" class="docs-image--right" >}} - -The Graphite query editor has been updated to support the latest Graphite version (v1.2) that adds -many new functions and support for querying by tags. You can now also view function documentation right in the query editor! - -Read more on [Graphite Tag Support](http://graphite.readthedocs.io/en/latest/tags.html?highlight=tags). - -
- -## Dashboard model, persistent URLs and API changes - -We are introducing a new unique identifier (`uid`) in the dashboard JSON model. It's automatically -generated if not provided when creating a dashboard and will have a length of 9-12 characters. - -The unique identifier allows having persistent URLs for accessing dashboards, sharing them -between instances and when using [dashboard provisioning](<(/administration/provisioning/#reusable-dashboard-urls)>). This means that dashboard can -be renamed without breaking any links. We're changing the URL format for dashboards -from `/dashboard/db/:slug` to `/d/:uid/:slug`. We'll keep supporting the old slug-based URLs for dashboards -and redirects to the new one for backward compatibility. Please note that the old slug-based URLs -have been deprecated and will be removed in a future release. - -Sharing dashboards between instances becomes much easier since the `uid` is unique (unique enough). -This might seem like a small change, but we are incredibly excited about it since it will make it -much easier to manage, collaborate and navigate between dashboards. - -### API changes - -New uid-based routes in the dashboard API have been introduced to retrieve and delete dashboards. -The corresponding slug-based routes have been deprecated and will be removed in a future release. diff --git a/docs/sources/whatsnew/whats-new-in-v5-1.md b/docs/sources/whatsnew/whats-new-in-v5-1.md deleted file mode 100644 index 0076840701e..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v5-1.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v5-1/ - - /docs/grafana/latest/whatsnew/whats-new-in-v5-1/ -description: Feature and improvement highlights for Grafana v5.1 -keywords: - - grafana - - new - - documentation - - '5.1' - - release notes -title: What's new in Grafana v5.1 -weight: -15 ---- - -# What's new in Grafana v5.1 - -Grafana v5.1 brings new features, many enhancements and bug fixes. This article will detail the major new features and enhancements. - -- [Improved scrolling experience]({{< relref "#improved-scrolling-experience" >}}) -- [Improved docker image]({{< relref "#improved-docker-image-breaking-change" >}}) with a breaking change! -- [Heatmap support for Prometheus]({{< relref "#prometheus" >}}) -- [Microsoft SQL Server]({{< relref "#microsoft-sql-server" >}}) as metric and table data source! -- [Dashboards and Panels]({{< relref "#dashboards-panels" >}}) Improved adding panels to dashboards and enhancements to Graph and Table panels. -- [New variable interpolation syntax]({{< relref "#new-variable-interpolation-syntax" >}}) -- [Improved workflow for provisioned dashboards]({{< relref "#improved-workflow-for-provisioned-dashboards" >}}) - -## Improved scrolling experience - -In Grafana v5.0 we introduced a new scrollbar component. Unfortunately this introduced a lot of issues and in some scenarios removed -the native scrolling functionality. Grafana v5.1 ships with a native scrollbar for all pages together with a scrollbar component for -the dashboard grid and panels that's not overriding the native scrolling functionality. We hope that these changes and improvements should -make the Grafana user experience much better! - -## Improved Docker image (breaking change) - -Grafana v5.1 brings an improved official docker image which should make it easier to run and use the Grafana docker image and at the same time give more control to the user how to use/run it. - -We've switched the id of the grafana user running Grafana inside a docker container. Unfortunately this means that files created prior to 5.1 won't have the correct permissions for later versions and thereby this introduces a breaking change. -We made this change so that it would be easier for you to control what user Grafana is executed as (see examples below). - -| Version | User | User ID | -| ------- | ------- | ------- | -| < 5.1 | grafana | 104 | -| >= 5.1 | grafana | 472 | - -Please read the [updated documentation](/installation/docker/#migrate-to-v51-or-later) which includes migration instructions and more information. - -## Prometheus - -{{< figure src="/static/img/docs/v51/prometheus_heatmap.png" max-width="800px" class="docs-image--right" >}} - -The Prometheus data source now support transforming Prometheus histograms to the heatmap panel. Prometheus histogram is a powerful feature, and we're -really happy to finally allow our users to render those as heatmaps. Please read [Heatmap panel documentation](/features/panels/heatmap/#pre-bucketed-data) -for more information on how to use it. - -Prometheus query editor also got support for autocomplete of template variables. More information in the [Prometheus data source documentation]({{< relref "../datasources/prometheus/" >}}). - -
- -## Microsoft SQL Server - -{{< figure src="/static/img/docs/v51/mssql_query_editor_showcase.png" max-width= "800px" class="docs-image--right" >}} - -Grafana v5.1 now ships with a built-in Microsoft SQL Server (MSSQL) data source plugin that allows you to query and visualize data from any -Microsoft SQL Server 2005 or newer, including Microsoft Azure SQL Database. Do you have metric or log data in MSSQL? You can now visualize -that data and define alert rules on it like with any of Grafana's other core data sources. - -Please read [Using Microsoft SQL Server in Grafana documentation]({{< relref "../datasources/mssql/" >}}) for more detailed information on how to get started and use it. - -
- -## Dashboards and Panels - -### Adding new panels to dashboards - -{{< figure src="/static/img/docs/v51/dashboard_add_panel.png" max-width= "800px" class="docs-image--right" >}} - -The control for adding new panels to dashboards have got some enhancements and now includes functionality to search for the type of panel -you want to add. Further, the control has tabs separating functionality for adding new panels and pasting -copied panels. - -By copying a panel in a dashboard it will be displayed in the `Paste` tab in _any_ dashboard and allows you to paste the -copied panel into the current dashboard. - -{{< figure src="/static/img/docs/v51/dashboard_panel_copy.png" max-width= "300px" >}} - -
- -### Graph Panel - -New enhancements include support for multiple series stacking in histogram mode, thresholds for right Y axis, aligning left and right Y-axes to one level and additional units. More information in the [Graph panel documentation]({{< relref "../visualizations/graph-panel/" >}}). - -### Table Panel - -New enhancements include support for mapping a numeric value/range to text and additional units. More information in the [Table panel documentation](/features/panels/table_panel/#string). - -## New variable interpolation syntax - -We now support a new option for rendering variables that gives the user full control of how the value(s) should be rendered. -In the table below you can see some examples and you can find all different options in the [Variables documentation](http://docs.grafana.org/variables/templates-and-variables/#advanced-formatting-options). - -| Filter Option | Example | Raw | Interpolated | Description | -| ------------- | ---------------- | ------------------ | -------------------------------- | --------------------------------------------------------- | -| `glob` | ${servers:glob} | `'test1', 'test2'` | `{test1,test2}` | Formats multi-value variable into a glob | -| `regex` | ${servers:regex} | `'test.', 'test2'` | (test\.|test2) | Formats multi-value variable into a regex string | -| `pipe` | ${servers:pipe} | `'test.', 'test2'` | test.|test2 | Formats multi-value variable into a pipe-separated string | -| `csv` | ${servers:csv} | `'test1', 'test2'` | `test1,test2` | Formats multi-value variable as a comma-separated string | - -## Improved workflow for provisioned dashboards - -{{< figure src="/static/img/docs/v51/provisioning_cannot_save_dashboard.png" max-width="800px" class="docs-image--right" >}} - -Grafana v5.1 brings an improved workflow for provisioned dashboards: - -- A populated `id` property in JSON is now automatically removed when provisioning dashboards. -- When making changes to a provisioned dashboard you can `Save` the dashboard which now will bring up a _Cannot save provisioned dashboard_ dialog like seen in the screenshot to the right. - -Available options in the dialog will let you `Copy JSON to Clipboard` and/or `Save JSON to file` which can help you synchronize your dashboard changes back to the provisioning source. -More information in the [Provisioning documentation](/administration/provisioning/). - -
- -## Changelog - -Check out the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file for a complete list -of new features, changes, and bug fixes. diff --git a/docs/sources/whatsnew/whats-new-in-v5-2.md b/docs/sources/whatsnew/whats-new-in-v5-2.md deleted file mode 100644 index 37847ba8837..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v5-2.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v5-2/ - - /docs/grafana/latest/whatsnew/whats-new-in-v5-2/ -description: Feature and improvement highlights for Grafana v5.2 -keywords: - - grafana - - new - - documentation - - '5.2' - - release notes -title: What's new in Grafana v5.2 -weight: -16 ---- - -# What's new in Grafana v5.2 - -Grafana v5.2 brings new features, many enhancements and bug fixes. This article will detail the major new features and enhancements. - -- [Elasticsearch alerting]({{< relref "#elasticsearch-alerting" >}}) it's finally here! -- [Native builds for ARM]({{< relref "#native-builds-for-arm" >}}) native builds of Grafana for many more platforms! -- [Improved Docker image]({{< relref "#improved-docker-image" >}}) with support for docker secrets -- [Security]({{< relref "#security" >}}) make your Grafana instance more secure -- [Prometheus]({{< relref "#prometheus" >}}) with alignment enhancements -- [InfluxDB]({{< relref "#influxdb" >}}) now supports the `mode` function -- [Alerting]({{< relref "#alerting" >}}) with alert notification channel type for Discord -- [Dashboards and Panels]({{< relref "#dashboards-panels" >}}) with save and import enhancements - -## Elasticsearch alerting - -{{< figure src="/static/img/docs/v52/elasticsearch_alerting.png" max-width="800px" class="docs-image--right" >}} - -Grafana v5.2 ships with an updated Elasticsearch data source with support for alerting. Alerting support for Elasticsearch has been one of -the most requested features by our community and now it's finally here. Please try it out and let us know what you think. - -
- -## Native builds for ARM - -Grafana v5.2 brings an improved build pipeline with cross-platform support. This enables native builds of Grafana for ARMv7 (x32) and ARM64 (x64). -We've been longing for native ARM build support for ages. With the help from our amazing community this is now finally available. -Please try it out and let us know what you think. - -Another great addition with the improved build pipeline is that binaries for macOS/Darwin (x64) and Windows (x64) are now automatically built and -published for both stable and nightly builds. - -## Improved Docker image - -The Grafana docker image adds support for Docker secrets which enables you to supply Grafana with configuration through files. More -information in the [Installing using Docker documentation](/installation/docker/#reading-secrets-from-files-support-for-docker-secrets). - -## Security - -{{< figure src="/static/img/docs/v52/login_change_password.png" max-width="800px" class="docs-image--right" >}} - -Starting from Grafana v5.2, when you login with the administrator account using the default password you'll be presented with a form to change the password. -We hope this encourages users to follow Grafana's best practices and change the default administrator password. - -
- -## Prometheus - -The Prometheus data source now aligns the start/end of the query sent to Prometheus with the step, which ensures PromQL expressions with _rate_ -functions get consistent results, and thus avoids graphs jumping around on reload. - -## InfluxDB - -The InfluxDB data source now includes support for the _mode_ function which returns the most frequent value in a list of field values. - -## Alerting - -By popular demand Grafana now includes support for an alert notification channel type for [Discord](https://discordapp.com/). - -## Dashboards and Panels - -### Modified time range and variables are no longer saved by default - -{{< figure src="/static/img/docs/v52/dashboard_save_modal.png" max-width="800px" class="docs-image--right" >}} - -Starting from Grafana v5.2, a modified time range or variable are no longer saved by default. To save a modified -time range or variable, you'll need to actively select that when saving a dashboard, see screenshot. -This should hopefully make it easier to have same defaults for time and variables in dashboards and make it more explicit -when you actually want to overwrite those settings. - -
- -### Import dashboard enhancements - -{{< figure src="/static/img/docs/v52/dashboard_import.png" max-width="800px" class="docs-image--right" >}} - -Grafana v5.2 adds support for specifying an existing folder or creating a new one when importing a dashboard - a long-awaited feature since -Grafana v5.0 introduced support for dashboard folders and permissions. The import dashboard page has also got some general improvements -and should now make it more clear if a possible import will overwrite an existing dashboard, or not. - -This release also adds some improvements for those users only having editor or admin permissions in certain folders. The links to -_Create Dashboard_ and _Import Dashboard_ are now available in the side navigation, in dashboard search and on the manage dashboards/folder page for a -user that has editor role in an organization or the edit permission in at least one folder. - -
- -## Changelog - -Check out the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file for a complete list -of new features, changes, and bug fixes. diff --git a/docs/sources/whatsnew/whats-new-in-v5-3.md b/docs/sources/whatsnew/whats-new-in-v5-3.md deleted file mode 100644 index 260f06a1e0b..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v5-3.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v5-3/ - - /docs/grafana/latest/whatsnew/whats-new-in-v5-3/ -description: Feature and improvement highlights for Grafana v5.3 -keywords: - - grafana - - new - - documentation - - '5.3' - - release notes -title: What's new in Grafana v5.3 -weight: -17 ---- - -# What's new in Grafana v5.3 - -Grafana v5.3 brings new features, many enhancements and bug fixes. This article will detail the major new features and enhancements. - -- [Google Stackdriver]({{< relref "#google-stackdriver" >}}) as a core data source! -- [TV mode]({{< relref "#tv-and-kiosk-mode" >}}) is improved and more accessible -- [Alerting]({{< relref "#notification-reminders" >}}) with notification reminders -- [Postgres]({{< relref "#postgres-query-builder" >}}) gets a new query builder! -- [OAuth]({{< relref "#improved-oauth-support-for-gitlab" >}}) support for GitLab is improved -- [Annotations]({{< relref "#annotations" >}}) with template variable filtering -- [Variables]({{< relref "#variables" >}}) with free text support - -## Google Stackdriver - -{{< figure src="/static/img/docs/v53/stackdriver-with-heatmap.png" max-width= "600px" class="docs-image--no-shadow docs-image--right" >}} - -Grafana v5.3 ships with built-in support for [Google Stackdriver](https://cloud.google.com/stackdriver/) and enables you to visualize your Stackdriver metrics in Grafana. - -Getting started with the plugin is easy. Simply create a GCE Service account that has access to the Stackdriver API scope, download the Service Account key file from Google and upload it on the Stackdriver data source configuration page in Grafana and you should have a secure server-to-server authentication setup. Like other core plugins, Stackdriver has built-in support for alerting. It also comes with support for heatmaps and basic variables. - -If you're already accustomed to the Stackdriver Metrics Explorer UI, you'll notice that there are a lot of similarities to the query editor in Grafana. It is possible to add filters using wildcards and regular expressions. You can do Group By, Primary Aggregation and Alignment. - -Alias By allows you to format the legend the way you want, and it's a feature that is not yet present in the Metrics Explorer. Two other features that are only supported in the Grafana plugin are the abilities to manually set the Alignment Period in the query editor and to add Annotations queries. - -The Grafana Stackdriver plugin comes with support for automatic unit detection. Grafana will try to map the Stackdriver unit type to a corresponding unit type in Grafana, and if successful the panel Y-axes will be updated accordingly to display the correct unit of measure. This is the first core plugin to provide support for unit detection, and it is our intention to provide support for this in other core plugins in the near future. - -The data source is still in the `beta` phase, meaning it's currently in active development and is still missing one important feature - templating queries. -Please try it out, but be aware of that it might be subject to changes and possible bugs. We would love to hear your feedback. - -Refer to [Using Google Stackdriver in Grafana]({{< relref "../datasources/google-cloud-monitoring/" >}}) for more detailed information on how to get started and use it. - -## TV and Kiosk Mode - -{{< figure src="/static/img/docs/v53/tv_mode_still.png" max-width="600px" class="docs-image--no-shadow docs-image--right" animated-gif="/static/img/docs/v53/tv_mode.gif" >}} - -We've improved the TV and kiosk mode to make it easier to use. There's now an icon in the top bar that will let you cycle through the different view modes. - -1. In the first view mode, the sidebar and most of the buttons in the top bar will be hidden. -1. In the second view mode, the top bar is completely hidden so that only the dashboard itself is shown. -1. Hit the escape key to go back to the default view mode. - -When switching view modes, the URL will be updated to reflect the view mode selected. This allows a dashboard to be opened with a -certain view mode enabled. Additionally, this also enables [playlists](/dashboards/playlist) to be started with a certain view mode enabled. - -
- -## Notification Reminders - -Do you use Grafana Alerting and have some notifications that are more important than others? Then it's possible to set reminders so that you continue to be alerted until the problem is fixed. This is done on the notification channel itself and will affect all alerts that use that channel. -For additional examples of why reminders might be useful for you, see [multiple series](/alerting/alerts-overview/#multiple-series). - -For more information about how to enable and configure reminders, refer to [alerting reminders](/alerting/notifications/#send-reminders). - -## Postgres Query Builder - -Grafana 5.3 comes with a new graphical query builder for Postgres. This brings Postgres integration more in line with some of the other data sources and makes it easier for both advanced users and beginners to work with timeseries in Postgres. For more information about Postgres graphical query builder, refer to [query editor]({{< relref "../datasources/postgres/#query-editor" >}}). - -{{< figure src="/static/img/docs/v53/postgres_query_still.png" class="docs-image--no-shadow" animated-gif="/static/img/docs/v53/postgres_query.gif" >}} - -## Improved OAuth Support for GitLab - -Grafana 5.3 comes with a new OAuth integration for GitLab that enables configuration to only allow users that are a member of certain GitLab groups to authenticate. This makes it possible to use GitLab OAuth with Grafana in a shared environment without giving everyone access to Grafana. -For more information about how to enable and configure OAuth, refer to [Gitlab OAuth](/auth/gitlab/). - -## Annotations - -Grafana 5.3 brings improved support for [native annotations](/dashboards/annotations/#native-annotations) and makes it possible to use template variables when filtering by tags. -For more information about native annotation, refer to [query by tag](/dashboards/annotations/#query-by-tag). - -{{< figure src="/static/img/docs/v53/annotation_tag_filter_variable.png" max-width="600px" >}} - -## Variables - -Grafana 5.3 ships with a brand new variable type named `Text box` which makes it easier and more convenient to provide free text input to a variable. -This new variable type will display as a free text input field with an optional prefilled default value. - -## Changelog - -Check out the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file for a complete list -of new features, changes, and bug fixes. diff --git a/docs/sources/whatsnew/whats-new-in-v5-4.md b/docs/sources/whatsnew/whats-new-in-v5-4.md deleted file mode 100644 index 8630cbdfbd1..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v5-4.md +++ /dev/null @@ -1,88 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v5-4/ - - /docs/grafana/latest/whatsnew/whats-new-in-v5-4/ -description: Feature and improvement highlights for Grafana v5.4 -keywords: - - grafana - - new - - documentation - - '5.4' - - release notes -title: What's new in Grafana v5.4 -weight: -18 ---- - -# What's new in Grafana v5.4 - -Grafana v5.4 brings new features, many enhancements and bug fixes. This article will detail the major new features and enhancements. - -- [Alerting]({{< relref "#alerting" >}}) Limit false positives with the new `For` setting -- [Google Stackdriver]({{< relref "#google-stackdriver" >}}) Now with support for templating queries -- [MySQL]({{< relref "#mysql-query-builder" >}}) gets a new query builder! -- [Graph Panel]({{< relref "#graph-panel-enhancements" >}}) Highlight time regions and more -- [Team Preferences]({{< relref "#team-preferences" >}}) Give your teams their own home dashboard - -## Alerting - -{{< figure src="/static/img/docs/v54/alerting-for-dark-theme.png" max-width="600px" class="docs-image--right" >}} - -Grafana v5.4 ships with a new alert rule setting named `For` which is great for removing false positives. If an alert rule has a configured `For` and the query violates the configured threshold it will first go from `OK` to `Pending`. Going from `OK` to `Pending` Grafana will not send any notifications. Once the alert rule has been firing for more than `For` duration, it will change to `Alerting` and send alert notifications. Typically, it's always a good idea to use this setting since it's often worse to get false positive than wait a few minutes before the alert notification triggers. - -In the screenshot you can see an example timeline of an alert using the `For` setting. At ~16:04 the alert state changes to `Pending` and after 4 minutes it changes to `Alerting` which is when alert notifications are sent. Once the series falls back to normal the alert rule goes back to `OK`. [Learn more](/alerting/alerts-overview/#for). - -Additionally, there's now support for disable the sending of `OK` alert notifications. [Learn more](/alerting/notifications/#disable-resolve-message). - -
- -## Google Stackdriver - -{{< figure src="/static/img/docs/v54/stackdriver_template_query.png" max-width="600px" class="docs-image--right" >}} - -Grafana v5.3 included built-in support for [Google Stackdriver](https://cloud.google.com/stackdriver/) which enables you to visualize your Stackdriver metrics in Grafana. -One important feature missing was support for templating queries. This is now included together with a brand new templating query editor for Stackdriver. - -The Stackdriver templating query editor lets you choose from a set of different Query Types. This will in turn reveal additional drop-downs to help you -find, filter and select the templating values you're interested in, see screenshot for details. The templating query editor also supports chaining multiple variables -making it easy to define variables that's dependent on other variables. - -Stackdriver is the first data source which has support for a custom templating query editor. But starting from Grafana v5.4 it's now possible for all data sources, including plugin data sources, to -create their very own templating query editor. - -Additionally, if Grafana is running on a Google Compute Engine (GCE) virtual machine, it is now possible for Grafana to automatically retrieve default credentials from the metadata server. -This has the advantage of not needing to generate a private key file for the service account and also not having to upload the file to Grafana. [Learn more]({{< relref "../datasources/google-cloud-monitoring/#using-gce-default-service-account" >}}). - -Please read [Using Google Stackdriver in Grafana]({{< relref "../datasources/google-cloud-monitoring/" >}}) for more detailed information on how to get started and use it. - -
- -## MySQL Query Builder - -Grafana v5.4 comes with a new graphical query builder for MySQL. This brings MySQL integration more in line with some of the other data sources and makes it easier for both advanced users and beginners to work with timeseries in MySQL. For more information about MySQL graphical query builder, refer to [query editor]({{< relref "../datasources/mysql/#query-editor" >}}). - -{{< figure src="/static/img/docs/v54/mysql_query_still.png" animated-gif="/static/img/docs/v54/mysql_query.gif" >}} - -## Graph Panel Enhancements - -Grafana v5.4 adds support for highlighting weekdays and/or certain timespans in the graph panel. This should make it easier to compare for example weekends, business hours and/or off work hours. - -{{< figure src="/static/img/docs/v54/graph_time_regions.png" max-width= "800px" >}} - -Additionally, when rendering series as lines in the graph panel, should there be only one data point available for one series so that a connecting line cannot be established, a point will -automatically be rendered for that data point. This should make it easier to understand what's going on when only receiving a single data point. - -{{< figure src="/static/img/docs/v54/graph_dot_single_point.png" max-width= "800px" >}} - -## Team Preferences - -Grafana v5.4 adds support for customizing home dashboard, timezone and theme for teams, in addition to the existing customization on Organization and user Profile level. - -1. Specifying a preference on User Profile level will override preference on Team and/or Organization level -1. Specifying a preference on Team level will override preference on Organization level. - -## Changelog - -Check out the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file for a complete list -of new features, changes, and bug fixes. diff --git a/docs/sources/whatsnew/whats-new-in-v6-0.md b/docs/sources/whatsnew/whats-new-in-v6-0.md deleted file mode 100644 index d6068ed4680..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v6-0.md +++ /dev/null @@ -1,181 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v6-0/ - - /docs/grafana/latest/whatsnew/whats-new-in-v6-0/ -description: Feature and improvement highlights for Grafana v6.0 -keywords: - - grafana - - new - - documentation - - '6.0' - - release notes -title: What's new in Grafana v6.0 -weight: -19 ---- - -# What's new in Grafana v6.0 - -This update to Grafana introduces a new way of exploring your data, support for log data, and tons of other features. - -The main highlights are: - -- [Explore]({{< relref "#explore" >}}) - A new query focused workflow for ad-hoc data exploration and troubleshooting. -- [Grafana Loki]({{< relref "#explore-and-grafana-loki" >}}) - Integration with the new open source log aggregation system from Grafana Labs. -- [Gauge Panel]({{< relref "#gauge-panel" >}}) - A new standalone panel for gauges. -- [New Panel Editor UX]({{< relref "#new-panel-editor" >}}) improves panel editing - and enables easy switching between different visualizations. -- [Google Stackdriver data source]({{< relref "#google-stackdriver-data-source" >}}) is out of beta and is officially released. -- [Azure Monitor]({{< relref "#azure-monitor-data-source" >}}) plugin is ported from being an external plugin to be a core data source -- [React Plugin]({{< relref "#react-panels-query-editors" >}}) support enables an easier way to build plugins. -- [Named Colors]({{< relref "#named-colors" >}}) in our new improved color picker. -- [Removal of user session storage]({{< relref "#easier-to-deploy-improved-security" >}}) makes Grafana easier to deploy and improves security. - -## Explore - -{{< figure src="/static/img/docs/v60/explore_prometheus.png" max-width="800px" class="docs-image--right" caption="Screenshot of the new Explore option in the panel menu" >}} - -Grafana's dashboard UI is all about building dashboards for visualization. **Explore** strips away all the dashboard and panel options so that you can focus on the query and metric exploration. Iterate until you have a working query and then think about building a dashboard. You can also jump from a dashboard panel into **Explore** and from there do some ad-hoc query exploration with the panel queries as a starting point. - -For infrastructure monitoring and incident response, you no longer need to switch to other tools to debug what went wrong. **Explore** allows you to dig deeper into your metrics and logs to find the cause. Grafana's new logging data source, [Loki](https://github.com/grafana/loki) is tightly integrated into Explore and allows you to correlate metrics and logs by viewing them side-by-side. - -**Explore** is a new paradigm for Grafana. It creates a new interactive debugging workflow that integrates two pillars -of observability—metrics and logs. Explore works with every data source but for Prometheus we have customized the -query editor and the experience to provide the best possible exploration UX. - -### Explore and Prometheus - -Explore features a new [Prometheus query editor](/explore/#prometheus-specific-features). This new editor has improved autocomplete, metric tree selector, -integrations with the Explore table view for easy label filtering, and useful query hints that can automatically apply -functions to your query. There is also integration between Prometheus and Grafana Loki (see more about Loki below) that -enabled jumping between metrics query and logs query with preserved label filters. - -### Explore splits - -Explore supports splitting the view so you can compare different queries, different data sources and metrics and logs side by side! - -{{< figure src="/static/img/docs/v60/explore_split.png" max-width="800px" caption="Screenshot of the new Explore option in the panel menu" >}} - -
- -### Explore and Grafana Loki - -The log exploration and visualization features in Explore are available to any data source but are currently only implemented by the new open source log -aggregation system from Grafana Lab called [Grafana Loki](https://github.com/grafana/loki). - -Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus. It is designed to be very cost effective, as it does not index the contents of the logs, but rather a set of labels for each log stream. The logs from Loki are queried in a similar way to querying with label selectors in Prometheus. It uses labels to group log streams which can be made to match up with your Prometheus labels. - -For more information about Grafana Loki, refer to [Github Grafana Loki](https://github.com/grafana/loki) or [Grafana Labs hosted Loki](https://grafana.com/loki). - -The Explore feature allows you to query logs and features a new log panel. In the near future, we will be adding support -for other log sources to Explore and the next planned integration is Elasticsearch. - -
- -
- -
- -## New Panel Editor - -Grafana v6.0 has a completely redesigned UX around editing panels. You can now resize the visualization area if you want -more space for queries/options and vice versa. You can now also change visualization (panel type) from within the new -panel edit mode. No need to add a new panel to try out different visualizations! Check out the -video below to see the new Panel Editor in action. - -
- -
- -
- -### Gauge Panel - -We have created a new separate Gauge panel as we felt having this visualization be a hidden option in the Singlestat panel -was not ideal. When it supports 100% of the Singlestat Gauge features, we plan to add a migration so all -singlestats that use it become Gauge panels instead. This new panel contains a new **Threshold** editor that we will -continue to refine and start using in other panels. - -{{< figure src="/static/img/docs/v60/gauge_panel.png" max-width="600px" caption="Gauge Panel" >}} - -
- -### React Panels and Query Editors - -A major part of all the work that has gone into Grafana v6.0 has been on the migration to React. This investment -is part of the future-proofing of Grafana's code base and ecosystem. Starting in v6.0 **Panels** and **Data -source** plugins can be written in React using our published `@grafana/ui` sdk library. More information on this -will be shared soon. - -{{< figure src="/static/img/docs/v60/react_panels.png" max-width="600px" caption="React Panel" >}} -
- -## Google Stackdriver data source - -Built-in support for [Google Stackdriver](https://cloud.google.com/stackdriver/) is officially released in Grafana 6.0. Beta support was added in Grafana 5.3 and we have added lots of improvements since then. - -To get started read the guide: [Using Google Stackdriver in Grafana]({{< relref "../datasources/google-cloud-monitoring/" >}}). - -## Azure Monitor data source - -One of the goals of the Grafana v6.0 release is to add support for the three major clouds. Amazon CloudWatch has been a core data source for years and Google Stackdriver is also now supported. We developed an external plugin for Azure Monitor last year and for this release the [plugin](https://grafana.com/plugins/grafana-azure-monitor-datasource) is being moved into Grafana to be one of the built-in data sources. For users of the external plugin, Grafana will automatically start using the built-in version. As a core data source, the Azure Monitor data source is able to get alerting support, in the 6.0 release alerting is supported for the Azure Monitor service, with the rest to follow. - -The Azure Monitor data source integrates four Azure services with Grafana - Azure Monitor, Azure Log Analytics, Azure Application Insights and Azure Application Insights Analytics. - -Please read [Using Azure Monitor in Grafana documentation]({{< relref "../datasources/azuremonitor/" >}}) for more detailed information on how to get started and use it. - -## Provisioning support for alert notifiers - -Grafana now has support for provisioning alert notifiers from configuration files, allowing operators to provision notifiers without using the UI or the API. A new field called `uid` has been introduced which is a string identifier that the administrator can set themselves. This is the same kind of identifier used for dashboards since v5.0. This feature makes it possible to use the same notifier configuration in multiple environments and refer to notifiers in dashboard json by a string identifier instead of the numeric id which depends on insert order and how many notifiers exist in the instance. - -## Easier to deploy and improved security - -Grafana 6.0 removes the need to configure and set up additional storage for [user sessions](/tutorials/ha_setup/#user-sessions). This should make it easier to deploy and operate Grafana in a -high availability setup and/or if you're using a stateless user session store like Redis, Memcache, Postgres or MySQL. - -Instead of user sessions, we've implemented a solution based on short-lived tokens that are rotated frequently. This also replaces the old "remember me cookie" -solution, which allowed a user to be logged in between browser sessions and which have been subject to several security holes throughout the years. -For more information about the short-lived token solution and how to configure it, refer to [short lived token](/auth/overview/#login-and-short-lived-tokens). - -> Please note that due to these changes, all users will be required to login upon next visit after upgrade. - -Besides these changes we have also made security improvements regarding Cross-Site Request Forgery (CSRF) and Cross-site Scripting (XSS) vulnerabilities: - -- Cookies are per default using the [SameSite](/administration/configuration/#cookie-samesite) attribute to protect against CSRF attacks -- Script tags in text panels are per default [disabled](/administration/configuration/#disable-sanitize-html) to protect against XSS attacks - -> **Note:** If you're using [Auth Proxy Authentication](/auth/auth-proxy/) you still need to have user sessions set up and configured -> but our goal is to remove this requirement in the near future. - -## Named Colors - -{{< figure src="/static/img/docs/v60/named_colors.png" max-width="400px" class="docs-image--right" caption="Named Colors" >}} - -We have updated the color picker to show named colors and primary colors. We hope this will improve accessibility and -helps making colors more consistent across dashboards. We hope to do more in this color picker in the future, like showing -colors used in the dashboard. - -Named colors also enables Grafana to adapt colors to the current theme. - -
- -## Other features - -- The ElasticSearch data source now supports [bucket script pipeline aggregations](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-pipeline-bucket-script-aggregation.html). This gives the ability to do per-bucket computations like the difference or ratio between two metrics. -- Support for Google Hangouts Chat alert notifications -- New built in template variables for the current time range in `$__from` and `$__to` - -## Upgrading - -See [upgrade notes](/installation/upgrading/#upgrading-to-v6-0). - -## Changelog - -Check out the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file for a complete list of new features, changes, and bug fixes. diff --git a/docs/sources/whatsnew/whats-new-in-v6-1.md b/docs/sources/whatsnew/whats-new-in-v6-1.md deleted file mode 100644 index 425840eb327..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v6-1.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v6-1/ - - /docs/grafana/latest/whatsnew/whats-new-in-v6-1/ -description: Feature and improvement highlights for Grafana v6.1 -keywords: - - grafana - - new - - documentation - - '6.1' - - release notes -title: What's new in Grafana v6.1 -weight: -20 ---- - -# What's new in Grafana v6.1 - -## Highlights - -### Ad hoc Filtering for Prometheus - -{{< figure class="float-right" max-width="30%" src="/static/img/docs/v61/prometheus-ad-hoc.gif" caption="Ad-hoc filters variable for Prometheus" >}} - -The ad hoc filter feature allows you to create new key/value filters on the fly with autocomplete for both key and values. The filter condition is then automatically applied to all queries on the dashboard. This makes it easier to explore your data in a dashboard without changing queries and without having to add new template variables. - -Other timeseries databases with label-based query languages have had this feature for a while. Recently Prometheus added support for fetching label names from their API and thanks to [Mitsuhiro Tanda](https://github.com/mtanda) implementing it in Grafana, the Prometheus data source finally supports ad hoc filtering. - -Support for fetching a list of label names was released in Prometheus v2.6.0 so that is a requirement for this feature to work in Grafana. - -### Permissions: Editors can own dashboards, folders and teams they create - -When the dashboard folders feature and permissions system was released in Grafana 5.0, users with the editor role were not allowed to administrate dashboards, folders or teams. In the 6.1 release, we have added a configuration option that can change the default permissions so that editors are admins for any Dashboard, Folder or Team they create. - -This feature also adds a new Team permission that can be assigned to any user with the editor or viewer role and enables that user to add other users to the Team. - -We believe that this is more in line with the Grafana philosophy, as it will allow teams to be more self-organizing. This option will be made permanent if it gets positive feedback from the community so let us know what you think in the [issue on GitHub](https://github.com/grafana/grafana/issues/15590). - -To turn this feature on add the following [configuration option](/administration/configuration/#editors-can-admin) to your Grafana ini file in the `users` section and then restart the Grafana server: - -```ini -[users] -editors_can_admin = true -``` - -### List and revoke of user auth tokens in the API - -As the first step of a feature to be able to list a user's signed in devices/sessions and to be able log out those devices from the Grafana UI, support has been added to the [API to list and revoke user authentication tokens](/http_api/admin/#auth-tokens-for-user). - -### Minor Features and Fixes - -This release contains a lot of small features and fixes: - -- A new keyboard shortcut `d l` toggles all Graph legends in a dashboard. -- A small bug fix for Elasticsearch - template variables in the alias field now work properly. -- Some new capabilities have been added for data source plugins that will be of interest to plugin authors: - - a new OAuth pass-through option. - - it is now possible to add user details to requests sent to the dataproxy. -- Heatmap and Explore fixes. - -Check out the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file for a complete list of new features, changes, and bug fixes. - -A huge thanks to our community for all the reported issues, bug fixes and feedback. diff --git a/docs/sources/whatsnew/whats-new-in-v6-2.md b/docs/sources/whatsnew/whats-new-in-v6-2.md deleted file mode 100644 index 64e0833155c..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v6-2.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v6-2/ - - /docs/grafana/latest/whatsnew/whats-new-in-v6-2/ -description: Feature and improvement highlights for Grafana v6.2 -keywords: - - grafana - - new - - documentation - - '6.2' - - release notes -title: What's new in Grafana v6.2 -weight: -21 ---- - -# What's new in Grafana v6.2 - -For all details please read the full [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md). - -If you use a password for your data sources please read the [upgrade notes](/installation/upgrading/#upgrading-to-v6-2). - -Check out the [demo dashboard](https://play.grafana.org/d/ZvPm55mWk/new-features-in-v6-2?orgId=1) of some the new features in v6.2. - -## Improved security - -Data sources now store passwords and basic auth passwords in `secureJsonData` encrypted by default. Existing data source with unencrypted passwords will keep working. -Read the [upgrade notes](/installation/upgrading/#upgrading-to-v6-2) on how to migrate existing data sources to use encrypted storage. - -To mitigate the risk of [Clickjacking](https://www.owasp.org/index.php/Clickjacking), embedding Grafana is no longer allowed per default. -Read the [upgrade notes](/installation/upgrading/#upgrading-to-v6-2) for further details of how this may affect you. - -To mitigate the risk of sensitive information being cached in browser after a user has logged out, browser caching is now disabled for full page requests. - -## Provisioning - -- Environment variables support, see [Using environment variables](/administration/provisioning/#using-environment-variables) for more information. -- Reload provisioning configs, see [Admin HTTP API](/http_api/admin/#reload-provisioning-configurations) for more information. -- Do not allow deletion of provisioned dashboards -- When trying to delete or save provisioned dashboard, relative file path to the file is shown in the dialog. - -## Official support for Elasticsearch 7 - -Grafana v6.2 ships with official support for Elasticsearch v7, see [Using Elasticsearch in Grafana]({{< relref "../datasources/elasticsearch/#elasticsearch-version" >}}) for more information. - -## Bar Gauge Panel - -Grafana v6.2 ships with a new exciting panel! This new panel, named Bar Gauge, is very similar to the current -Gauge panel and shares almost all it's options. The main difference is that the Bar Gauge uses both horizontal and -vertical space much better and can be more efficiently stacked both vertically and horizontally. The Bar Gauge also -comes with 3 unique display modes, Basic, Gradient, and Retro LED. Read the -[preview article](https://grafana.com/blog/2019/04/11/sneak-preview-of-new-visualizations-coming-to-grafana/) to learn -more about the design and features of this new panel. - -Retro LED display mode -{{< figure src="/assets/img/blog/bargauge/bar_gauge_retro_led.jpg" max-width="800px" caption="Bar Gauge LED mode" >}} - -Gradient mode -{{< figure src="/assets/img/blog/bargauge/gradient.jpg" max-width="800px" caption="Bar Gauge Gradient mode" >}} - -## Improved table data support - -We have been working on improving table support in our new react panels (Gauge and Bar Gauge) and this is ongoing work -that will eventually come to the new Graph and Singlestat and Table panels we are working on. But you can see it already in -the Gauge and Bar Gauge panels. Without any config, you can visualize any number of columns or choose to visualize each -row as its own gauge. - -## Lazy loading of panels out of view - -This has been one of the most requested features for many years and is now finally here! Lazy loading of panels means -Grafana will not issue any data queries for panels that are not visible. This will greatly reduce the load -on your data source backends when loading dashboards with many panels. - -## Panels without title - -Sometimes your panels do not need a title and having that panel header still take up space makes singlestats and -other panels look strange and have bad vertical centering. In v6.2 Grafana will allow panel content (visualizations) -to use the full panel height in case there is no panel title. - -{{< figure src="/static/img/docs/v62/panels_with_no_title.jpg" max-width="800px" caption="Bar Gauge Gradient mode" >}} - -## Minor Features and Fixes - -This release contains a lot of small features and fixes: - -- Explore - Adds user time zone support, reconnect for failing data sources and a fix that prevents killing Prometheus instances when Histogram metrics are loaded. -- Alerting - Adds support for configuring timeout durations and retries, see [configuration](/administration/configuration/#evaluation-timeout-seconds) for more information. -- Azure Monitor - Adds support for multiple subscriptions per data source. -- Elasticsearch - A small bug fix to properly display percentiles metrics in table panel. -- InfluxDB - Support for POST HTTP verb. -- CloudWatch - Important fix for default alias disappearing in v6.1. -- Search - Works in a scope of dashboard's folder by default when viewing dashboard. - -Check out the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file for a complete list of new features, changes, and bug fixes. - -A huge thanks to our community for all the reported issues, bug fixes and feedback. - -## Upgrading - -Read important [upgrade notes](/installation/upgrading/#upgrading-to-v6-2). diff --git a/docs/sources/whatsnew/whats-new-in-v6-3.md b/docs/sources/whatsnew/whats-new-in-v6-3.md deleted file mode 100644 index 70921206347..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v6-3.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v6-3/ - - /docs/grafana/latest/whatsnew/whats-new-in-v6-3/ -description: Feature and improvement highlights for Grafana v6.3 -keywords: - - grafana - - new - - documentation - - '6.3' - - release notes -title: What's new in Grafana v6.3 -weight: -22 ---- - -# What's new in Grafana v6.3 - -For all details please read the full [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md). - -## Highlights - -- New Explore features - - [Loki Live Streaming]({{< relref "#loki-live-streaming" >}}) - - [Loki Context Queries]({{< relref "#loki-context-queries" >}}) - - [Elasticsearch Logs Support]({{< relref "#elasticsearch-logs-support" >}}) - - [InfluxDB Logs Support]({{< relref "#influxdb-logs-support" >}}) -- [Data links]({{< relref "#data-links" >}}) -- [New Time Picker]({{< relref "#new-time-picker" >}}) -- [Graph Area Gradients]({{< relref "#graph-gradients" >}}) - A new graph display option! -- Grafana Enterprise - - [LDAP Active Sync]({{< relref "#ldap-active-sync" >}}) - LDAP Active Sync - - [SAML Authentication]({{< relref "#saml-authentication" >}}) - SAML Authentication - -## Explore improvements - -This release adds a ton of enhancements to Explore. Both in terms of new general enhancements but also in -new data source specific features. - -### Loki live streaming - -For log queries using the Loki data source you can now stream logs live directly to the Explore UI. - -### Loki context queries - -After finding a log line through the heavy use of query filters it can then be useful to -see the log lines surrounding the line your searched for. The `show context` feature -allows you to view lines before and after the line of interest. - -### Elasticsearch logs support - -This release adds support for searching and visualizing logs stored in Elasticsearch in the Explore mode. With a special -simplified query interface specifically designed for logs search. - -{{< figure src="/static/img/docs/v63/elasticsearch_explore_logs.png" max-width="600px" caption="New Time Picker" >}} - -Please read [Using Elasticsearch in Grafana]({{< relref "../datasources/elasticsearch/#elasticsearch-version" >}}) for more detailed information on how to get started and use it. - -### InfluxDB logs support - -This release adds support for searching and visualizing logs stored in InfluxDB in the Explore mode. With a special -simplified query interface specifically designed for logs search. - -{{< figure src="/static/img/docs/v63/influxdb_explore_logs.png" max-width="600px" caption="New Time Picker" >}} - -Please read [Using InfluxDB in Grafana]({{< relref "../datasources/influxdb/#querying-logs-beta" >}}) for more detailed information on how to get started and use it. - -## Data Links - -We have simplified the UI for defining panel drilldown links (and renamed them to Panel links). We have also added a -new type of link named `Data link`. The reason to have two different types is to make it clear how they are used -and what variables you can use in the link. Panel links are only shown in the top left corner of -the panel and you cannot reference series name or any data field. - -While `Data links` are used by the actual visualization and can reference data fields. - -Example: - -```url -http://my-grafana.com/d/bPCI6VSZz/other-dashboard?var-server=${__series_name} -``` - -You have access to these variables: - -| Name | Description | -| ----------------------- | -------------------------------------------------------------------------- | -| _${\_\_series_name}_ | The name of the time series (or table) | -| _${\_\_value_time}_ | The time of the point your clicking on (in millisecond epoch) | -| _${\_\_url_time_range}_ | Interpolates as the full time range (i.e. from=21312323412&to=21312312312) | -| _${\_\_all_variables}_ | Adds all current variables (and current values) to the URL | - -You can then click on point in the Graph. - -{{< figure src="/static/img/docs/v63/graph_datalink.png" max-width="400px" caption="New Time Picker" >}} - -For now only the Graph panel supports `Data links` but we hope to add these to many visualizations. - -## New Time Picker - -The time picker has been re-designed and with a more basic design that makes accessing quick ranges more easy. - -{{< figure src="/static/img/docs/v63/time_picker.png" max-width="400px" caption="New Time Picker" >}} - -## Graph Gradients - -Want more eye candy in your graphs? Then the fill gradient option might be for you! Works really well for -graphs with only a single series. - -{{< figure src="/static/img/docs/v63/graph_gradient_area.jpeg" max-width="800px" caption="Graph Gradient Area" >}} - -Looks really nice in light theme as well. - -{{< figure src="/static/img/docs/v63/graph_gradients_white.png" max-width="800px" caption="Graph Gradient Area" >}} - -## Grafana Enterprise - -Substantial refactoring and improvements to the external auth systems has gone in to this release making the features -listed below possible as well as laying a foundation for future enhancements. - -### LDAP Active Sync - -This is a new Enterprise feature that enables background syncing of user information, org role and teams memberships. -This syncing is otherwise only done at login time. With this feature you can schedule how often this user synchronization should -occur. - -For example, lets say a user is removed from an LDAP group. In previous versions of Grafana an admin would have to -wait for the user to logout or the session to expire for the Grafana permissions to update, a process that can take days. - -With active sync the user would be automatically removed from the corresponding team in Grafana or even logged out and disabled if no longer -belonging to an LDAP group that gives them access to Grafana. - -[Read more](/auth/enhanced_ldap/#active-ldap-synchronization). - -### SAML Authentication - -Built-in support for SAML is now available in Grafana Enterprise. - -[See docs]({{< relref "../setup-grafana/configure-security/configure-authentication/saml/" >}}) - -### Team Sync for GitHub OAuth - -When setting up OAuth with GitHub it's now possible to sync GitHub teams with Teams in Grafana. - -[See docs]({{< relref "../setup-grafana/configure-security/configure-authentication/github/" >}}) - -### Team Sync for Auth Proxy - -We've added support for enriching the Auth Proxy headers with Teams information, which makes it possible -to use Team Sync with Auth Proxy. - -[See docs](/auth/auth-proxy/#auth-proxy-authentication). diff --git a/docs/sources/whatsnew/whats-new-in-v6-4.md b/docs/sources/whatsnew/whats-new-in-v6-4.md deleted file mode 100644 index acfb61b153c..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v6-4.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v6-4/ - - /docs/grafana/latest/whatsnew/whats-new-in-v6-4/ -description: Feature and improvement highlights for Grafana v6.4 -keywords: - - grafana - - new - - documentation - - '6.4' - - release notes -title: What's new in Grafana v6.4 -weight: -23 ---- - -# What's new in Grafana v6.4 - -For all details please read the full [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md). - -## Highlights - -Grafana 6.4 comes with a lot of new features and enhancements backed with tons of work around the data models and query execution that is going to enable powerful future capabilities. -Some of those new capabilities can already be seen in this release, like sharing query results between panels. - -- [**Explore:** Go back to dashboard (with query changes)]({{< relref "#go-back-to-dashboard-from-explore" >}}) -- [**Explore:** Live tailing improvements]({{< relref "#live-tailing-improvements" >}}) -- **Loki:** Show logs as annotations in dashboard graphs -- **Loki:** Use Loki in dashboard panels -- [**Panels:** New logs panel]({{< relref "#new-logs-panel" >}}) -- [**Panels:** Data links improvements]({{< relref "#data-links-improvements" >}}) -- [**Graph:** Series override to turn constant (point) into a line]({{< relref "#series-override-to turn-constant-into-a-line" >}}) -- [**Dashboard:** Share query results between panels]({{< relref "#share-query-results-between-panels" >}}) -- [**Plugins:** Alpha version of grafana-toolkit]({{< relref "#alpha-version-of-grafana-toolkit" >}}) -- [**Image Rendering:** PhantomJS deprecation]({{< relref "#phantomjs-deprecation" >}}) -- [**Docker:** Alpine based docker image]({{< relref "#alpine-based-docker-image" >}}) -- [**LDAP:** Debug UI]({{< relref "#ldap-debug-ui" >}}) -- [**Enterprise**: Reporting]({{< relref "#reporting" >}}) -- [**Enterprise**: GitLab OAuth Team Sync support]({{< relref "#gitlab-oauth-team-sync-support" >}}) -- [**Enterprise**: Teams and LDAP Improvements]({{< relref "#ldap-teams" >}}) - -### Go back to dashboard from Explore - -To help accelerate workflows that involve regularly switching from Explore to a dashboard and vice-versa, we've added the ability to return to the origin dashboard -after navigating to Explore from the panel's dropdown. - -{{< figure src="/static/img/docs/v60/explore_panel_menu.png" caption="Screenshot of the new Explore Icon" >}} - -After you've navigated to Explore, you should notice a "Back" button in the Explore toolbar. - - - -Simply clicking the button will return you to the origin dashboard, or, if you'd like to bring changes you make in Explore back to the dashboard, simply click -the arrow next to the button to reveal a "Return to panel with changes" menu item. - - - -### Live tailing improvements - -With 6.4 version you can now pause the live tail view to see the last 1000 lines of logs without being interrupted by new logs coming in. You can either pause manually with pause button or the live tailing will automatically pause when you scroll up to see older logs. To resume you just hit the resume button to continue live tailing. - -We also introduced some performance optimizations to allow live tailing of higher throughput log streams and various UI fixes and improvements like more consistent styling and fresh logs highlighting. - - - -### New Logs Panel - -The logs panel shows log lines from datasources that support logs, e.g., Elastic, Influx, and Loki. Typically you would use this panel next to a graph panel to display the log output of a related process. - - - -Limitations: Even though Live tailing can be enabled on logs panels in dashboards, we recommend using Live tailing in Explore. On dashboards, the refresher at the top of the page should be used instead to keep the data of all panels in sync. Note that the logs panel is still beta and we're looking to get feedback. - -## Data Links improvements - -With Grafana 6.3 we introduced a new way of creating [Data Links](https://grafana.com/blog/2019/08/27/new-in-grafana-6.3-easy-to-use-data-links/). -Grafana 6.4 improves Data Links and adds them to the Gauge and Bar Gauge and panels. - -With Data Links you can define dynamic links to other dashboards and systems. The link can now reference template variables and query results like series name and labels, field name, value and time. - -For more information about Data Links, refer to [data link](https://grafana.com/docs/features/panels/graph/#data-link) - -## Series override to turn constant into a line - -Some graph query results are made up only of one datapoint per series but can be shown in the graph panel with the help of [series overrides](/features/panels/graph/#series-overrides). -To show a horizontal line through the Y-value of the datapoint across the whole graph, add a series override and select `Transform > constant`. - - - -## Share query results between panels - -Grafana 6.4 continues the work started in 6.3 of creating a data model and query execution lifecycle that can support robust analytics and streaming. These changes are mostly structural and lay the foundation for powerful features in future releases. - -The first new feature all these changes have enabled is the ability to share query results between panels. So for example if you have an expensive query you can visualize the same results in a graph, table and singlestat panel. To reuse another panel’s query result select the data source named `-- Dashboard --` and then select the panel. - -To make the sharing of query results even more powerful we are introducing a transformation step as well that allows you to select specific parts of the query result and transform it. This new transformation feature is in [alpha](https://grafana.com/docs/administration/configuration/#enable-alpha) state and has to be enabled in the config file. - -DataFrame, our primary data model, has now a [columnar](https://en.wikipedia.org/wiki/Column-oriented_DBMS) layout. This -will support easier frontend processing. The DataSource query interface has been updated to better support streaming. -The result can now either return a `Promise` or `Observable`. Be on the lookout for more on live data -streaming in the future! - -## Alpha version of grafana-toolkit - -[grafana-toolkit](https://www.npmjs.com/package/@grafana/toolkit/v/6.4.0-beta.1) is our attempt to simplify the life of plugin developers. It’s a CLI that helps them focus on the core value of their plugin rather than the ceremony around setting up the environment, configs, tests and builds. It’s available as an NPM package under `next` tag. - -You can read more about the grafana-toolkit [in the Readme](https://github.com/grafana/grafana/blob/master/packages/grafana-toolkit/README.md) and play with it by trying out our [react panel](https://github.com/grafana/simple-react-panel) or [angular panel](https://github.com/grafana/simple-angular-panel) templates. - -## PhantomJS deprecation - -[PhantomJS](https://phantomjs.org/), which is used for rendering images of dashboards and panels, have been deprecated and will be removed in a future Grafana release. A deprecation warning will from now on be logged when Grafana starts up if PhantomJS is in use. - -Please consider migrating from PhantomJS to the [Grafana Image Renderer plugin](https://grafana.com/grafana/plugins/grafana-image-renderer). - -## Alpine-based Docker image - -Grafana’s Docker image is now based on Alpine 3.10 and should from now on report zero vulnerabilities when scanning the image for security vulnerabilities. - -## LDAP Debug UI - -After listening to customer feedback, we have been working at improving the experience to set up authentication and synchronization with LDAP. We're happy to present the new LDAP Debug View. - -You'll be able to see how a user authenticating with LDAP would be mapped and whether your LDAP integration is working correctly. Furthermore, it provides a simpler method to test your integration with LDAP server(s) and have a clear view of how attributes are mapped between both systems. - -The feature is currently limited to Grafana Server Admins. - -For more information on how to use this new feature, follow the [guide]({{< relref "../setup-grafana/configure-security/configure-authentication/ldap/#ldap-debug-view" >}}). - -## Grafana Enterprise - -### Reporting - -A common request from Enterprise users have been to be able to set up reporting for Grafana, and now it’s here. A report is simply a PDF of a Grafana dashboard, outside of just generating a PDF you can set up a schedule so that you can get the report emailed to yourself (or whoever is interested) whenever it suits you. - -This feature is currently limited to Organization Admins. - -{{< figure src="/static/img/docs/v64/reports.jpeg" max-width="500px" caption="Reporting" >}} - -### GitLab OAuth Team Sync support - -GitLab OAuth gets support for Team Sync, making it possible to synchronize your GitLab Groups with Teams in Grafana. - -[Read more about Team Sync](https://grafana.com/docs/auth/team-sync/). - -## Upgrading - -See [upgrade notes](/installation/upgrading/#upgrading-to-v6-4). - -## Changelog - -Check out the [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) file for a complete list of new features, changes, and bug fixes. diff --git a/docs/sources/whatsnew/whats-new-in-v6-5.md b/docs/sources/whatsnew/whats-new-in-v6-5.md deleted file mode 100644 index 9405e60f4b1..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v6-5.md +++ /dev/null @@ -1,216 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v6-5/ - - /docs/grafana/latest/whatsnew/whats-new-in-v6-5/ -description: Feature and improvement highlights for Grafana v6.5 -keywords: - - grafana - - new - - documentation - - '6.5' - - release notes -title: What's new in Grafana v6.5 -weight: -24 ---- - -# What's new in Grafana v6.5 - -For all details, read the full [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md). - -## Highlights - -Grafana 6.5 comes with a lot of new features and enhancements: - -- [**Docker:** Ubuntu-based images and more]({{< relref "#ubuntu-based-docker-images" >}}) -- [**CloudWatch:** Major rewrite and lots of enhancements]({{< relref "#cloudwatch-data-source-improvements" >}}) -- [**Templating:** Dynamic typeahead queries using $__searchFilter]({{< relref "#dynamic-typeahead-support-in-query-variables" >}}) -- [**Graphite:** Support for additional Metrictank functionality]({{< relref "#graphite-support-for-additional-metrictank-functionality" >}}) -- [**Explore:** New log row details view]({{< relref "#explore-logs-log-row-details" >}}) -- [**Explore:** Turn parts of log message into a link using derived fields]({{< relref "#loki-explore-derived-fields" >}}) -- [**Explore:** Time-sync of split views]({{< relref "#time-sync-of-split-views-in-explore" >}}) -- [**Explore**: Hover/tooltip support in graphs]({{< relref "#explore-metrics-graph-hover-tooltip" >}}) -- [**Azure Monitor**: Alerting support for Azure Application Insights]({{< relref "#alerting-support-for-azure-application-insights" >}}) -- [**Provisioning**: Allow saving of provisioned dashboards from UI]({{< relref "#allow-saving-of-provisioned-dashboards-from-ui" >}}) -- [**Auth Proxy:** Mix auth proxy with Grafana login token and session cookie]({{< relref "#mix-auth-proxy-with-grafana-login-token-and-session-cookie" >}}) -- [**OAuth:** Generic OAuth now supports role mapping]({{< relref "#generic-oauth-role-mapping" >}}) -- [**Image Rendering:** Quick update since Grafana 6.4]({{< relref "#image-renderer-plugin" >}}) - -### Ubuntu-based Docker images - -In Grafana [v6.4]({{< relref "whats-new-in-v6-4/#alpine-based-docker-image" >}}), we switched the Grafana Docker image from Ubuntu to Alpine. This change provides a more secure and lightweight Docker image. - -This change has received both negative and positive feedback as well as some bug reports. We learned that switching to an Alpine-based Docker image was a big breaking change for a lot of users. We should have more clearly highlighted this in blog post, release notes, changelog, and the [Docker Hub readme](https://hub.docker.com/r/grafana/grafana). - -We also broke the Docker images for ARM, but this is fixed in Grafana v6.5. - -Grafana Docker images should be as secure as possible by default and that’s why the Alpine-based Docker images will continue to be the Grafana default (`grafana/grafana:`). With that said, it’s good to give users options, and that’s why starting from Grafana v6.5, Ubuntu-based Docker images are also (`grafana/grafana:-ubuntu`) available. - -Read more about [Installing using Docker]({{< relref "../setup-grafana/installation/docker/" >}}). - -### CloudWatch data source improvements - -In this release, several feature improvements and additions were made in the CloudWatch data source. This work has been done in collaboration with the Amazon CloudWatch team. - -#### GetMetricData API - -For Grafana version 6.5 or higher, all API requests to GetMetricStatistics have been replaced with calls to GetMetricData, following Amazon’s [best practice to use the GetMetricData API](https://aws.amazon.com/premiumsupport/knowledge-center/cloudwatch-getmetricdata-api) instead of GetMetricStatistics, because data can be retrieved faster at scale with GetMetricData. This change provides better support for CloudWatch metric math and enables the use of automatic search expressions. - -While GetMetricStatistics qualified for the CloudWatch API free tier, this is not the case for GetMetricData calls. For more information, please refer to the [CloudWatch pricing page](https://aws.amazon.com/cloudwatch/pricing/). - -#### Dynamic queries using dimension wildcards - -In Grafana 6.5 or higher, you can monitor a dynamic list of metrics by using the asterisk (\*) wildcard for one or more dimension values. - -{{< figure src="/static/img/docs/v65/cloudwatch-dimension-wildcard.png" max-width="800px" class="docs-image--right" caption="CloudWatch dimension wildcard" >}} - -The example queries all metrics in the namespace `AWS/EC2` with a metric name of `CPUUtilization` and _any_ value for the `InstanceId` dimension. This can help you monitor metrics for AWS resources, like EC2 instances or containers. For example, when new instances get created as part of an auto scaling event, they automatically appear in the graph without you having to track new instance IDs. You can click `Show Query Preview` to see the search expression that is automatically built to support wildcards. To learn more about search expressions, visit the [CloudWatch documentation](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/search-expression-syntax.html). - -By default, the search expression is defined in such a way that the queried metrics must match the defined dimension names exactly. This means that in the example it only returns metrics with exactly one dimension with name ‘InstanceId’. - -You can untoggle `Match Exact` to include metrics that have other dimensions defined. Turning off `Match Exact` also creates a search expression even if you don’t use wildcards. We simply search for any metric that match at least the namespace, metric name, and all defined dimensions. - -#### Deep linking from Grafana panels to the CloudWatch console - -{{< figure src="/static/img/docs/v65/cloudwatch-deep-linking.png" max-width="500px" class="docs-image--right" caption="CloudWatch deep linking" >}} - -Left-clicking a time series in the panel displays a context menu with a link to `View in CloudWatch console`. Clicking that link opens the CloudWatch console and displays all the metrics for that query. If you are not currently logged in to the CloudWatch console, then the link opens the login page. The link is valid for any account, but it only displays the right metrics if you are logged in to the account that corresponds to the selected data source in Grafana. - -This feature is not available for metrics based on math expressions. - -#### Improved feedback when throttling occurs - -If the [limit of the GetMetricData API](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch_limits.html) is reached, either the transactions per second limit or the data points per second limit, then a throttling error will be returned by the CloudWatch API. Throttling limits are defined per account and region, so the alert modal indicates which data source got throttled in which region. A link to request a limit increase for the affected region is provided, but you will have to log in to the correct account. For example, for us-east-1, a limit increase can be requested on [AWS console](https://console.aws.amazon.com/servicequotas/home?region=us-east-1#!/services/monitoring/quotas/L-5E141212). - -#### Multi-value template variables now use search expressions - -When defining dimension values based on multi-valued template variables, we now use search expressions to query for the matching metrics. This enables the use of multiple template variables in one query and also allows you to use template variables for queries that have the `Match Exact` option disabled. - -Search expressions are currently limited to 1024 characters, so your query may fail if you have a long list of values. We recommend using the asterisk (\*) wildcard instead of the `All` option if you want to query all metrics that have any value for a certain dimension name. - -The use of multi-valued template variables is only supported for dimension values. Using multi-valued template variables for `Region`, `Namespace`, or `Metric Name` is not supported. - -#### Curated Dashboards - -The updated CloudWatch data source is shipped with pre-configured dashboards for five of the most popular AWS services: - -- Amazon Elastic Compute Cloud `Amazon EC2` -- Amazon Elastic Block Store `Amazon EBS` -- AWS Lambda `AWS Lambda` -- Amazon CloudWatch Logs `Amazon CloudWatch Logs` -- Amazon Relational Database Service `Amazon RDS` - -To import the pre-configured dashboards, go to the configuration page of your CloudWatch data source and click on the `Dashboards` tab. Click `Import` for the dashboard you would like to use. To customize the dashboard, we recommend to save the dashboard under a different name, because otherwise the dashboard will be overwritten when a new version of the dashboard is released. - -{{< figure src="/static/img/docs/v65/cloudwatch-dashboard-import.png" max-width="600px" caption="CloudWatch dashboard import" >}} - -### Dynamic typeahead support in query variables - -If you have a query variable that has many thousands of values it can be quite slow to search for a specific value in the dropdown. This is due to the fact that all that search filtering is happening in the browser. - -Using `__searchFilter` in the template variable query field you can filter the query results based on what the user types in the variable dropdown input. When nothing has been entered by the user the default value for `__searchFilter` is `*` , `.*` or `%` depending on data source and formatting option. - -The example below shows how to use `__searchFilter` as part of the query field to enable searching for `server` while the user types in the dropdown select box. - -Query - -```bash -apps.$app.servers.$__searchFilter -``` - -TagValues - -```bash -tag_values(server, server=~${__searchFilter:regex}) -``` - -This feature is currently only supported by [Graphite]({{< relref "../datasources/graphite/#using-searchfilter-to-filter-results-in-query-variable" >}}), [MySQL]({{< relref "../datasources/mysql/#using-searchfilter-to-filter-results-in-query-variable" >}}) and [Postgres]({{< relref "../datasources/postgres/#using-searchfilter-to-filter-results-in-query-variable" >}}) data sources. - -### Graphite: Support for additional Metrictank functionality - -The Graphite data source now has an option to enable extra functionality when using [Metrictank](https://grafana.com/oss/metrictank/) as a Graphite datastore. -In the Datasource configuration for Graphite, you can change the type to Metrictank. -Metrictank returns 2 kinds of additional metadata along its responses: - -- **Performance information:** Time spent querying index, fetching data, running processing functions, the number of series and points fetched, cache hits/misses, etc. This can be useful for optimizing queries or tuning the chunk cache. -- **Lineage information about the returned series:** Which archive was fetched from (raw or rollup), which (if any) runtime consolidation was applied (using which processing function), etc. This is very useful information for anyone trying to understand how their data was generated and why it may not look as expected. - -To see the metadata response from Metrictank you can inspect the response using the Query Inspector found in the panel queries tab. -Grafana 6.5 includes a new `Panel Inspector` in alpha/preview where you also can see the metadata response from Metrictank. -You can try it out by enabling a feature flag in the Grafana configuration file: - -```bash -[feature_toggles] -enable = inspect -``` - -{{< figure src="/static/img/docs/v65/panel-inspector.png" max-width="400px" caption="New Panel Inspector modal" >}} - -In Grafana 6.6, this will have a more user friendly display. In the future, additional Metrictank functionality will become available when the Graphite datasource option is set to the `Metrictank` type. - -### Explore/Metrics: Graph hover/tooltip - -We finally got around to implementing the series hover that shows values of the timeseries you hover over. This has been a requested feature ever since Explore was released. The graph component has been rewritten from scratch, making it more composable for future interactions with the graph data. - -{{< figure src="/static/img/docs/v65/explore_tooltip.png" max-width="500px" caption="Explore graph tooltip/hover" >}} - -### Explore/Logs: Log row details - -We have massively simplified the way we display both log row labels/fields as well as parsed fields by putting them into an extendable area in each row. - -So far labels had been squashed into their own column, making long label values difficult to read or interact with. Similarly, the parsed fields (available for logfmt and JSON structured logs) were too fiddly for mouse interaction. To solve this we took both and put them into a collapsed area below each row for more robust interaction. We have also added the ability to filter out labels, i.e., turn them into a negative filter on click (in addition to a positive filter). - -{{< figure src="/static/img/docs/v65/explore_log_details.gif" caption="Explore Log row details" >}} - -### Loki/Explore: Derived fields - -Derived fields allow any part of a log message to be turned into a link. Leaning on the concept of data links for graphs, we've extended the log result viewer in Explore to turn certain parsed fields into a link, based on a pattern to match. - -This allows you to turn an occurrence of e.g., `traceId=624f706351956b81` in your log line, into a link to your distributed tracing system to view that trace. The configuration for the patterns to match can be found in the datasource settings. - -This release starts with support for Loki, but we will bring this concept to other data sources soon. - -### Time-sync of split views in Explore - -In the Explore split view, you can now link the two timepickers so that if you change one, the other gets changed as well. This helps with keeping start and end times of the split view queries in sync and will ensure that you're looking at the same time interval in both split panes. - -{{< figure src="/static/img/docs/v65/explore_time_sync.gif" caption="Time-sync of split views in Explore" >}} - -### Alerting support for Azure Application Insights - -The [Azure Monitor]({{< relref "../datasources/azuremonitor/" >}}) data source supports multiple services in the Azure cloud. Before Grafana v6.5, only the Azure Monitor service had support for [Grafana Alerting]({{< relref "../alerting/" >}}). In Grafana 6.5, alerting support has been implemented for the [Application Insights service]({{< relref "../datasources/azuremonitor/#querying-the-application-insights-service" >}}). - -### Allow saving of provisioned dashboards from UI - -Historically it has been possible to make changes to a provisioned dashboard in the Grafana UI. However, it hasn't been possible to save the changes without manual intervention. In Grafana 6.5 we introduce a new dashboard provisioning setting named `allowUiUpdates`. If `allowUiUpdates` is set to `true` and you make changes to a provisioned dashboard, you can save the dashboard and the changes will be persisted to the Grafana database. - -Read more about this new feature in [Provisioning Grafana]({{< relref "../administration/provisioning/#making-changes-to-a-provisioned-dashboard" >}}). - -### Mix auth proxy with Grafana login token and session cookie - -With the new setting, `enable_login_token`, set to true Grafana will, after successful auth proxy header validation, assign the user a login token and cookie. You only have to configure your auth proxy to provide headers for the /login route. Requests via other routes will be authenticated using the cookie. - -Read more about this new feature in [Auth Proxy Authentication]({{< relref "../setup-grafana/configure-security/configure-authentication/auth-proxy/#login-token-and-session-cookie" >}}) - -### Generic OAuth role mapping - -Grafana 6.5 makes it possible to configure Generic OAuth to map a certain response from OAuth provider to a certain Grafana organization role, similar to the existing [LDAP Group Mappings]({{< relref "../setup-grafana/configure-security/configure-authentication/ldap/#group-mappings" >}}) feature. The new setting is named `role_attribute_path` and expects a [JMESPath](http://jmespath.org/) expression. - -Read more about this new feature in [Generic OAuth Authentication]({{< relref "../setup-grafana/configure-security/configure-authentication/generic-oauth/" >}}) and make sure to check out the [JMESPath examples]({{< relref "../setup-grafana/configure-security/configure-authentication/generic-oauth/#jmespath-examples" >}}). - -### Image renderer plugin - -Since we announced the deprecation of PhantomJS and the new [Image Renderer Plugin](https://grafana.com/grafana/plugins/grafana-image-renderer) in Grafana [6.4]({{< relref "whats-new-in-v6-4/#phantomjs-deprecation" >}}), we’ve received bug reports and valuable feedback. - -In Grafana 6.5 we’ve updated documentation to make it easier to understand how to install and troubleshoot possible problems. Read more about [Image Rendering]({{< relref "../setup-grafana/image-rendering/" >}}). - -Please try the [Image Renderer plugin](https://grafana.com/grafana/plugins/grafana-image-renderer) and let us know what you think. - -## Upgrading - -See [upgrade notes]({{< relref "../setup-grafana/upgrade-grafana/#upgrading-to-v6-5" >}}). - -## Changelog - -Check out [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) for a complete list of new features, changes, and bug fixes. diff --git a/docs/sources/whatsnew/whats-new-in-v6-6.md b/docs/sources/whatsnew/whats-new-in-v6-6.md deleted file mode 100644 index 30a4d2fe85b..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v6-6.md +++ /dev/null @@ -1,225 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v6-6/ - - /docs/grafana/latest/whatsnew/whats-new-in-v6-6/ -description: Feature and improvement highlights for Grafana v6.6 -keywords: - - grafana - - new - - documentation - - '6.6' - - release notes -title: What's new in Grafana v6.6 -weight: -25 ---- - -# What's new in Grafana v6.6 - -For all details, read the full [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md). - -## Highlights - -Grafana 6.6 comes with a lot of new features and enhancements: - -- [**Panels:** New stat panel]({{< relref "#new-stat-panel" >}}) -- [**Panels:** Auto min/max for Bar Gauge/Gauge/Stat]({{< relref "#auto-min-max" >}}) -- [**Panels:** News panel]({{< relref "#news-panel" >}}) -- [**Panels:** Custom data units]({{< relref "#custom-data-units" >}}) -- [**Panels:** Bar Gauge unfilled option]({{< relref "#bar-gauge-unfilled-option" >}}) -- [**TimePicker:** New design & features]({{< relref "#new-time-picker" >}}) -- [**Alerting enhancements**]({{< relref "#alerting-enhancements" >}}) -- [**Explore:** Added log message line wrapping options for logs]({{< relref "#explore-logs-panel-log-message-line-wrapping-options" >}}) -- [**Explore:** Column with unique log labels ]({{< relref "#explore-logs-panel-column-with-unique-log-labels" >}}) -- [**Explore:** Context tooltip]({{< relref "#explore-context-tooltip" >}}) -- **Explore:** Added ability to specify step with Prometheus queries -- **Graphite:** Added Metrictank dashboard to Graphite datasource -- **Loki:** Support for template variable queries -- **Postgres/MySQL/MSSQL:** Added support for region annotations -- [**Security:** Added disabled option for cookie sameSite attribute]({{< relref "#cookie-management-modifications" >}}) -- **TablePanel, GraphPanel:** Exclude hidden columns from CSV -- [**Enterprise:** White labeling]({{< relref "#enterprise-white-labeling" >}}) -- [**Enterprise:** APT and YUM repositories]({{< relref "#enterprise-apt-and-yum-repositories" >}}) -- [**Stackdriver:** Meta labels]({{< relref "#stackdriver-meta-labels" >}}) -- [**CloudWatch:** Calculate period based on time range]({{< relref "#cloudwatch-calculate-period-based-on-time-range" >}}) -- [**CloudWatch:** Display partial result in graph when max DP/call limit is reached]({{< relref "#cloudwatch-display-partial-result-in-graph-when-max-data-points-per-call-limit-is-reached" >}}) - -## New stat panel - -{{< figure src="/static/img/docs/v66/stat_panel_dark2.png" max-width="1024px" caption="Stat panel" >}} - -This release adds a new panel named `Stat`. This panel is designed to replace the current `Singlestat` as the primary way to show big single number panels along with a sparkline. This panel is of course building on our new panel infrastructure and option design. So, you can use the new threshold UI and data links. It also supports the same repeating feature as the Gauge and Bar Gauge panels, meaning it will repeat a separate visualization for every series or row -in the query result. - -Key features: - -- Automatic font size handling -- Automatic layout handling based on panel size -- Colors based on thresholds that adapt to light or dark theme -- Data links support -- Repeats horizontally or vertically for every series, row, or column - -Here is how it looks in light theme: - -{{< figure src="/static/img/docs/v66/stat_panel_light.png" max-width="1024px" caption="Stat panel" >}} - -## Auto min-max - -For the panels Gauge, Bar Gauge, and Stat, you can now leave the min and max settings empty. Grafana will, in that case, calculate the min and max based on all the data. - -## News panel - -This panel shows RSS feeds as news items in the default home dashboard for v6.6. Add it to your custom home dashboards to keep up-to-date with Grafana news, or switch the default RSS feed to one of your choice. - -{{< figure src="/static/img/docs/v66/news_panel.png" max-width="600px" caption="News panel" >}} - -## Custom data units - -A top feature request for years is now finally here. All panels now support custom units. Type any text in the unit picker and select the `Custom: ` option. By default, the text will be used as a suffix unit. If you want a custom prefix, then type `prefix: ` to make the custom unit appear before the value. If you want a custom SI unit (with auto SI suffixes) specify `si:Ups`. A value like 1000 will be rendered as `1 kUps`. - -{{< figure src="/static/img/docs/v66/custom_unit_burger1.png" max-width="600px" caption="Custom unit" >}} - -You can also paste a native emoji in the unit picker and pick it as a custom unit: - -{{< figure src="/static/img/docs/v66/custom_unit_burger2.png" max-width="600px" caption="Custom unit emoji" >}} - -## Bar Gauge unfilled option - -The Bar Gauge visualization has a new display option: `Unfilled`. This new option is enabled by default, so it will change how this visualization is displayed on old dashboards. If you prefer the old default -- in which an unfilled area is not shown, and the value follows directly after -- you have to update the visualization settings. -{{< figure src="/static/img/docs/v66/bar_gauge_unfilled.png" max-width="900px" caption="Bar gauge unfilled" >}} - -## New time picker - -The time picker has gotten a major design update. Key changes: - -- Quickly access the absolute from and to input fields without an extra click. -- Calendar automatically shows when from or to inputs have focus. -- A single calendar view can be used to select and show the from and to date. -- You can now select recent absolute ranges. - -{{< figure src="/static/img/docs/v66/time_picker_update.png" max-width="700px" caption="New time picker" >}} - -## Alerting enhancements - -- We have introduced a new configuration for enforcing a minimal interval between evaluations to reduce load on the backend. -- The email notifier can now optionally send a single email to all recipients. -- OpsGenie, PagerDuty, Threema, and Google Chat notifiers have been updated to send additional information. - -## Cookie management modifications - -In order to align with a [change in Chrome 80](https://www.chromestatus.com/feature/5088147346030592), a breaking change has been introduced to Grafana's [`cookie_samesite` setting]({{< relref "../setup-grafana/configure-grafana/#cookie-samesite" >}}). Grafana now properly renders cookies with the `SameSite=None` attribute when this setting is `none`. The previous behavior of `none` was to omit the `SameSite` attribute from cookies. Grafana will use the previous behavior when `cookie_samesite` is set to `disabled`. - -Read more about this in the [upgrade notes]({{< relref "../setup-grafana/upgrade-grafana/#important-changes-regarding-samesite-cookie-attribute" >}}). - -## Explore/Logs Panel: Log message line wrapping options - -We introduced the wrap-lines option for logs because as for some of our users feel it's more efficient to see one line per log message. The wrapped-line option is set as a default; the unwrapped setting results in horizontal scrolling. - -{{< figure src="/static/img/docs/v66/explore_wrap_lines.gif" max-width="600px" caption="Log message line wrapping" >}} - -## Explore/Logs Panel: Column with unique log labels - -After feedback from our community, we have decided to reintroduce a labels column. However, for better readability and usefulness, we have transformed it into a Unique labels column which includes only non-common labels. All common labels are displayed above. - -{{< figure src="/static/img/docs/v66/explore_labels_column.png" max-width="600px" caption="Unique log labels column" >}} - -## Explore: Context tooltip - -Isolating a series from a big set of lines in a graph is important for drill-downs. That's why we have implemented the context tooltip in Explore, which allows you to copy data and labels from it to further refine the query. - -{{< figure src="/static/img/docs/v66/explore_context_tooltip.png" max-width="600px" caption="Explore context tooltip" >}} - -## Enterprise: White labeling - -This release adds new white labeling options to the grafana.ini file (can also be set via ENV variables). - -```bash -[white_labeling] -# Set to complete URL to override login logo -login_logo = https://my.logo.url/images/logo.png - -# Set to complete css background expression to override login background -login_background = url(http://www.bhmpics.com/wallpapers/starfield-1920x1080.jpg) - -# Set to complete URL to override menu logo -menu_logo = https://my.logo.url/images/logo_icon.png - -# Set to complete URL to override fav icon (icon shown in browser tab) -fav_icon = https://my.logo.url/images/logo_icon_32px.png - -# Set to complete URL to override apple/ios icon -apple_touch_icon = https://my.logo.url/images/logo_icon_32px.png - -# Below is an example for how to replace the default footer & help links with 2 custom links -footer_links = support guides -footer_links_support_text = Support -footer_links_support_url = http://your.support.site -footer_links_guides_text = Guides -footer_links_guides_url = http://your.guides.site -``` - -Customize the login page, side menu bar, and footer links. - -{{< figure src="/static/img/docs/v66/whitelabeling_1.png" max-width="700px" caption="White labeling example" >}} - -## Enterprise APT and YUM repositories - -Now you can install the enterprise edition from the APT and YUM repository. The following table shows the APT repository for each Grafana version (for instructions read the [installation notes]({{< relref "../setup-grafana/installation/debian/#install-from-apt-repository" >}})) : - -| Grafana Version | Package | Repository | -| ------------------------- | ------------------ | --------------------------------------------------------- | -| Grafana OSS | grafana | `https://packages.grafana.com/oss/deb stable main` | -| Grafana OSS (Beta) | grafana | `https://packages.grafana.com/oss/deb beta main` | -| Grafana Enterprise | grafana-enterprise | `https://packages.grafana.com/enterprise/deb stable main` | -| Grafana Enterprise (Beta) | grafana-enterprise | `https://packages.grafana.com/enterprise/deb beta main` | - -The following table shows the YUM repositories for each Grafana version (for instructions read the [installation notes]({{< relref "../setup-grafana/installation/rpm/#install-from-yum-repository" >}})) : - -| Grafana Version | Package | Repository | -| ------------------------- | ------------------ | -------------------------------------------------- | -| Grafana OSS | grafana | `https://packages.grafana.com/oss/rpm` | -| Grafana OSS (Beta) | grafana | `https://packages.grafana.com/oss/rpm-beta` | -| Grafana Enterprise | grafana-enterprise | `https://packages.grafana.com/enterprise/rpm` | -| Grafana Enterprise (Beta) | grafana-enterprise | `https://packages.grafana.com/enterprise/rpm-beta` | - -We recommend all users to install the Enterprise Edition of Grafana, which can be seamlessly upgraded with a Grafana Enterprise [subscription](https://grafana.com/products/enterprise/?utm_source=grafana-install-page). - -## Stackdriver: Meta labels - -From now on it will be possible to utilize meta data label in "group bys", filters and in the alias field. Unfortunately, there's no API to retrieve all the labels, but the group by field dropdown comes with a pre-defined list of common system labels. User labels cannot be pre-defined, but it's possible to enter them manually in the group by field. If a meta data label, user label or system label, is included in the group by segment, it will be possible to create filters based on it and to expand its value on the alias field. - -{{< figure src="/static/img/docs/v66/metadatalabels.gif" max-width="800px" caption="Stackdriver meta labels" >}} - -## CloudWatch: Calculate period based on time range - -When the period field was left blank in Grafana 6.5, it would default to 60 seconds. In case users issued queries with a large time span, there was a high risk that they would reach the 100,800 data points per request limit in the Get Metric Data (GMD) API. When the period field is left blank in Grafana 6.6, the period will be calculated automatically based on the time range. The formula that is used is `time range in seconds / 2000`, and then we snap to next higher value in an array of pre-defined periods `[60, 300, 900, 3600, 21600, 86400]`. This will reduce the risk for receiving a `Too many datapoints requested` error in the panel. - -## CloudWatch: Display partial result in graph when max data points per call limit is reached - -In case all queries in a GMD call are metric stat (not using math expressions), Grafana will paginate the response until all data points are received. But pagination is not supported in case a math expression is being used, so in that case it's not possible to receive more than 100,800 data points. Previously when that limit was reached, we only displayed an error message. In Grafana 6.6, we also display the 100,800 data points that were received in the graph. - -## Upgrading - -See [upgrade notes]({{< relref "../setup-grafana/upgrade-grafana/#upgrading-to-v6-6" >}}). - -## Changelog - -Check out [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) for a complete list of new features, changes, and bug fixes. - -## Notice about upcoming changes in backendSrv for plugin authors - -In our mission to migrate away from AngularJS to React we have removed all AngularJS dependencies in the core data retrieval service `backendSrv`. This change is already in master and will be introduced in the next `major` Grafana release. - -Removing the AngularJS dependencies in `backendSrv` has the unfortunate side effect of AngularJS digest no longer being triggered for any request made with `backendSrv`. Because of this, external plugins using `backendSrv` directly may suffer from strange behaviour in the UI. - -To remedy this issue as a plugin author you need to trigger the digest after a direct call to `backendSrv`. - -Example: - -```js -backendSrv.get(‘http://your.url/api’).then(result => { - this.result = result; - this.$scope.$digest(); -}); -``` diff --git a/docs/sources/whatsnew/whats-new-in-v6-7.md b/docs/sources/whatsnew/whats-new-in-v6-7.md deleted file mode 100644 index b77e9f418f7..00000000000 --- a/docs/sources/whatsnew/whats-new-in-v6-7.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -_build: - list: false -aliases: - - /docs/grafana/latest/guides/whats-new-in-v6-7/ - - /docs/grafana/latest/whatsnew/whats-new-in-v6-7/ -description: Feature and improvement highlights for Grafana v6.7 -keywords: - - grafana - - new - - documentation - - '6.7' - - release notes -title: What's New in Grafana v6.7 -weight: -26 ---- - -# What's new in Grafana v6.7 - -This topic includes the release notes for the Grafana v6.7. For all details, read the full [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md). - -Grafana 6.7 comes with a lot of new features and enhancements: - -- [**Dashboard:** Enforce minimum refresh interval]({{< relref "#enforce-minimum-dashboard-refresh-interval" >}}) -- **Data source:** Google Sheets data source -- [**Explore:** Query history]({{< relref "#query-history" >}}) -- [**Authorization:** Azure OAuth]({{< relref "#azure-oauth" >}}) -- [**Stackdriver:** Project Selector]({{< relref "#stackdriver-project-selector" >}}) -- [**Enterprise:** White Labeling for application title]({{< relref "#white-labeling-for-application-title" >}}) -- [**Enterprise:** Reporting configuration for timeout and concurrency]({{< relref "#reporting-configuration-for-timeout-and-concurrency" >}}) -- [**Enterprise:** Export dashboard as pdf]({{< relref "#export-dashboard-as-pdf" >}}) -- [**Enterprise:** Report landscape mode]({{< relref "#report-landscape-mode" >}}) -- [**Enterprise:** Azure OAuth Team Sync support]({{< relref "#azure-oauth-team-sync-support" >}}) - -## General features - -General features are included in all Grafana editions. - -### Query history - -> BETA: Query history is a beta feature. It is local to your browser and is not shared with others. - -Query history is a new feature that lets you view and interact with the queries that you have previously run in Explore. You can add queries to the Explore query editor, write comments, create and share URL links, star your favorite queries, and much more. Starred queries are displayed in Starred tab, so it is easier to reuse queries that you run often without typing them from scratch. - -Learn more about query history in [Explore]({{< relref "../explore/" >}}). - -{{< figure src="/static/img/docs/v67/rich-history.gif" max-width="1024px" caption="Query history" >}} - -### Azure OAuth - -Grafana v6.7 comes with a new OAuth integration for Microsoft Azure Active Directory. You can now assign users and groups to Grafana roles from the Azure Portal. Learn how to enable and configure it in [Azure AD OAuth2 authentication]({{< relref "../setup-grafana/configure-security/configure-authentication/azuread/" >}}). - -### Enforce minimum dashboard refresh interval - -Allowing a low dashboard refresh interval can cause severe load on data sources and Grafana. Grafana v6.7 allows you to restrict the dashboard refresh interval so it cannot be set lower than a given interval. This provides a way for administrators to control dashboard refresh behavior on a global level. - -Refer to min_refresh_interval in [Configuration]({{< relref "../setup-grafana/configure-grafana/#min-refresh-interval" >}}) for more information and how to enable this feature. - -### Stackdriver project selector - -A Stackdriver data source in Grafana is configured for one service account only. That service account is always associated with a default project in Google Cloud Platform (GCP). Depending on your setup in GCP, the service account might be granted access to more projects than just the default project. - -In Grafana 6.7, the query editor has been enhanced with a project selector that makes it possible to query different projects without changing datasource. Many thanks [Eraac](https://github.com/Eraac), [eliaslaouiti](https://github.com/eliaslaouiti), and [NaurisSadovskis](https://github.com/NaurisSadovskis) for making this happen! - -## Grafana Enterprise features - -General features are included in the Grafana Enterprise edition software. - -### White labeling customizes application title - -This release adds a new white labeling option to customize the application title. Learn how to configure it in [White labeling]({{< relref "../setup-grafana/enable-custom-branding/" >}}). - -``` -[white_labeling] -# Set to your company name to override application title -app_title = Your Company -``` - -### Configure reporting for timeout and concurrency - -This release adds more configuration for the reporting feature rendering requests. You can set the panel rendering request timeout and the maximum number of concurrent calls to the rendering service in your configuration. Learn how to do it in [Reporting]({{< relref "../enterprise/reporting/" >}}). - -``` -[reporting] -# Set timeout for each panel rendering request -rendering_timeout = 10s -# Set maximum number of concurrent calls to the rendering service -concurrent_render_limit = 10 -``` - -### Export dashboard as PDF - -This feature allows you to export a dashboard as a PDF document. All dashboard panels will be rendered as images and added into the PDF document. Learn more in [Export dashboard as PDF]({{< relref "../enterprise/export-pdf/" >}}). - -### Report landscape mode - -You can now use either portrait or landscape mode in your reports. Portrait will render three panels per page and landscape two. -{{< figure src="/static/img/docs/enterprise/reports_create_new.png" max-width="1024px" caption="New report" >}} - -[Reporting]({{< relref "../enterprise/reporting/" >}}) has been updated as a result of this change. - -### Azure OAuth Team Sync support - -When setting up OAuth with Microsoft Azure AD, you can now sync Azure groups with Teams in Grafana. -Learn more in [Team sync]({{< relref "../setup-grafana/configure-security/configure-team-sync/" >}}). diff --git a/emails/templates/layouts/default.txt b/emails/templates/layouts/default.txt index 1a323c772d3..543f4ac140d 100644 --- a/emails/templates/layouts/default.txt +++ b/emails/templates/layouts/default.txt @@ -1,3 +1,3 @@ {{> body }} -Sent by Grafana v[[.BuildVersion]] (c) 2021 Grafana Labs \ No newline at end of file +Sent by Grafana v[[.BuildVersion]] (c) 2022 Grafana Labs \ No newline at end of file diff --git a/emails/templates/ng_alert_notification.html b/emails/templates/ng_alert_notification.html index b7c7f6156dd..f97757e7869 100644 --- a/emails/templates/ng_alert_notification.html +++ b/emails/templates/ng_alert_notification.html @@ -4,6 +4,21 @@ [[Subject .Subject "[[.Title]]"]] [[ define "alert" ]] + + [[ if ne .ImageURL "" ]] + + + Alerting Panel + + + [[ end ]] + [[ if ne .EmbeddedImage "" ]] + + + Alerting Chart Attached Below + + + [[ end ]] Value: [[ .ValueString ]] @@ -101,7 +116,7 @@ [[ end ]] [[ if gt (len .Message) 0 ]] - [[ .Message ]] +
[[ .Message ]] [[ else ]]