Merge pull request #319 from grafana/bump-version-8.4.7

Release: Bump version to 8.4.7
"Release: Updated versions in package to 8.4.7"
2022-04-19 18:05:49 +02:00 · 2022-04-19 15:49:53 +00:00 · 2022-04-19 13:22:41 +02:00 · 2022-04-15 09:26:31 -04:00 · 2022-04-14 11:41:34 +02:00 · 2022-04-14 11:00:49 +02:00
5161 changed files with 55259 additions and 148312 deletions
--- a/.betterer.results
+++ b/.betterer.results
@@ -1,342 +0,0 @@
-// BETTERER RESULTS V2.
-// 
-// If this file contains merge conflicts, use `betterer merge` to automatically resolve them:
-// https://phenomnomnominal.github.io/betterer/docs/results-file/#merge
-//
-exports[`no enzyme tests`] = {
-  value: `{
-    "packages/grafana-ui/src/components/BarGauge/BarGauge.test.tsx:4199795290": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/ColorPicker/NamedColorsPalette.test.tsx:3311646309": [
-      [0, 31, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/FormField/FormField.test.tsx:3429087660": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/Forms/Legacy/Input/Input.test.tsx:3129955645": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/Gauge/Gauge.test.tsx:2525939157": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/Graph/Graph.test.tsx:1664091255": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/Graph/GraphTooltip/MultiModeGraphTooltip.test.tsx:1865444105": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/List/AbstractList.test.tsx:2972876749": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/Logs/LogLabels.test.tsx:1029448019": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/Logs/LogMessageAnsi.test.tsx:1630730648": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/Logs/LogRowContextProvider.test.tsx:2719724375": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/Logs/LogRows.test.tsx:3121815234": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/QueryField/QueryField.test.tsx:375894800": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/Slider/Slider.test.tsx:751112695": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/Typeahead/PartialHighlighter.test.tsx:1751923376": [
-      [0, 31, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/Typeahead/Typeahead.test.tsx:972524250": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/components/Typeahead/TypeaheadInfo.test.tsx:3512289373": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/slate-plugins/braces.test.tsx:1440546721": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/slate-plugins/clear.test.tsx:1085648664": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/slate-plugins/runner.test.tsx:446043290": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/grafana-ui/src/slate-plugins/suggestions.test.tsx:3654981205": [
-      [0, 18, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TracePageHeader/SpanGraph/CanvasSpanGraph.test.js:1974748555": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TracePageHeader/SpanGraph/GraphTicks.test.js:940336852": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TracePageHeader/SpanGraph/Scrubber.test.js:4256741694": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TracePageHeader/SpanGraph/TickLabels.test.js:2931161174": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TracePageHeader/SpanGraph/ViewingLayer.test.js:1676554632": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TracePageHeader/SpanGraph/index.test.js:186764954": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TracePageHeader/TracePageHeader.test.js:3242042907": [
-      [14, 26, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TracePageHeader/TracePageSearchBar.test.js:2807329716": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/ListView/index.test.js:1734982398": [
-      [14, 26, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/ReferencesButton.test.js:3807792910": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/SpanBar.test.js:1478502145": [
-      [14, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/SpanBarRow.test.js:3826510429": [
-      [14, 26, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/SpanDetail/AccordianKeyValues.test.js:2408389970": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/SpanDetail/AccordianLogs.test.js:3960703835": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/SpanDetail/AccordianReferences.test.js:2429764318": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/SpanDetail/AccordianText.test.js:1966455998": [
-      [14, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/SpanDetail/KeyValuesTable.test.js:3813002651": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/SpanDetail/TextList.test.js:3006381933": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/SpanDetail/index.test.js:3097530078": [
-      [16, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/SpanDetailRow.test.js:2623922632": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/SpanTreeOffset.test.js:1117377794": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/Ticks.test.js:743308415": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/TimelineHeaderRow/TimelineCollapser.test.js:4018342820": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/TimelineHeaderRow/TimelineColumnResizer.test.js:2286101708": [
-      [15, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/TimelineHeaderRow/TimelineHeaderRow.test.js:2106409544": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/TimelineHeaderRow/TimelineViewingLayer.test.js:1423129438": [
-      [15, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/VirtualizedTraceView.test.js:2326471104": [
-      [13, 26, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/TraceTimelineViewer/index.test.js:381298544": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/common/CopyIcon.test.js:187212136": [
-      [15, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/common/NewWindowIcon.test.js:1750458349": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/common/UiFindInput.test.js:2207118020": [
-      [14, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "packages/jaeger-ui-components/src/url/ReferenceLink.test.js:3249503373": [
-      [14, 26, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/core/components/PageActionBar/PageActionBar.test.tsx:1251504193": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/core/components/QueryOperationRow/QueryOperationAction.test.tsx:3032694716": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/core/components/QueryOperationRow/QueryOperationRow.test.tsx:2026575657": [
-      [0, 26, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/core/components/Select/FolderPicker.test.tsx:993468764": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/core/components/Select/MetricSelect.test.tsx:3351544014": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/alerting/AlertRuleList.test.tsx:2998938420": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/alerting/TestRuleResult.test.tsx:2358420489": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/api-keys/ApiKeysAddedModal.test.tsx:3246264379": [
-      [0, 20, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/dashboard/components/DashboardRow/DashboardRow.test.tsx:1463123173": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/dashboard/components/SaveDashboard/forms/SaveDashboardAsForm.test.tsx:1969004590": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/dashboard/components/SaveDashboard/forms/SaveDashboardForm.test.tsx:948029434": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/dashboard/components/ShareModal/ShareLink.test.tsx:2357087833": [
-      [0, 35, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/dashboard/dashgrid/DashboardGrid.test.tsx:2723773538": [
-      [0, 35, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/dashboard/dashgrid/PanelHeader/PanelHeaderCorner.test.tsx:2851646279": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/datasources/DashboardsTable.test.tsx:1950355032": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/datasources/DataSourceDashboards.test.tsx:1369048021": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/datasources/DataSourcesListPage.test.tsx:2960099202": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/datasources/settings/BasicSettings.test.tsx:625016324": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/datasources/settings/ButtonRow.test.tsx:1422996720": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/dimensions/editors/ThresholdsEditor/ThresholdsEditor.test.tsx:4164297658": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/explore/LiveLogs.test.tsx:156663779": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/explore/RichHistory/RichHistory.test.tsx:193587232": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/explore/RichHistory/RichHistoryCard.test.tsx:4263002507": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/explore/RichHistory/RichHistoryQueriesTab.test.tsx:3770907760": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/explore/RichHistory/RichHistorySettings.test.tsx:4065084278": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/explore/RichHistory/RichHistoryStarredTab.test.tsx:3750328521": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/explore/RunButton.test.tsx:4267530266": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/explore/SecondaryActions.test.tsx:1177396128": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/explore/TimeSyncButton.test.tsx:853739820": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/folders/FolderSettingsPage.test.tsx:1109052730": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/invites/InviteesTable.test.tsx:3612992381": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/org/OrgDetailsPage.test.tsx:3835042085": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/org/OrgProfile.test.tsx:623809345": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/teams/CreateTeam.test.tsx:1750035593": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/teams/TeamGroupSync.test.tsx:2526985933": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/teams/TeamList.test.tsx:854193970": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/teams/TeamMemberRow.test.tsx:1649328210": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/teams/TeamMembers.test.tsx:4089428239": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/teams/TeamPages.test.tsx:3990420214": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/teams/TeamSettings.test.tsx:2043271249": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/users/UsersActionBar.test.tsx:3740177621": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/users/UsersListPage.test.tsx:3908145117": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/features/users/UsersTable.test.tsx:263958312": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/datasource/cloud-monitoring/components/Aggregation.test.tsx:3822406835": [
-      [1, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/datasource/cloudwatch/components/ConfigEditor.test.tsx:1224072551": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/datasource/cloudwatch/components/LogsQueryField.test.tsx:1501504663": [
-      [2, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/datasource/elasticsearch/configuration/ConfigEditor.test.tsx:3481855642": [
-      [0, 26, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/datasource/elasticsearch/configuration/DataLinks.test.tsx:248699332": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/datasource/grafana-azure-monitor-datasource/components/deprecated/components/InsightsConfig.test.tsx:1107283234": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/datasource/influxdb/components/ConfigEditor.test.tsx:3456478975": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/datasource/loki/components/LokiExploreQueryEditor.test.tsx:1488067923": [
-      [0, 26, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/datasource/loki/components/LokiQueryEditor.test.tsx:146069464": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/datasource/loki/configuration/ConfigEditor.test.tsx:3658171175": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/datasource/loki/configuration/DebugSection.test.tsx:1551927716": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/datasource/loki/configuration/DerivedField.test.tsx:3570129984": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/datasource/loki/configuration/DerivedFields.test.tsx:2402631398": [
-      [0, 17, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/datasource/prometheus/configuration/AzureCredentialsForm.test.tsx:3424320489": [
-      [0, 19, 13, "RegExp match", "2409514259"]
-    ],
-    "public/app/plugins/panel/bargauge/BarGaugePanel.test.tsx:1597135392": [
-      [0, 31, 13, "RegExp match", "2409514259"]
-    ]
-  }`
-};
--- a/.betterer.ts
+++ b/.betterer.ts
@@ -1,5 +0,0 @@
-import { regexp } from '@betterer/regexp';
-
-export default {
-  'no enzyme tests': () => regexp(/from 'enzyme'/g).include('**/*.test.*'),
-};
--- a/.drone.yml
+++ b/.drone.yml
--- a/.eslintignore
+++ b/.eslintignore
@@ -1,18 +1,14 @@
-.git
-.github
-.yarn
-build
+node_modules
 compiled
-data
-deployment_tools_config.json
+build
+vendor
 devenv
+data
 dist
 e2e/tmp
-node_modules
-pkg
-public/lib/monaco
 scripts/grafana-server/tmp
-vendor
+public/lib/monaco
+deployment_tools_config.json

 # TS generate from cue by cuetsy
 **/*.gen.ts
@@ -20,6 +16,3 @@ vendor
 # Auto-generated localisation files
 public/locales/_build/
 public/locales/**/*.js
-
-# Auto-generated icon file
-packages/grafana-ui/src/components/Icon/iconBundle.ts
--- a/.eslintrc
+++ b/.eslintrc
@@ -1,24 +1,12 @@
 {
  "extends": ["@grafana/eslint-config"],
  "root": true,
-  "plugins": ["@emotion", "lodash", "jest", "import"],
-  "settings": {
-    "import/internal-regex": "^(app/)|(@grafana)",
-    "import/external-module-folders": ["node_modules", ".yarn"]
-  },
+  "plugins": ["no-only-tests", "@emotion", "lodash"],
  "rules": {
+    "no-only-tests/no-only-tests": "error",
    "react/prop-types": "off",
    "@emotion/jsx-import": "error",
-    "lodash/import-scope": [2, "member"],
-    "jest/no-focused-tests": "error",
-    "import/order": [
-      "error",
-      {
-        "groups": [["builtin", "external"], "internal", "parent", "sibling", "index"],
-        "newlines-between": "always",
-        "alphabetize": { "order": "asc" }
-      }
-    ]
+    "lodash/import-scope": [2, "member"]
  },
  "overrides": [
    {
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -53,18 +53,12 @@ go.sum @grafana/backend-platform
 /pkg/services/sqlstore/migrations @grafana/backend-platform @grafana/hosted-grafana-team
 *_mig.go @grafana/backend-platform @grafana/hosted-grafana-team

-# Grafana edge
+# Grafana live
 /pkg/services/live/ @grafana/grafana-edge-squad
-/pkg/services/searchV2/ @grafana/grafana-edge-squad
-/pkg/services/store/ @grafana/grafana-edge-squad
-/pkg/infra/filestore/ @grafana/grafana-edge-squad

-# Alerting
-/pkg/services/ngalert @grafana/alerting-squad-backend
-/pkg/services/sqlstore/migrations/ualert @grafana/alerting-squad-backend
-/pkg/services/alerting @grafana/alerting-squad-backend
-/pkg/tests/api/alerting @grafana/alerting-squad-backend
-/public/app/features/alerting @grafana/alerting-squad-frontend
+# Unified Alerting
+/pkg/services/ngalert @grafana/alerting-squad
+/pkg/services/sqlstore/migrations/ualert @grafana/alerting-squad

 # Library Services
 /pkg/services/libraryelements @grafana/user-essentials
@@ -102,13 +96,12 @@ go.sum @grafana/backend-platform
 /public/app/core/components/TimePicker @grafana/grafana-bi-squad
 /public/app/core/components/Layers @grafana/grafana-edge-squad
 /public/app/features/canvas/ @grafana/grafana-edge-squad
-/public/app/features/comments/ @grafana/grafana-edge-squad
 /public/app/features/dimensions/ @grafana/grafana-edge-squad
 /public/app/features/geo/ @grafana/grafana-edge-squad
 /public/app/features/live/ @grafana/grafana-edge-squad
 /public/app/features/explore/ @grafana/observability-experience-squad
 /public/app/features/plugins @grafana/plugins-platform-frontend
-/public/app/features/transformers/spatial @grafana/grafana-edge-squad
+/public/app/core/components/TransformersUI/spatial @grafana/grafana-edge-squad
 /public/app/plugins/panel/alertlist @grafana/alerting-squad
 /public/app/plugins/panel/barchart @grafana/grafana-bi-squad
 /public/app/plugins/panel/heatmap @grafana/grafana-bi-squad
--- a/.github/commands.json
+++ b/.github/commands.json
@@ -90,14 +90,6 @@
      "url":"https://github.com/orgs/grafana/projects/97"
    }
  },
-  {
-    "type":"label",
-    "name":"datasource/CloudWatch Logs",
-    "action":"addToProject",
-    "addToProject":{
-      "url":"https://github.com/orgs/grafana/projects/97"
-    }
-  },
  {
    "type":"label",
    "name":"datasource/GoogleCloudMonitoring",
@@ -106,12 +98,20 @@
      "url":"https://github.com/orgs/grafana/projects/97"
    }
  },
+  {
+    "type":"label",
+    "name":"oss-observability",
+    "action":"addToProject",
+    "addToProject":{
+      "url":"https://github.com/orgs/grafana/projects/54"
+    }
+  },
  {
    "type":"label",
    "name":"datasource/Prometheus",
    "action":"addToProject",
    "addToProject":{
-      "url":"https://github.com/orgs/grafana/projects/112"
+      "url":"https://github.com/orgs/grafana/projects/54"
    }
  },
  {
@@ -119,23 +119,7 @@
    "name":"datasource/InfluxDB",
    "action":"addToProject",
    "addToProject":{
-      "url":"https://github.com/orgs/grafana/projects/112"
-    }
-  },
-  {
-    "type":"label",
-    "name":"datasource/Graphite",
-    "action":"addToProject",
-    "addToProject":{
-      "url":"https://github.com/orgs/grafana/projects/112"
-    }
-  },
-  {
-    "type":"label",
-    "name":"datasource/OpenTSDB",
-    "action":"addToProject",
-    "addToProject":{
-      "url":"https://github.com/orgs/grafana/projects/112"
+      "url":"https://github.com/orgs/grafana/projects/54"
    }
  },
  {
@@ -143,7 +127,7 @@
    "name":"datasource/OpenSearch",
    "action":"addToProject",
    "addToProject":{
-      "url":"https://github.com/orgs/grafana/projects/110"
+      "url":"https://github.com/orgs/grafana/projects/54"
    }
  },
  {
@@ -151,7 +135,7 @@
    "name":"datasource/Loki",
    "action":"addToProject",
    "addToProject":{
-      "url":"https://github.com/orgs/grafana/projects/110"
+      "url":"https://github.com/orgs/grafana/projects/54"
    }
  },
  {
@@ -159,7 +143,7 @@
    "name":"datasource/Tempo",
    "action":"addToProject",
    "addToProject":{
-      "url":"https://github.com/orgs/grafana/projects/110"
+      "url":"https://github.com/orgs/grafana/projects/54"
    }
  },
  {
@@ -167,23 +151,7 @@
    "name":"datasource/Elasticsearch",
    "action":"addToProject",
    "addToProject":{
-      "url":"https://github.com/orgs/grafana/projects/110"
-    }
-  },
-  {
-    "type":"label",
-    "name":"datasource/Jaeger",
-    "action":"addToProject",
-    "addToProject":{
-      "url":"https://github.com/orgs/grafana/projects/110"
-    }
-  },
-  {
-    "type":"label",
-    "name":"datasource/Zipkin",
-    "action":"addToProject",
-    "addToProject":{
-      "url":"https://github.com/orgs/grafana/projects/110"
+      "url":"https://github.com/orgs/grafana/projects/54"
    }
  },
  {
@@ -191,7 +159,7 @@
    "name":"area/explore",
    "action":"addToProject",
    "addToProject":{
-      "url":"https://github.com/orgs/grafana/projects/111"
+      "url":"https://github.com/orgs/grafana/projects/54"
    }
  },
  {
@@ -209,13 +177,5 @@
    "removeFromProject":{
      "url":"https://github.com/grafana/grafana/projects/33"
    }
-  },
-  {
-    "type": "label",
-    "name": "team/grafana-partners",
-    "action": "addToProject",
-    "addToProject": {
-      "url": "https://github.com/orgs/grafana/projects/87"
-    }
  }
 ]
--- a/.github/pr-commands.json
+++ b/.github/pr-commands.json
@@ -179,17 +179,11 @@
    "action": "updateLabel",
    "addLabel": "area/dashboard/templating"
  },
-  {
-    "type": "changedfiles",
-    "matches": ["/pkg/services/ngalert/**/*", "/pkg/services/sqlstore/migrations/ualert/**/*", "/pkg/services/alerting/**/*", "/public/app/features/alerting/**/*", "/pkg/tests/api/alerting/**/*"],
-    "action": "updateLabel",
-    "addLabel": "area/alerting"
-  },
  {
    "type": "author",
    "name": "pr/external",
    "notMemberOf": { "org": "grafana" },
-    "ignoreList": ["renovate[bot]","dependabot[bot]"],
+    "ignoreList": ["renovate[bot]"],
    "action": "updateLabel",
    "addLabel": "pr/external"
  }
--- a/.github/renovate.json5
+++ b/.github/renovate.json5
@@ -11,16 +11,13 @@
    "@types/d3-scale-chromatic", // we should bump this once we move to esm modules
    "@types/grafana__slate-react", // should be updated when the `slate` package is updated
    "@types/react-icons", // jaeger-ui-components is being refactored to use @grafana/ui icons instead
-    "commander", // we are planning to remove this, so no need to update it
    "d3",
    "d3-force", // we should bump this once we move to esm modules
    "d3-interpolate", // we should bump this once we move to esm modules
    "d3-scale-chromatic", // we should bump this once we move to esm modules
+    "eslint", // wait until `eslint-plugin-react-hooks>4.2.0` is released
    "execa", // we should bump this once we move to esm modules
    "history", // we should bump this together with react-router-dom
-    "@mdx-js/react", // storybook peer-depends on it's 1.x version, we should upgrade this when we upgrade storybook
-    "monaco-editor", // due to us exposing this via @grafana/ui/CodeEditor's props bumping can break plugins
-    "react-hook-form", // due to us exposing these hooks via @grafana/ui form components bumping can break plugins
    "react-icons", // jaeger-ui-components is being refactored to use @grafana/ui icons instead
    "react-router-dom", // we should bump this together with history
    "slate",
--- a/.github/stale.yml
+++ b/.github/stale.yml
@@ -0,0 +1,47 @@
+# Configuration for probot-stale - https://github.com/probot/stale
+
+# General configuration
+# Label to use when marking as stale
+staleLabel: stale
+
+# Pull request specific configuration
+pulls:
+  # Number of days of inactivity before an Issue or Pull Request becomes stale
+  daysUntilStale: 14
+  # Number of days of inactivity before a stale Issue or Pull Request is closed.
+  # Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
+  daysUntilClose: 30
+  # Comment to post when marking as stale. Set to `false` to disable
+  markComment: >
+    This pull request has been automatically marked as stale because it has not had
+    activity in the last 2 weeks. It will be closed in 30 days if no further activity occurs. Please
+    feel free to give a status update now, ping for review, or re-open when it's ready.
+    Thank you for your contributions!
+  # Comment to post when closing a stale Issue or Pull Request.
+  closeComment: >
+     This pull request has been automatically closed because it has not had
+     activity in the last 30 days. Please feel free to give a status update now, ping for review, or re-open when it's ready.
+     Thank you for your contributions!
+  # Limit the number of actions per hour, from 1-30. Default is 30
+  limitPerRun: 1
+
+exemptLabels:
+  - help wanted
+  - type/bug
+  - type/feature-request
+  - Epic
+  - no stalebot
+
+# Issue specific configuration
+issues:
+  limitPerRun: 1
+  daysUntilStale: 100000
+  daysUntilClose: 100000
+  markComment: >
+    This issue has been automatically marked as stale because it has not had activity in the
+    last 100 days. It will be closed in the next 100 days if no activity occurs.
+    Thank you for your contributions.
+  closeComment: >
+    This issue has been automatically closed because it has not had activity in the
+    last month and a half. If this issue is still valid, please ping a maintainer and ask them to check this again.
+    Thank you for your contributions.
--- a/.github/workflows/bump-version.yml
+++ b/.github/workflows/bump-version.yml
@@ -4,7 +4,7 @@ on:
    inputs:
      version:
        required: true
-        default: '7.x.x'
+        default: '8.x.x'
  workflow_call:
    inputs:
      version_call:
--- a/.github/workflows/cloud-data-sources-code-coverage.yml
+++ b/.github/workflows/cloud-data-sources-code-coverage.yml
@@ -1,17 +0,0 @@
-name: Cloud data sources test code coverage
-on:
-  pull_request:
-    paths:
-      - 'pkg/tsdb/azuremonitor/**'
-      - 'pkg/tsdb/cloudwatch/**'
-      - 'pkg/tsdb/cloudmonitoring/**'
-      - 'public/app/plugins/datasource/grafana-azure-monitor-datasource/**'
-      - 'public/app/plugins/datasource/cloudwatch/**'
-      - 'public/app/plugins/datasource/cloud-monitoring/**'
-    branches-ignore:
-      - dependabot/**
-      - backport-**
-
-jobs:
-  workflow-call:
-    uses: grafana/code-coverage/.github/workflows/code-coverage.yml@v0.1.2
--- a/.github/workflows/codeql-analysis.yml
+++ b/.github/workflows/codeql-analysis.yml
@@ -8,12 +8,9 @@ name: "CodeQL"
 on:
  push:
    branches: [main, v1.8.x, v2.0.x, v2.1.x, v2.6.x, v3.0.x, v3.1.x, v4.0.x, v4.1.x, v4.2.x, v4.3.x, v4.4.x, v4.5.x, v4.6.x, v4.7.x, v5.0.x, v5.1.x, v5.2.x, v5.3.x, v5.4.x, v6.0.x, v6.1.x, v6.2.x, v6.3.x, v6.4.x, v6.5.x, v6.6.x, v6.7.x, v7.0.x, v7.1.x, v7.2.x]
-    paths-ignore:
-      - '**/*.cue'
-      - '**/*.json'
-      - '**/*.md'
-      - '**/*.txt'
-      - '**/*.yml'
+  pull_request:
+    # The branches below must be a subset of the branches above
+    branches: [main]
  schedule:
    - cron: '0 4 * * 6'

@@ -49,5 +46,21 @@ jobs:
        # Prefix the list here with "+" to use these queries and those in the config file.
        # queries: ./path/to/local/query, your-org/your-repo/queries@main

+    # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
+    # If this step fails, then you should remove it and run the build manually (see below)
+    - name: Autobuild
+      uses: github/codeql-action/autobuild@v1
+
+    # ℹ️ Command-line programs to run using the OS shell.
+    # 📚 https://git.io/JvXDl
+
+    # ✏️ If the Autobuild fails above, remove it and uncomment the following three lines
+    #    and modify them (or add more) to build your code if your project
+    #    uses a compiled language
+
+    #- run: |
+    #   make bootstrap
+    #   make release
+
    - name: Perform CodeQL Analysis
      uses: github/codeql-action/analyze@v1
--- a/.github/workflows/commands.yml
+++ b/.github/workflows/commands.yml
@@ -4,8 +4,7 @@ on:
    types: [labeled, unlabeled]
  issue_comment:
    types: [created]
-concurrency:
-  group: issue-commands-${{ github.event.issue.number }}
+
 jobs:
  main:
    runs-on: ubuntu-latest
--- a/.github/workflows/detect-breaking-changes-build.yml
+++ b/.github/workflows/detect-breaking-changes-build.yml
@@ -112,7 +112,7 @@ jobs:

      - name: Get link for the Github Action job
        id: job
-        uses: actions/github-script@v6
+        uses: actions/github-script@v5
        with:
          script: |
              const script = require('./.github/workflows/scripts/pr-get-job-link.js')
@@ -128,7 +128,7 @@ jobs:
      - name: Persisting the check output
        run: |
            mkdir -p ./levitate
-            echo "{ \"exit_code\": ${{ steps.breaking-changes.outputs.is_breaking }}, \"message\": \"${{ steps.breaking-changes.outputs.message }}\", \"job_link\": \"${{ steps.job.outputs.link }}#step:${GITHUB_STEP_NUMBER}:1\", \"pr_number\": \"${{ github.event.pull_request.number }}\" }" > ./levitate/result.json
+            echo "{ \"exit_code\": ${{ steps.breaking-changes.outputs.is_breaking }}, \"message\": \"${{ steps.breaking-changes.outputs.message }}\", \"job_link\": \"${{ steps.job.outputs.link }}#step:${GITHUB_STEP_NUMBER}:1\" }" > ./levitate/result.json

      - name: Upload check output as artifact
        uses: actions/upload-artifact@v2
--- a/.github/workflows/detect-breaking-changes-report.yml
+++ b/.github/workflows/detect-breaking-changes-report.yml
@@ -17,7 +17,7 @@ jobs:
    - uses: actions/checkout@v2
    
    - name: 'Download artifact'
-      uses: actions/github-script@v6
+      uses: actions/github-script@v5
      env:
        RUN_ID: ${{ github.event.workflow_run.id }}
      with:
@@ -53,7 +53,7 @@ jobs:
      run: unzip "${ARTIFACT_FOLDER}/${ARTIFACT_NAME}.zip" -d "${ARTIFACT_FOLDER}"
    
    - name: Parsing levitate result
-      uses: actions/github-script@v6
+      uses: actions/github-script@v5
      id: levitate-run
      with:
        script: |
@@ -63,7 +63,7 @@ jobs:

    - name: Check if "breaking change" label exists
      id: does-label-exist
-      uses: actions/github-script@v6
+      uses: actions/github-script@v5
      env:
        PR_NUMBER: ${{ github.event.workflow_run.pull_requests[0].number }}
      with:
@@ -82,7 +82,7 @@ jobs:
      if: ${{ steps.levitate-run.outputs.exit_code == 1 }}
      uses: marocchino/sticky-pull-request-comment@v2
      with:
-        number: ${{ steps.levitate-run.outputs.pr_number }}
+        number: ${{ github.event.workflow_run.pull_requests[0].number }}
        message: |
          ⚠️ &nbsp;&nbsp;**Possible breaking changes**

@@ -90,40 +90,22 @@ jobs:

          ${{ steps.levitate-run.outputs.message }}

-          [Console output](${{ steps.levitate-run.outputs.job_link }})
-          [Read our guideline](https://github.com/grafana/grafana/blob/main/contribute/breaking-changes-guide.md)
+          [Check console output](${{ steps.levitate-run.outputs.job_link }})

    - name: Remove comment on PR
      if: ${{ steps.levitate-run.outputs.exit_code == 0 }}
      uses: marocchino/sticky-pull-request-comment@v2
      with:
-        number: ${{ steps.levitate-run.outputs.pr_number }}
+        number: ${{ github.event.workflow_run.pull_requests[0].number }}
        delete: true

-    # Posts a notification to Slack if a PR has a breaking change and it did not have a breaking change before
-    - name: Post to Slack
-      id: slack
-      if: ${{ steps.levitate-run.outputs.exit_code == 1 && steps.does-label-exist.outputs.result == 0 }}
-      uses: slackapi/slack-github-action@v1.18.0
-      with:
-        payload: |
-          {
-            "pr_link": "https://github.com/grafana/grafana/pull/${{ steps.levitate-run.outputs.pr_number }}",
-            "pr_number": "${{ steps.levitate-run.outputs.pr_number }}",
-            "job_link": "${{ steps.levitate-run.outputs.job_link }}",
-            "reporting_job_link": "${{ github.event.workflow_run.html_url }}",
-            "message": "${{ steps.levitate-run.outputs.message }}"
-          }
-      env:
-        SLACK_WEBHOOK_URL: ${{ secrets.SLACK_LEVITATE_WEBHOOK_URL }}

    - name: Add "breaking change" label
      if: ${{ steps.levitate-run.outputs.exit_code == 1 && steps.does-label-exist.outputs.result == 0 }}
-      uses: actions/github-script@v6
+      uses: actions/github-script@v5
      env:
-        PR_NUMBER: ${{ steps.levitate-run.outputs.pr_number }}
+        PR_NUMBER: ${{ github.event.workflow_run.pull_requests[0].number }}
      with:
-        github-token: ${{ secrets.GH_BOT_ACCESS_TOKEN }}
        script: |
          await github.rest.issues.addLabels({
            issue_number: process.env.PR_NUMBER,
@@ -134,11 +116,10 @@ jobs:

    - name: Remove "breaking change" label
      if: ${{ steps.levitate-run.outputs.exit_code == 0 && steps.does-label-exist.outputs.result == 1 }}
-      uses: actions/github-script@v6
+      uses: actions/github-script@v5
      env:
-        PR_NUMBER: ${{ steps.levitate-run.outputs.pr_number }}
+        PR_NUMBER: ${{ github.event.workflow_run.pull_requests[0].number }}
      with:
-        github-token: ${{ secrets.GH_BOT_ACCESS_TOKEN }}
        script: |
          await github.rest.issues.removeLabel({
            issue_number: process.env.PR_NUMBER,
@@ -151,11 +132,10 @@ jobs:
    # Related issue: https://github.com/renovatebot/renovate/issues/1908
    - name: Add "grafana/plugins-platform-frontend" as a reviewer
      if: ${{ steps.levitate-run.outputs.exit_code == 1 }}
-      uses: actions/github-script@v6
+      uses: actions/github-script@v5
      env:
-        PR_NUMBER: ${{ steps.levitate-run.outputs.pr_number }}
+        PR_NUMBER: ${{ github.event.workflow_run.pull_requests[0].number }}
      with:
-        github-token: ${{ secrets.GH_BOT_ACCESS_TOKEN }}
        script: |
          await github.rest.pulls.requestReviewers({
            pull_number: process.env.PR_NUMBER,
@@ -167,11 +147,10 @@ jobs:

    - name: Remove "grafana/plugins-platform-frontend" from the list of reviewers
      if: ${{ steps.levitate-run.outputs.exit_code == 0 }}
-      uses: actions/github-script@v6
+      uses: actions/github-script@v5
      env:
-        PR_NUMBER: ${{ steps.levitate-run.outputs.pr_number }}
+        PR_NUMBER: ${{ github.event.workflow_run.pull_requests[0].number }}
      with:
-        github-token: ${{ secrets.GH_BOT_ACCESS_TOKEN }}
        script: |
          await github.rest.pulls.removeRequestedReviewers({
            pull_number: process.env.PR_NUMBER,
--- a/.github/workflows/pr-checks.yml
+++ b/.github/workflows/pr-checks.yml
@@ -12,8 +12,7 @@ on:
    types:
      - milestoned
      - demilestoned
-concurrency:
-  group: pr-checks-${{ github.event.number }}
+
 jobs:
  main:
    runs-on: ubuntu-latest
--- a/.github/workflows/pr-codeql-analysis-go.yml
+++ b/.github/workflows/pr-codeql-analysis-go.yml
@@ -1,29 +0,0 @@
-name: "CodeQL for PR / go"
-
-on:
-  pull_request:
-    branches: [main]
-    paths:
-      - '**/*.go'
-
-jobs:
-  analyze:
-    name: Analyze
-    runs-on: ubuntu-latest
-
-    steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
-
-    # Initializes the CodeQL tools for scanning.
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: "go"
-
-    - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@v1
--- a/.github/workflows/pr-codeql-analysis-javascript.yml
+++ b/.github/workflows/pr-codeql-analysis-javascript.yml
@@ -1,31 +0,0 @@
-name: "CodeQL for PR / javascript"
-
-on:
-  pull_request:
-    branches: [main]
-    paths:
-      - '**/*.js'
-      - '**/*.ts'
-      - '**/*.tsx'
-
-jobs:
-  analyze:
-    name: Analyze
-    runs-on: ubuntu-latest
-
-    steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
-
-    # Initializes the CodeQL tools for scanning.
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: "javascript"
-
-    - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@v1
--- a/.github/workflows/pr-codeql-analysis-python.yml
+++ b/.github/workflows/pr-codeql-analysis-python.yml
@@ -1,29 +0,0 @@
-name: "CodeQL for PR / python"
-
-on:
-  pull_request:
-    branches: [main]
-    paths:
-      - '**/*.py'
-
-jobs:
-  analyze:
-    name: Analyze
-    runs-on: ubuntu-latest
-
-    steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
-
-    # Initializes the CodeQL tools for scanning.
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: "python"
-
-    - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@v1
--- a/.github/workflows/pr-commands-closed.yml
+++ b/.github/workflows/pr-commands-closed.yml
@@ -3,8 +3,7 @@ on:
  pull_request:
    types:
      - closed      
-concurrency:
-  group: pr-commands-closed-${{ github.event.number }}
+
 jobs:
  close_job:
    # this job will only run if the PR has been closed without being merged
--- a/.github/workflows/pr-commands.yml
+++ b/.github/workflows/pr-commands.yml
@@ -4,8 +4,7 @@ on:
    types:
      - opened
      - synchronize
-concurrency:
-  group: pr-commands-${{ github.event.number }}
+
 jobs:
  main:
    runs-on: ubuntu-latest
--- a/.github/workflows/publish.yml
+++ b/.github/workflows/publish.yml
@@ -3,7 +3,7 @@ name: publish_docs
 on:
  push:
    branches:
-    - v8.5.x
+    - v8.4.x
    paths:
    - 'docs/sources/**'
    - 'packages/grafana-*/**'
@@ -20,7 +20,7 @@ jobs:
      uses: actions/setup-node@v2.5.1
      id: generate-docs
      with:
-        node-version: '16'
+        node-version: '14'
    - name: Get yarn cache directory path
      id: yarn-cache-dir-path
      run: echo "::set-output name=dir::$(yarn config get cacheFolder)"
--- a/.github/workflows/stale.yml
+++ b/.github/workflows/stale.yml
@@ -1,33 +0,0 @@
-name: 'Close stale issues and PRs'
-on:
-  schedule:
-    - cron: '30 1 * * *'
-
-jobs:
-  stale:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/stale@v4
-        with:
-          repo-token: ${{ secrets.GH_BOT_ACCESS_TOKEN }}
-          # Number of days of inactivity before a stale Issue or Pull Request is closed.
-          # Set to -1 to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
-          days-before-close: 14
-          # Number of days of inactivity before an Issue or Pull Request becomes stale
-          days-before-stale: 30
-          # We don't want any Issues to be marked as stale for now.
-          days-before-issue-stale: -1
-          exempt-issue-labels: no stalebot
-          exempt-pr-labels: no stalebot
-          operations-per-run: 500
-          stale-issue-label: stale
-          stale-pr-label: stale
-          stale-pr-message: >
-            This pull request has been automatically marked as stale because it has not had
-            activity in the last 30 days. It will be closed in 2 weeks if no further activity occurs. Please
-            feel free to give a status update now, ping for review, or re-open when it's ready.
-            Thank you for your contributions!
-          close-pr-message: >
-            This pull request has been automatically closed because it has not had
-            activity in the last 2 weeks. Please feel free to give a status update now, ping for review, or re-open when it's ready.
-            Thank you for your contributions!
--- a/.gitignore
+++ b/.gitignore
@@ -7,6 +7,7 @@ awsconfig
 /.awcache
 /dist
 /public/build
+public/dist/tsconfig.tsbuildinfo
 /public/views/index.html
 /public/views/error.html
 /emails/dist
@@ -16,7 +17,6 @@ awsconfig
 vendor/
 /docs/menu.yaml
 /requests
-tsconfig.tsbuildinfo

 # Yarn
 .yarn/*
@@ -39,7 +39,6 @@ tsconfig.tsbuildinfo

 # Enterprise devenv
 /devenv/docker/blocks/grafana-enterprise
-/devenv/docker/blocks/saml-enterprise

 /tmp
 tools/phantomjs/phantomjs
--- a/.husky/pre-commit
+++ b/.husky/pre-commit
@@ -1,8 +1,4 @@
 #!/bin/sh
-
-# Ignore husky hooks if no frontend code has been changed
-git diff --cached --name-only | grep -v --quiet "^pkg/" || exit 0
-
 . "$(dirname "$0")/_/husky.sh"

 yarn run precommit
--- a/.nvmrc
+++ b/.nvmrc
@@ -1 +1 @@
-v16.14.0
+v16.13.2
--- a/.prettierignore
+++ b/.prettierignore
@@ -1,23 +1,14 @@
 .git
 .github
-.yarn
-build
-compiled
-data
-deployment_tools_config.json
-devenv
-dist
-e2e/tmp
+dist/
+pkg/
 node_modules
-pkg
-public/lib/monaco
-public/sass/*.generated.scss
+public/vendor/
+vendor/
+/data/
+e2e/tmp
 scripts/grafana-server/tmp
-vendor
-
-# TS generate from cue by cuetsy
-**/*.gen.ts
-
-# Auto-generated localisation files
-public/locales/_build/
-public/locales/**/*.js
+public/build/
+public/sass/*.generated.scss
+devenv/
+public/lib/monaco
--- a/.vscode/launch.json
+++ b/.vscode/launch.json
@@ -8,15 +8,13 @@
      "mode": "auto",
      "program": "${workspaceFolder}/pkg/cmd/grafana-server/",
      "env": {},
-      "cwd": "${workspaceFolder}",
      "args": ["--homepath", "${workspaceFolder}", "--packaging", "dev"]
    },
    {
      "name": "Debug Jest test",
      "type": "node",
      "request": "launch",
-      "runtimeExecutable": "yarn",
-      "runtimeArgs": ["run", "jest", "--runInBand", "${file}"],
+      "runtimeArgs": ["--inspect-brk", "${workspaceRoot}/node_modules/.bin/jest", "--runInBand", "${file}"],
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "port": 9229
--- a/.yarn/releases/yarn-3.1.1.cjs
+++ b/.yarn/releases/yarn-3.1.1.cjs
--- a/.yarn/releases/yarn-3.2.0.cjs
+++ b/.yarn/releases/yarn-3.2.0.cjs
--- a/.yarn/sdks/eslint/package.json
+++ b/.yarn/sdks/eslint/package.json
@@ -1,6 +1,6 @@
 {
  "name": "eslint",
-  "version": "8.11.0-sdk",
+  "version": "7.28.0-sdk",
  "main": "./lib/api.js",
  "type": "commonjs"
 }
--- a/.yarn/sdks/prettier/package.json
+++ b/.yarn/sdks/prettier/package.json
@@ -1,6 +1,6 @@
 {
  "name": "prettier",
-  "version": "2.5.1-sdk",
+  "version": "2.2.1-sdk",
  "main": "./index.js",
  "type": "commonjs"
 }
--- a/.yarn/sdks/stylelint/bin/stylelint.js
+++ b/.yarn/sdks/stylelint/bin/stylelint.js
@@ -0,0 +1,20 @@
+#!/usr/bin/env node
+
+const {existsSync} = require(`fs`);
+const {createRequire, createRequireFromPath} = require(`module`);
+const {resolve} = require(`path`);
+
+const relPnpApiPath = "../../../../.pnp.cjs";
+
+const absPnpApiPath = resolve(__dirname, relPnpApiPath);
+const absRequire = (createRequire || createRequireFromPath)(absPnpApiPath);
+
+if (existsSync(absPnpApiPath)) {
+  if (!process.versions.pnp) {
+    // Setup the environment to be able to require stylelint/bin/stylelint.js
+    require(absPnpApiPath).setup();
+  }
+}
+
+// Defer to the real stylelint/bin/stylelint.js your application uses
+module.exports = absRequire(`stylelint/bin/stylelint.js`);
--- a/.yarn/sdks/stylelint/lib/index.js
+++ b/.yarn/sdks/stylelint/lib/index.js
@@ -0,0 +1,20 @@
+#!/usr/bin/env node
+
+const {existsSync} = require(`fs`);
+const {createRequire, createRequireFromPath} = require(`module`);
+const {resolve} = require(`path`);
+
+const relPnpApiPath = "../../../../.pnp.cjs";
+
+const absPnpApiPath = resolve(__dirname, relPnpApiPath);
+const absRequire = (createRequire || createRequireFromPath)(absPnpApiPath);
+
+if (existsSync(absPnpApiPath)) {
+  if (!process.versions.pnp) {
+    // Setup the environment to be able to require stylelint/lib/index.js
+    require(absPnpApiPath).setup();
+  }
+}
+
+// Defer to the real stylelint/lib/index.js your application uses
+module.exports = absRequire(`stylelint/lib/index.js`);
--- a/.yarn/sdks/stylelint/package.json
+++ b/.yarn/sdks/stylelint/package.json
@@ -0,0 +1,6 @@
+{
+  "name": "stylelint",
+  "version": "14.0.1-sdk",
+  "main": "lib/index.js",
+  "type": "commonjs"
+}
--- a/.yarn/sdks/typescript/lib/tsserver.js
+++ b/.yarn/sdks/typescript/lib/tsserver.js
@@ -18,7 +18,6 @@ const moduleWrapper = tsserver => {
  const pnpApi = require(`pnpapi`);

  const isVirtual = str => str.match(/\/(\$\$virtual|__virtual__)\//);
-  const isPortal = str => str.startsWith("portal:/");
  const normalize = str => str.replace(/\\/g, `/`).replace(/^\/?/, `/`);

  const dependencyTreeRoots = new Set(pnpApi.getDependencyTreeRoots().map(locator => {
@@ -45,7 +44,7 @@ const moduleWrapper = tsserver => {
      const resolved = isVirtual(str) ? pnpApi.resolveVirtual(str) : str;
      if (resolved) {
        const locator = pnpApi.findPackageLocator(resolved);
-        if (locator && (dependencyTreeRoots.has(`${locator.name}@${locator.reference}`) || isPortal(locator.reference))) {
+        if (locator && dependencyTreeRoots.has(`${locator.name}@${locator.reference}`)) {
          str = resolved;
        }
      }
@@ -86,7 +85,7 @@ const moduleWrapper = tsserver => {
          // everything else is up to neovim
          case `neovim`: {
            str = normalize(resolved).replace(/\.zip\//, `.zip::`);
-            str = `zipfile://${str}`;
+            str = `zipfile:${str}`;
          } break;

          default: {
@@ -101,7 +100,8 @@ const moduleWrapper = tsserver => {

  function fromEditorPath(str) {
    switch (hostInfo) {
-      case `coc-nvim`: {
+      case `coc-nvim`:
+      case `neovim`: {
        str = str.replace(/\.zip::/, `.zip/`);
        // The path for coc-nvim is in format of /<pwd>/zipfile:/<pwd>/.yarn/...
        // So in order to convert it back, we use .* to match all the thing
@@ -111,12 +111,6 @@ const moduleWrapper = tsserver => {
          : str.replace(/^.*zipfile:/, ``);
      } break;

-      case `neovim`: {
-        str = str.replace(/\.zip::/, `.zip/`);
-        // The path for neovim is in format of zipfile:///<pwd>/.yarn/...
-        return str.replace(/^zipfile:\/\//, ``);
-      } break;
-
      case `vscode`:
      default: {
        return process.platform === `win32`
@@ -149,9 +143,8 @@ const moduleWrapper = tsserver => {
  let hostInfo = `unknown`;

  Object.assign(Session.prototype, {
-    onMessage(/** @type {string | object} */ message) {
-      const isStringMessage = typeof message === 'string';
-      const parsedMessage = isStringMessage ? JSON.parse(message) : message;
+    onMessage(/** @type {string} */ message) {
+      const parsedMessage = JSON.parse(message)

      if (
        parsedMessage != null &&
@@ -165,14 +158,9 @@ const moduleWrapper = tsserver => {
        }
      }

-      const processedMessageJSON = JSON.stringify(parsedMessage, (key, value) => {
-        return typeof value === 'string' ? fromEditorPath(value) : value;
-      });
-
-      return originalOnMessage.call(
-        this,
-        isStringMessage ? processedMessageJSON : JSON.parse(processedMessageJSON)
-      );
+      return originalOnMessage.call(this, JSON.stringify(parsedMessage, (key, value) => {
+        return typeof value === `string` ? fromEditorPath(value) : value;
+      }));
    },

    send(/** @type {any} */ msg) {
--- a/.yarn/sdks/typescript/lib/tsserverlibrary.js
+++ b/.yarn/sdks/typescript/lib/tsserverlibrary.js
@@ -18,7 +18,6 @@ const moduleWrapper = tsserver => {
  const pnpApi = require(`pnpapi`);

  const isVirtual = str => str.match(/\/(\$\$virtual|__virtual__)\//);
-  const isPortal = str => str.startsWith("portal:/");
  const normalize = str => str.replace(/\\/g, `/`).replace(/^\/?/, `/`);

  const dependencyTreeRoots = new Set(pnpApi.getDependencyTreeRoots().map(locator => {
@@ -45,7 +44,7 @@ const moduleWrapper = tsserver => {
      const resolved = isVirtual(str) ? pnpApi.resolveVirtual(str) : str;
      if (resolved) {
        const locator = pnpApi.findPackageLocator(resolved);
-        if (locator && (dependencyTreeRoots.has(`${locator.name}@${locator.reference}`) || isPortal(locator.reference))) {
+        if (locator && dependencyTreeRoots.has(`${locator.name}@${locator.reference}`)) {
          str = resolved;
        }
      }
@@ -86,7 +85,7 @@ const moduleWrapper = tsserver => {
          // everything else is up to neovim
          case `neovim`: {
            str = normalize(resolved).replace(/\.zip\//, `.zip::`);
-            str = `zipfile://${str}`;
+            str = `zipfile:${str}`;
          } break;

          default: {
@@ -101,7 +100,8 @@ const moduleWrapper = tsserver => {

  function fromEditorPath(str) {
    switch (hostInfo) {
-      case `coc-nvim`: {
+      case `coc-nvim`:
+      case `neovim`: {
        str = str.replace(/\.zip::/, `.zip/`);
        // The path for coc-nvim is in format of /<pwd>/zipfile:/<pwd>/.yarn/...
        // So in order to convert it back, we use .* to match all the thing
@@ -111,12 +111,6 @@ const moduleWrapper = tsserver => {
          : str.replace(/^.*zipfile:/, ``);
      } break;

-      case `neovim`: {
-        str = str.replace(/\.zip::/, `.zip/`);
-        // The path for neovim is in format of zipfile:///<pwd>/.yarn/...
-        return str.replace(/^zipfile:\/\//, ``);
-      } break;
-
      case `vscode`:
      default: {
        return process.platform === `win32`
@@ -149,9 +143,8 @@ const moduleWrapper = tsserver => {
  let hostInfo = `unknown`;

  Object.assign(Session.prototype, {
-    onMessage(/** @type {string | object} */ message) {
-      const isStringMessage = typeof message === 'string';
-      const parsedMessage = isStringMessage ? JSON.parse(message) : message;
+    onMessage(/** @type {string} */ message) {
+      const parsedMessage = JSON.parse(message)

      if (
        parsedMessage != null &&
@@ -165,14 +158,9 @@ const moduleWrapper = tsserver => {
        }
      }

-      const processedMessageJSON = JSON.stringify(parsedMessage, (key, value) => {
-        return typeof value === 'string' ? fromEditorPath(value) : value;
-      });
-
-      return originalOnMessage.call(
-        this,
-        isStringMessage ? processedMessageJSON : JSON.parse(processedMessageJSON)
-      );
+      return originalOnMessage.call(this, JSON.stringify(parsedMessage, (key, value) => {
+        return typeof value === `string` ? fromEditorPath(value) : value;
+      }));
    },

    send(/** @type {any} */ msg) {
--- a/.yarnrc.yml
+++ b/.yarnrc.yml
@@ -34,7 +34,7 @@ packageExtensions:
  doctrine@3.0.0:
    dependencies:
      assert: 2.0.0
-  moveable@0.28.0:
+  moveable@0.27.3:
    dependencies:
      "@daybrush/utils": 1.6.0
      framework-utils: ^1.1.0
@@ -49,13 +49,13 @@ packageExtensions:
  react-compat-css-styled@1.0.8:
    dependencies:
      react-simple-compat: 1.2.1
-  react-compat-moveable@0.16.0:
+  react-compat-moveable@0.15.2:
    dependencies:
      "@egjs/agent": ^2.2.1
      "@egjs/children-differ": ^1.0.1
      "@scena/matrix": 1.1.1
      css-to-mat: ^1.0.3
-      gesto: ^1.7.0
+      gesto: ^1.4.0
      overlap-area: ^1.0.0
      react-simple-compat: 1.2.1
    peerDependencies:
@@ -78,4 +78,4 @@ plugins:
  - path: .yarn/plugins/@yarnpkg/plugin-outdated.cjs
    spec: "https://mskelton.dev/yarn-outdated/v2"

-yarnPath: .yarn/releases/yarn-3.2.0.cjs
+yarnPath: .yarn/releases/yarn-3.1.1.cjs
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,231 +1,3 @@
-<!-- 8.5.4 START -->
-
-# 8.5.4 (2022-05-30)
-
-### Features and enhancements
-
- **Alerting:** Remove disabled flag for data source when migrating alerts. [#48559](https://github.com/grafana/grafana/pull/48559), [@yuri-tceretian](https://github.com/yuri-tceretian)
- **Alerting:** Show notification tab of legacy alerting only to editor. [#49624](https://github.com/grafana/grafana/pull/49624), [@yuri-tceretian](https://github.com/yuri-tceretian)
- **Alerting:** Update migration to migrate only alerts that belong to existing org\dashboard. [#49192](https://github.com/grafana/grafana/pull/49192), [@yuri-tceretian](https://github.com/yuri-tceretian)
- **AzureMonitor:** Do not quote variables when a custom "All" variable option is used. [#49428](https://github.com/grafana/grafana/pull/49428), [@andresmgot](https://github.com/andresmgot)
- **AzureMonitor:** Update allowed namespaces. [#48468](https://github.com/grafana/grafana/pull/48468), [@jcolladokuri](https://github.com/jcolladokuri)
- **CloudMonitor:** Correctly encode default project response. [#49510](https://github.com/grafana/grafana/pull/49510), [@aangelisc](https://github.com/aangelisc)
- **Cloudwatch:** Add support for new AWS/RDS EBS\* metrics. [#48798](https://github.com/grafana/grafana/pull/48798), [@szymonpk](https://github.com/szymonpk)
- **InfluxDB:** Use backend for influxDB by default via feature toggle. [#48453](https://github.com/grafana/grafana/pull/48453), [@yesoreyeram](https://github.com/yesoreyeram)
- **Legend:** Use correct unit for percent and count calculations. [#49004](https://github.com/grafana/grafana/pull/49004), [@dprokop](https://github.com/dprokop)
- **LokI:** use millisecond steps in Grafana 8.5.x. [#48630](https://github.com/grafana/grafana/pull/48630), [@gabor](https://github.com/gabor)
- **Plugins:** Introduce HTTP 207 Multi Status response to api/ds/query. [#48550](https://github.com/grafana/grafana/pull/48550), [@wbrowne](https://github.com/wbrowne)
- **Reporting:** Improve PDF file size using grid layout. (Enterprise)
- **Transformations:** Add an All Unique Values Reducer. [#48653](https://github.com/grafana/grafana/pull/48653), [@josiahg](https://github.com/josiahg)
- **Transformers:** avoid error when the ExtractFields source field is missing. [#49368](https://github.com/grafana/grafana/pull/49368), [@wardbekker](https://github.com/wardbekker)
- **[v8.5.x] Alerting:** Update migration to migrate only alerts that belong to existing org\dashboard. [#49199](https://github.com/grafana/grafana/pull/49199), [@grafanabot](https://github.com/grafanabot)
- **[v8.5.x] Reporting:** Improve PDF file size using grid layout. (Enterprise)
-
-### Bug fixes
-
- **Alerting:** Allow disabling override timings for notification policies. [#48648](https://github.com/grafana/grafana/pull/48648), [@gillesdemey](https://github.com/gillesdemey)
- **Alerting:** Allow serving images from custom url path. [#49022](https://github.com/grafana/grafana/pull/49022), [@gillesdemey](https://github.com/gillesdemey)
- **Alerting:** Apply Custom Headers to datasource queries. [#47860](https://github.com/grafana/grafana/pull/47860), [@joeblubaugh](https://github.com/joeblubaugh)
- **Alerting:** Fix RBAC actions for notification policies. [#49185](https://github.com/grafana/grafana/pull/49185), [@yuri-tceretian](https://github.com/yuri-tceretian)
- **Alerting:** Fix access to alerts for viewer with editor permissions when RBAC is disabled. [#49270](https://github.com/grafana/grafana/pull/49270), [@yuri-tceretian](https://github.com/yuri-tceretian)
- **Alerting:** Fix anonymous access to alerting. [#49203](https://github.com/grafana/grafana/pull/49203), [@yuri-tceretian](https://github.com/yuri-tceretian)
- **Alerting:** correctly show all alerts in a folder. [#48684](https://github.com/grafana/grafana/pull/48684), [@gillesdemey](https://github.com/gillesdemey)
- **AzureMonitor:** Fixes metric definition for Azure Storage queue/file/blob/table resources. [#49101](https://github.com/grafana/grafana/pull/49101), [@aangelisc](https://github.com/aangelisc)
- **Dashboard:** Fix dashboard update permission check. [#48746](https://github.com/grafana/grafana/pull/48746), [@IevaVasiljeva](https://github.com/IevaVasiljeva)
- **DashboardExport:** Fix exporting and importing dashboards where query data source ended up as incorrect. [#48410](https://github.com/grafana/grafana/pull/48410), [@torkelo](https://github.com/torkelo)
- **FileUpload:** clicking the `Upload file` button now opens the modal correctly. [#48766](https://github.com/grafana/grafana/pull/48766), [@ashharrison90](https://github.com/ashharrison90)
- **GrafanaUI:** Fix color of links in error Tooltips in light theme. [#49327](https://github.com/grafana/grafana/pull/49327), [@joshhunt](https://github.com/joshhunt)
- **LibraryPanels:** Fix library panels not connecting properly in imported dashboards. [#49161](https://github.com/grafana/grafana/pull/49161), [@joshhunt](https://github.com/joshhunt)
- **Loki:** Improve unpack parser handling. [#49074](https://github.com/grafana/grafana/pull/49074), [@gabor](https://github.com/gabor)
- **RolePicker:** Fix menu position on smaller screens. [#48429](https://github.com/grafana/grafana/pull/48429), [@Clarity-89](https://github.com/Clarity-89)
- **TimeRange:** Fixes updating time range from url and browser history. [#48657](https://github.com/grafana/grafana/pull/48657), [@torkelo](https://github.com/torkelo)
- **TimeSeries:** Fix detection & rendering of sparse datapoints. [#48841](https://github.com/grafana/grafana/pull/48841), [@leeoniya](https://github.com/leeoniya)
- **Timeseries:** Fix outside range stale state. [#49633](https://github.com/grafana/grafana/pull/49633), [@ryantxu](https://github.com/ryantxu)
- **Tooltip:** Fix links not legible in Tooltips when using light theme. [#48748](https://github.com/grafana/grafana/pull/48748), [@joshhunt](https://github.com/joshhunt)
- **Tooltip:** Sort decimals using standard numeric compare. [#49084](https://github.com/grafana/grafana/pull/49084), [@dprokop](https://github.com/dprokop)
- **Transforms:** Labels to fields, fix label picker layout. [#49304](https://github.com/grafana/grafana/pull/49304), [@torkelo](https://github.com/torkelo)
- **Variables:** Fixes issue with data source variables not updating queries with variable. [#49478](https://github.com/grafana/grafana/pull/49478), [@torkelo](https://github.com/torkelo)
- **[v8.5.x] Alerting:** Fix RBAC actions for notification policies (#49185). [#49348](https://github.com/grafana/grafana/pull/49348), [@yuri-tceretian](https://github.com/yuri-tceretian)
- **[v8.5.x] Alerting:** Fix access to alerts for viewer with editor permissions when RBAC is disabled. [#49427](https://github.com/grafana/grafana/pull/49427), [@konrad147](https://github.com/konrad147)
- **[v8.5.x] Alerting:** Fix anonymous access to alerting. [#49268](https://github.com/grafana/grafana/pull/49268), [@yuri-tceretian](https://github.com/yuri-tceretian)
-
-### Breaking changes
-
-For a data source query made via /api/ds/query :
-
- If the `DatasourceQueryMultiStatus` feature is enabled and
-  - The data source response has an error set as part of the `DataResponse`, the resulting HTTP status code is now `207 Multi Status` instead of `400 Bad gateway`
- If the `DatasourceQueryMultiStatus` feature is **not** enabled and
-  - The data source response has an error set as part of the `DataResponse`, the resulting HTTP status code is `400 Bad Request` (no breaking change)
-    --> Issue [#48550](https://github.com/grafana/grafana/issues/48550)
-
-<!-- 8.5.4 END -->
-<!-- 8.5.3 START -->
-
-# 8.5.3
-
-### Bug fixes
-
- **Security:** fixes CVE-2022-29170. [#49240](https://github.com/grafana/grafana/pull/49240), [@xlson](https://github.com/xlson)
-
-<!-- 8.5.3 END -->
-<!-- 8.5.2 START -->
-
-# 8.5.2 (2022-05-03)
-
-### Features and enhancements
-
- **Alerting:** Add safeguard for migrations that might cause dataloss. [#48526](https://github.com/grafana/grafana/pull/48526), [@JohnnyQQQQ](https://github.com/JohnnyQQQQ)
- **AzureMonitor:** Add support for not equals and startsWith operators when creating Azure Metrics dimension filters. [#48077](https://github.com/grafana/grafana/pull/48077), [@aangelisc](https://github.com/aangelisc)
- **Elasticsearch:** Add deprecation notice for < 7.10 versions. [#48506](https://github.com/grafana/grafana/pull/48506), [@ivanahuckova](https://github.com/ivanahuckova)
- **Traces:** Filter by service/span name and operation in Tempo and Jaeger. [#48209](https://github.com/grafana/grafana/pull/48209), [@joey-grafana](https://github.com/joey-grafana)
-
-### Bug fixes
-
- **AzureAd Oauth:** Fix strictMode to reject users without an assigned role. [#48474](https://github.com/grafana/grafana/pull/48474), [@kyschouv](https://github.com/kyschouv)
- **CloudWatch:** Fix variable query tag migration. [#48587](https://github.com/grafana/grafana/pull/48587), [@iwysiu](https://github.com/iwysiu)
- **Plugins:** Ensure catching all appropriate 4xx api/ds/query scenarios. [#47565](https://github.com/grafana/grafana/pull/47565), [@wbrowne](https://github.com/wbrowne)
-
-<!-- 8.5.2 END -->
-<!-- 8.5.1 START -->
-
-# 8.5.1 (2022-04-27)
-
-### Bug fixes
-
- **Azure Monitor:** Fix space character encoding for metrics query link to Azure Portal. [#48139](https://github.com/grafana/grafana/pull/48139), [@kevinwcyu](https://github.com/kevinwcyu)
- **CloudWatch:** Prevent log groups from being removed on query change. [#47994](https://github.com/grafana/grafana/pull/47994), [@asimpson](https://github.com/asimpson)
- **Cloudwatch:** Fix template variables in variable queries. [#48140](https://github.com/grafana/grafana/pull/48140), [@iwysiu](https://github.com/iwysiu)
- **Explore:** Prevent direct access to explore if disabled via feature toggle. [#47714](https://github.com/grafana/grafana/pull/47714), [@Elfo404](https://github.com/Elfo404)
- **InfluxDB:** Fixes invalid no data alerts. [#48295](https://github.com/grafana/grafana/pull/48295), [@yesoreyeram](https://github.com/yesoreyeram)
- **Navigation:** Prevent navbar briefly showing on login. [#47968](https://github.com/grafana/grafana/pull/47968), [@ashharrison90](https://github.com/ashharrison90)
- **Plugins Catalog:** Fix styling of hyperlinks. [#48196](https://github.com/grafana/grafana/pull/48196), [@marefr](https://github.com/marefr)
- **Table:** Fix filter crashes table. [#48258](https://github.com/grafana/grafana/pull/48258), [@zoltanbedi](https://github.com/zoltanbedi)
- **TimeSeries:** Properly stack series with missing datapoints. [#48321](https://github.com/grafana/grafana/pull/48321), [@leeoniya](https://github.com/leeoniya)
-
-<!-- 8.5.1 END -->
-<!-- 8.5.0 START -->
-
-# 8.5.0 (2022-04-21)
-
-### Features and enhancements
-
- **Alerting:** Add contact points provisioning API. [#47197](https://github.com/grafana/grafana/pull/47197), [@JohnnyQQQQ](https://github.com/JohnnyQQQQ)
- **Alerting:** Add resolved count to notification title when both firing and resolved present. [#46697](https://github.com/grafana/grafana/pull/46697), [@JacobsonMT](https://github.com/JacobsonMT)
- **Alerting:** Alert rule should wait For duration when execution error state is Alerting. [#47052](https://github.com/grafana/grafana/pull/47052), [@grobinson-grafana](https://github.com/grobinson-grafana)
- **Alerting:** Classic conditions can now display multiple values. [#46971](https://github.com/grafana/grafana/pull/46971), [@gotjosh](https://github.com/gotjosh)
- **Alerting:** Display query from grafana-managed alert rules on `/api/v1/rules`. [#45969](https://github.com/grafana/grafana/pull/45969), [@gotjosh](https://github.com/gotjosh)
- **Alerting:** Enhance support for arbitrary group names in managed alerts. [#47785](https://github.com/grafana/grafana/pull/47785), [@gillesdemey](https://github.com/gillesdemey)
- **Alerting:** add field for custom slack endpoint. [#45751](https://github.com/grafana/grafana/pull/45751), [@nathanrodman](https://github.com/nathanrodman)
- **Azure Monitor :** Adding json formatting of error messages in Panel Header Corner and Inspect Error Tab. [#44877](https://github.com/grafana/grafana/pull/44877), [@yaelleC](https://github.com/yaelleC)
- **Azure Monitor:** Add 2 more Curated Dashboards for VM Insights. [#45187](https://github.com/grafana/grafana/pull/45187), [@jcolladokuri](https://github.com/jcolladokuri)
- **CloudWatch:** Handle new error codes for MetricInsights. [#47033](https://github.com/grafana/grafana/pull/47033), [@Gabrielopesantos](https://github.com/Gabrielopesantos)
- **Dashboards:** show changes in save dialog. [#46557](https://github.com/grafana/grafana/pull/46557), [@ryantxu](https://github.com/ryantxu)
- **DataSource:** Default data source is no longer a persisted state but just the default data source for new panels. [#45132](https://github.com/grafana/grafana/pull/45132), [@torkelo](https://github.com/torkelo)
- **DataSourcePlugin API:** Allow queries import when changing data source type. [#47435](https://github.com/grafana/grafana/pull/47435), [@dprokop](https://github.com/dprokop)
- **Explore:** Remove return to panel button. [#45018](https://github.com/grafana/grafana/pull/45018), [@gelicia](https://github.com/gelicia)
- **Explore:** allow users to save Explore state to a new panel in a new dashboard. [#45148](https://github.com/grafana/grafana/pull/45148), [@Elfo404](https://github.com/Elfo404)
- **Instrumentation:** Proxy status code correction and various improvements. [#47473](https://github.com/grafana/grafana/pull/47473), [@marefr](https://github.com/marefr)
- **Logging:** Introduce feature toggle to activate gokit/log format. [#47336](https://github.com/grafana/grafana/pull/47336), [@ying-jeanne](https://github.com/ying-jeanne)
- **NewsPanel:** Add support for Atom feeds. [#45390](https://github.com/grafana/grafana/pull/45390), [@kaydelaney](https://github.com/kaydelaney)
- **Plugins:** Add deprecation notice for /api/tsdb/query endpoint. [#45238](https://github.com/grafana/grafana/pull/45238), [@wbrowne](https://github.com/wbrowne)
- **Plugins:** Adding support for traceID field to accept variables. [#45559](https://github.com/grafana/grafana/pull/45559), [@vinisdl](https://github.com/vinisdl)
- **PostgreSQL:** \_\_unixEpochGroup to support arithmetic expression as argument. [#46764](https://github.com/grafana/grafana/pull/46764), [@s0nik42](https://github.com/s0nik42)
- **Profile/Help:** Expose option to disable profile section and help menu. [#46308](https://github.com/grafana/grafana/pull/46308), [@cameronwaterman](https://github.com/cameronwaterman)
- **Prometheus:** Enable new visual query builder by default. [#46634](https://github.com/grafana/grafana/pull/46634), [@torkelo](https://github.com/torkelo)
- **SAML:** Allow disabling of SAML signups. [#47481](https://github.com/grafana/grafana/pull/47481), [@mmandrus](https://github.com/mmandrus)
- **SAML:** Allow disabling of SAML signups. (Enterprise)
- **Table:** New pagination option. [#45732](https://github.com/grafana/grafana/pull/45732), [@zoltanbedi](https://github.com/zoltanbedi)
- **TablePanel:** Add cell inspect option. [#45620](https://github.com/grafana/grafana/pull/45620), [@dprokop](https://github.com/dprokop)
- **Tempo / Trace Viewer:** Support Span Links in Trace Viewer. [#45632](https://github.com/grafana/grafana/pull/45632), [@Shachi16](https://github.com/Shachi16)
- **Tempo:** Download span references in data inspector. [#47074](https://github.com/grafana/grafana/pull/47074), [@connorlindsey](https://github.com/connorlindsey)
- **Tempo:** Separate trace to logs and loki search datasource config. [#46655](https://github.com/grafana/grafana/pull/46655), [@connorlindsey](https://github.com/connorlindsey)
- **Trace View:** Show number of child spans. [#44393](https://github.com/grafana/grafana/pull/44393), [@tharun208](https://github.com/tharun208)
- **Transformations:** Support escaped characters in key-value pair parsing. [#47901](https://github.com/grafana/grafana/pull/47901), [@aangelisc](https://github.com/aangelisc)
-
-### Bug fixes
-
- **Azure Monitor:** Bug Fix for incorrect variable cascading for template variables. [#47478](https://github.com/grafana/grafana/pull/47478), [@jcolladokuri](https://github.com/jcolladokuri)
- **CloudWatch:** List all metrics properly in SQL autocomplete. [#45898](https://github.com/grafana/grafana/pull/45898), [@sunker](https://github.com/sunker)
- **CloudWatch:** Run query on blur in logs query field. [#47454](https://github.com/grafana/grafana/pull/47454), [@fridgepoet](https://github.com/fridgepoet)
- **Dashboard:** Template variables are now correctly persisted when clicking breadcrumb links. [#46790](https://github.com/grafana/grafana/pull/46790), [@ashharrison90](https://github.com/ashharrison90)
- **DashboardPage:** Remember scroll position when coming back panel edit / view panel. [#47639](https://github.com/grafana/grafana/pull/47639), [@torkelo](https://github.com/torkelo)
- **Panel Edit:** Options search now works correctly when a logarithmic scale option is set. [#47927](https://github.com/grafana/grafana/pull/47927), [@ashharrison90](https://github.com/ashharrison90)
- **Postgres:** Return tables with hyphenated schemes. [#45754](https://github.com/grafana/grafana/pull/45754), [@zuchka](https://github.com/zuchka)
- **Table panel:** Fix horizontal scrolling when pagination is enabled. [#47776](https://github.com/grafana/grafana/pull/47776), [@dprokop](https://github.com/dprokop)
- **Variables:** Ensure variables in query params are correctly recognised. [#47049](https://github.com/grafana/grafana/pull/47049), [@ashharrison90](https://github.com/ashharrison90)
- **Variables:** Fix crash when changing query variable datasource. [#44957](https://github.com/grafana/grafana/pull/44957), [@joshhunt](https://github.com/joshhunt)
- **Visualizations:** Stack negative-valued series downwards. [#47373](https://github.com/grafana/grafana/pull/47373), [@leeoniya](https://github.com/leeoniya)
-
-### Breaking changes
-
-For a proxied request, e.g. Grafana's datasource or plugin proxy:
-
- If the request is cancelled, e.g. from the browser/by the client, the HTTP status code is now `499 Client closed request` instead of `502 Bad gateway`
- If the request times out, e.g. takes longer time than allowed, the HTTP status code is now `504 Gateway timeout` instead of `502 Bad gateway`. Issue [#47473](https://github.com/grafana/grafana/issues/47473)
-
-The change in behavior is that negative-valued series are now stacked downwards from 0 (in their own stacks), rather than downwards from the top of the positive stacks. We now automatically group stacks by Draw style, Line interpolation, and Bar alignment, making it impossible to stack bars on top of lines, or smooth lines on top of stepped lines. Issue [#47373](https://github.com/grafana/grafana/issues/47373)
-
-The meaning of the default data source has now changed from being a persisted property in a panel. Before when you selected the default data source for a panel and later changed the default data source to another data source it would change all panels who were configured to use the default data source. From now on the default data source is just the default for new panels and changing the default will not impact any currently saved dashboards. Issue [#45132](https://github.com/grafana/grafana/issues/45132)
-
-The Tooltip component provided by `@grafana/ui` is no longer automatically interactive (that is you can hover onto it and click a link or select text). It will from now on by default close automatically when you mouse out from the trigger element. To make tooltips behave like before set the new `interactive` property to true.  
- Issue [#45053](https://github.com/grafana/grafana/issues/45053)
-
-### Deprecations
-
-`/api/tsdb/query` API has been deprecated and will be removed in a future release. Use [/api/ds/query](https://grafana.com/docs/grafana/latest/http_api/data_source/#query-a-data-source) instead. Issue [#45238](https://github.com/grafana/grafana/issues/45238)
-
-### Plugin development fixes & changes
-
- **Card:** Increase clickable area when meta items are present. [#47935](https://github.com/grafana/grafana/pull/47935), [@ashharrison90](https://github.com/ashharrison90)
- **Loki:** Fix operator description propup from being shortened. [#46575](https://github.com/grafana/grafana/pull/46575), [@glintik](https://github.com/glintik)
- **Tooltips:** Make tooltips non interactive by default. [#45053](https://github.com/grafana/grafana/pull/45053), [@torkelo](https://github.com/torkelo)
-
-<!-- 8.5.0 END -->
-<!-- 8.5.0-beta1 START -->
-
-# 8.5.0-beta1 (2022-04-06)
-
-### Features and enhancements
-
- Add config option to enable/disable reporting. (Enterprise)
- **Alerting:** Accurately set value for prom-compatible APIs. [#47216](https://github.com/grafana/grafana/pull/47216), [@gotjosh](https://github.com/gotjosh)
- **Alerting:** Provisioning API - Notification Policies. [#46755](https://github.com/grafana/grafana/pull/46755), [@alexweav](https://github.com/alexweav)
- **Alerting:** Notification URL points to alert view page instead of alert edit page. [#47752](https://github.com/grafana/grafana/pull/47752), [@joeblubaugh](https://github.com/joeblubaugh)
- **Analytics:** Enable grafana and plugin update checks to be operated independently. [#46352](https://github.com/grafana/grafana/pull/46352), [@wbrowne](https://github.com/wbrowne)
- **Azure Monitor:** Add support for multiple template variables in resource picker. [#46215](https://github.com/grafana/grafana/pull/46215), [@sarahzinger](https://github.com/sarahzinger)
- **Caching:** Add separate TTL for resources cache. (Enterprise)
- **Caching:** add support for TLS configuration for Redis Cluster. (Enterprise)
- **NewsPanel:** Remove Use Proxy option and update documentation with recommendations. [#47189](https://github.com/grafana/grafana/pull/47189), [@joshhunt](https://github.com/joshhunt)
- **OAuth:** Sync GitHub OAuth user name to Grafana if it's set. [#45438](https://github.com/grafana/grafana/pull/45438), [@pallxk](https://github.com/pallxk)
-
-### Bug fixes
-
- **Plugins:** Fix Default Nav URL for dashboard includes. [#47143](https://github.com/grafana/grafana/pull/47143), [@wbrowne](https://github.com/wbrowne)
-
-### Breaking changes
-
-When user is using Github OAuth, GitHub login is showed as both Grafana login and name. Now the GitHub name is showed as Grafana name, and GitHub login is showed as Grafana Login. Issue [#45438](https://github.com/grafana/grafana/issues/45438)
-
-The meaning of the default data source has now changed from being a persisted property in a panel. Before when you selected the default data source for a panel and later changed the default data source to another data source it would change all panels who were configured to use the default data source. From now on the default data source is just the default for new panels and changing the default will not impact any currently saved dashboards. Issue [#45132](https://github.com/grafana/grafana/issues/45132)
-
-<!-- 8.4.7 START -->
-
-# 8.4.7 (2022-04-19)
-
-### Features and enhancements
-
- **CloudWatch:** Added missing MemoryDB Namespace metrics. [#47290](https://github.com/grafana/grafana/pull/47290), [@james-deee](https://github.com/james-deee)
- **Histogram Panel:** Take decimal into consideration. [#47330](https://github.com/grafana/grafana/pull/47330), [@mdvictor](https://github.com/mdvictor)
- **TimeSeries:** Sort tooltip values based on raw values. [#46738](https://github.com/grafana/grafana/pull/46738), [@dprokop](https://github.com/dprokop)
-
-### Bug fixes
-
- **API:** Include userId, orgId, uname in request logging middleware. [#47183](https://github.com/grafana/grafana/pull/47183), [@marefr](https://github.com/marefr)
- **Elasticsearch:** Respect maxConcurrentShardRequests datasource setting. [#47120](https://github.com/grafana/grafana/pull/47120), [@alexandrst88](https://github.com/alexandrst88)
-
-<!-- 8.4.7 END -->
-<!-- 8.5.0-beta1 END -->
 <!-- 8.4.6 START -->

 # 8.4.6 (2022-04-12)
@@ -396,43 +168,6 @@ AngularJS plugin support is now in a deprecated state, meaning it will be remove
 - **News:** Reload feed when changing the time range or refreshing. [#42217](https://github.com/grafana/grafana/pull/42217), [@ashharrison90](https://github.com/ashharrison90)
 - **UI/Plot:** Implement keyboard controls for plot cursor. [#42244](https://github.com/grafana/grafana/pull/42244), [@kaydelaney](https://github.com/kaydelaney)

-<!-- 8.3.7 START -->
-
-# 8.3.7 (2022-03-01)
-
-### Bug fixes
-
- **Provisioning:** Ensure that the default value for orgID is set when provisioning datasources to be deleted. [#44244](https://github.com/grafana/grafana/pull/44244), [@filewalkwithme](https://github.com/filewalkwithme)
-
-<!-- 8.3.7 END -->
-
-<!-- 8.3.6 START -->
-
-# 8.3.6 (2022-02-09)
-
-### Features and enhancements
-
- **Cloud Monitoring:** Reduce request size when listing labels. [#44365](https://github.com/grafana/grafana/pull/44365), [@mtanda](https://github.com/mtanda)
- **Explore:** Show scalar data result in a table instead of graph. [#44362](https://github.com/grafana/grafana/pull/44362), [@tharun208](https://github.com/tharun208)
- **Snapshots:** Updates the default external snapshot server URL. [#44563](https://github.com/grafana/grafana/pull/44563), [@DanCech](https://github.com/DanCech)
- **Table:** Makes footer not overlap table content. [#44210](https://github.com/grafana/grafana/pull/44210), [@dprokop](https://github.com/dprokop)
- **Tempo:** Add request histogram to service graph datalink. [#44671](https://github.com/grafana/grafana/pull/44671), [@connorlindsey](https://github.com/connorlindsey)
- **Tempo:** Add time range to tempo search query behind a feature flag. [#43811](https://github.com/grafana/grafana/pull/43811), [@connorlindsey](https://github.com/connorlindsey)
- **Tempo:** Auto-clear results when changing query type. [#44390](https://github.com/grafana/grafana/pull/44390), [@connorlindsey](https://github.com/connorlindsey)
- **Tempo:** Display start time in search results as relative time. [#44568](https://github.com/grafana/grafana/pull/44568), [@tharun208](https://github.com/tharun208)
-
-### Bug fixes
-
- **CloudMonitoring:** Fix resource labels in query editor. [#44550](https://github.com/grafana/grafana/pull/44550), [@iwysiu](https://github.com/iwysiu)
- **Cursor sync:** Apply the settings without saving the dashboard. [#44270](https://github.com/grafana/grafana/pull/44270), [@dprokop](https://github.com/dprokop)
- **LibraryPanels:** Fix for Error while cleaning library panels. [#45033](https://github.com/grafana/grafana/pull/45033), [@hugohaggmark](https://github.com/hugohaggmark)
- **Logs Panel:** fix timestamp parsing for string dates without timezone. [#44664](https://github.com/grafana/grafana/pull/44664), [@Elfo404](https://github.com/Elfo404)
- **Prometheus:** Fix some of the alerting queries that use reduce/math operation. [#44380](https://github.com/grafana/grafana/pull/44380), [@ivanahuckova](https://github.com/ivanahuckova)
- **TablePanel:** Fix ad-hoc variables not working on default datasources. [#44314](https://github.com/grafana/grafana/pull/44314), [@joshhunt](https://github.com/joshhunt)
- **Text Panel:** Fix alignment of elements. [#44313](https://github.com/grafana/grafana/pull/44313), [@ashharrison90](https://github.com/ashharrison90)
- **Variables:** Fix for constant variables in self referencing links. [#44631](https://github.com/grafana/grafana/pull/44631), [@hugohaggmark](https://github.com/hugohaggmark)
-
-<!-- 8.3.6 END -->
 <!-- 8.4.0-beta1 END -->
 <!-- 8.3.5 START -->

--- a/2
+++ b/2
@@ -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.8-alpine3.15 as go-builder

 RUN apk add --no-cache gcc g++ make

--- 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.8 AS go-builder

 WORKDIR /src/grafana

--- a/GOVERNANCE.md
+++ b/GOVERNANCE.md
@@ -100,7 +100,7 @@ The current team members are:
 - Ryan McKinley ([Grafana Labs](https://grafana.com/))
 - Sofia Papagiannaki ([Grafana Labs](https://grafana.com/))
 - Stephanie Closson ([Grafana Labs](https://grafana.com/))
- Tobias Skarhed ([CERN](https://home.web.cern.ch/))
+- Tobias Skarhed ([Grafana Labs](https://grafana.com/))
 - Torkel Ödegaard ([Grafana Labs](https://grafana.com/))
 - Utkarsh Bhatnagar ([Tinder](https://www.tinder.com/))
 - Will Browne ([Grafana Labs](https://grafana.com/))
--- a/ISSUE_TRIAGE.md
+++ b/ISSUE_TRIAGE.md
@@ -77,11 +77,11 @@ Instructions for setting up filters in Gmail can be found [here](#setting-up-gma

 ## 2. Ensure the issue contains basic information

-Before triaging an issue very far, make sure that the issue's author provided the standard issue information. This will help you make an educated recommendation on how to categorize the issue. The Grafana project utilizes [GitHub issue templates](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository) to guide contributors to provide standard information that must be included for each type of template or type of issue.
+Before triaging an issue very far, make sure that the issue's author provided the standard issue information. This will help you make an educated recommendation on how to categorize the issue. The Grafana project utilizes [GitHub issue templates](https://help.github.com/en/articles/creating-issue-templates-for-your-repository) to guide contributors to provide standard information that must be included for each type of template or type of issue.

 ### Standard issue information that must be included

-Given a certain [issue template](https://github.com/grafana/grafana/issues/new/choose) have been used by the issue author or depending how the issue is perceived by the issue triage responsible, the following should help you understand what standard issue information that must be included.
+Given a certain [issue template](<[template](https://github.com/grafana/grafana/issues/new/choose)>) have been used by the issue author or depending how the issue is perceived by the issue triage responsible, the following should help you understand what standard issue information that must be included.

 #### Bug reports

@@ -192,7 +192,7 @@ First, evaluate if the documentation makes sense to be included in the Grafana p

 - Is this something we want/can maintain as a project?
 - Is this referring to usage of some specific integration/tool and in that case is that a popular use case in combination with Grafana?
- If unsure, kindly and politely add a comment explaining that we would need [upvotes](https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments) to identify that lots of other users want/need this.
+- If unsure, kindly and politely add a comment explaining that we would need [upvotes](https://help.github.com/en/articles/about-conversations-on-github#reacting-to-ideas-in-comments) to identify that lots of other users want/need this.

 Second, label the issue `type/docs` and at least one `area/*` or `datasource/*` label.

@@ -296,13 +296,13 @@ In many cases the issue author or community as a whole is more suitable to contr

 ## Investigation of issues

-When an issue has all basic information provided, but the triage responsible haven't been able to reproduce the reported problem at a first glance, the issue is labeled [Needs investigation](https://github.com/grafana/grafana/labels/needs%20investigation). Depending on the perceived severity and/or number of [upvotes](https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments), the investigation will either be delegated to another maintainer for further investigation or put on hold until someone else (maintainer or contributor) picks it up and eventually starts investigating it.
+When an issue has all basic information provided, but the triage responsible haven't been able to reproduce the reported problem at a first glance, the issue is labeled [Needs investigation](https://github.com/grafana/grafana/labels/needs%20investigation). Depending on the perceived severity and/or number of [upvotes](https://help.github.com/en/articles/about-conversations-on-github#reacting-to-ideas-in-comments), the investigation will either be delegated to another maintainer for further investigation or put on hold until someone else (maintainer or contributor) picks it up and eventually starts investigating it.

 Investigating issues can be a very time consuming task, especially for the maintainers, given the huge number of combinations of plugins, data sources, platforms, databases, browsers, tools, hardware, integrations, versions and cloud services, etc that are being used with Grafana. There is a certain number of combinations that are more common than others, and these are in general easier for maintainers to investigate.

 For some other combinations it may not be possible at all for a maintainer to setup a proper test environment to investigate the issue. In these cases we really appreciate any help we can get from the community. Otherwise the issue is highly likely to be closed.

-Even if you don't have the time or knowledge to investigate an issue we highly recommend that you [upvote](https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments) the issue if you happen to have the same problem. If you have further details that may help investigating the issue please provide as much information as possible.
+Even if you don't have the time or knowledge to investigate an issue we highly recommend that you [upvote](https://help.github.com/en/articles/about-conversations-on-github#reacting-to-ideas-in-comments) the issue if you happen to have the same problem. If you have further details that may help investigating the issue please provide as much information as possible.

 ## Automation

--- a/README.md
+++ b/README.md
@@ -1,14 +1,14 @@
 ![Grafana](docs/logo-horizontal.png)

-The open-source platform for monitoring and observability
+The open-source platform for monitoring and observability.

 [![License](https://img.shields.io/github/license/grafana/grafana)](LICENSE)
 [![Drone](https://drone.grafana.net/api/badges/grafana/grafana/status.svg)](https://drone.grafana.net/grafana/grafana)
 [![Go Report Card](https://goreportcard.com/badge/github.com/grafana/grafana)](https://goreportcard.com/report/github.com/grafana/grafana)

-Grafana allows you to query, visualize, alert on and understand your metrics no matter where they are stored. Create, explore, and share dashboards with your team and foster a data-driven culture:
+Grafana allows you to query, visualize, alert on and understand your metrics no matter where they are stored. Create, explore, and share dashboards with your team and foster a data driven culture:

- **Visualizations:** Fast and flexible client side graphs with a multitude of options. Panel plugins offer many different ways to visualize metrics and logs.
+- **Visualize:** Fast and flexible client side graphs with a multitude of options. Panel plugins offer many different ways to visualize metrics and logs.
 - **Dynamic Dashboards:** Create dynamic & reusable dashboards with template variables that appear as dropdowns at the top of the dashboard.
 - **Explore Metrics:** Explore your data through ad-hoc queries and dynamic drilldown. Split view and compare different time ranges, queries and data sources side by side.
 - **Explore Logs:** Experience the magic of switching from metrics to logs with preserved label filters. Quickly search through all your logs or streaming them live.
--- a/UPGRADING_DEPENDENCIES.md
+++ b/UPGRADING_DEPENDENCIES.md
@@ -15,7 +15,6 @@ Upgrading Go or Node.js requires making changes in many different files. See bel
 - `grafana/build-container`
 - Appveyor
 - Dockerfile
- `.github/workflows/publish.yml`

 ## Go dependencies

--- a/conf/defaults.ini
+++ b/conf/defaults.ini
@@ -9,9 +9,6 @@ app_mode = production
 # instance name, defaults to HOSTNAME environment variable value or hostname if HOSTNAME var is empty
 instance_name = ${HOSTNAME}

-# force migration will run migrations that might cause dataloss
-force_migration = false
-
 #################################### Paths ###############################
 [paths]
 # Path to where grafana can store temp files, sessions, and the sqlite3 db (if that is used)
@@ -196,19 +193,12 @@ reporting_enabled = true
 reporting_distributor = grafana-labs

 # Set to false to disable all checks to https://grafana.com
-# for new versions of grafana. The check is used
-# in some UI views to notify that a grafana update exists.
+# for new versions (grafana itself and plugins), check is used
+# in some UI views to notify that grafana or plugin update exists
 # This option does not cause any auto updates, nor send any information
-# only a GET request to https://raw.githubusercontent.com/grafana/grafana/main/latest.json to get the latest version.
+# only a GET request to https://grafana.com to get latest versions
 check_for_updates = true

-# Set to false to disable all checks to https://grafana.com
-# for new versions of plugins. The check is used
-# in some UI views to notify that a plugin update exists.
-# This option does not cause any auto updates, nor send any information
-# only a GET request to https://grafana.com to get the latest versions.
-check_for_plugin_updates = true
-
 # Google Analytics universal tracking code, only enabled if you specify an id here
 google_analytics_ua_id =

@@ -233,9 +223,6 @@ application_insights_connection_string =
 # Optional. Specifies an Application Insights endpoint URL where the endpoint string is wrapped in backticks ``.
 application_insights_endpoint_url =

-# Controls if the UI contains any links to user feedback forms
-feedback_links_enabled = true
-
 #################################### Security ############################
 [security]
 # disable creation of admin user on first start of grafana
@@ -305,18 +292,6 @@ content_security_policy = false
 # $ROOT_PATH is server.root_url without the protocol.
 content_security_policy_template = """script-src 'self' 'unsafe-eval' 'unsafe-inline' 'strict-dynamic' $NONCE;object-src 'none';font-src 'self';style-src 'self' 'unsafe-inline' blob:;img-src * data:;base-uri 'self';connect-src 'self' grafana.com ws://$ROOT_PATH wss://$ROOT_PATH;manifest-src 'self';media-src 'none';form-action 'self';"""

-# Controls if old angular plugins are supported or not. This will be disabled by default in future release
-angular_support_enabled = true
-
-[security.encryption]
-# Defines the time-to-live (TTL) for decrypted data encryption keys stored in memory (cache).
-# Please note that small values may cause performance issues due to a high frequency decryption operations.
-data_keys_cache_ttl = 15m
-
-# Defines the frequency of data encryption keys cache cleanup interval.
-# On every interval, decrypted data encryption keys that reached the TTL are removed from the cache.
-data_keys_cache_cleanup_interval = 1m
-
 #################################### Snapshots ###########################
 [snapshots]
 # snapshot sharing options
@@ -521,7 +496,6 @@ auth_url = https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/authorize
 token_url = https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/token
 allowed_domains =
 allowed_groups =
-role_attribute_strict = false

 #################################### Okta OAuth #######################
 [auth.okta]
@@ -903,16 +877,6 @@ max_annotations_to_keep =
 # Enable the Explore section
 enabled = true

-#################################### Help #############################
-[help]
-# Enable the Help section
-enabled = true
-
-#################################### Profile #############################
-[profile]
-# Enable the Profile section
-enabled = true
-
 #################################### Query History #############################
 [query_history]
 # Enable the Query history
@@ -1137,12 +1101,6 @@ license_path =
 # enable = feature1,feature2
 enable =

-# The new prometheus visual query builder
-promQueryBuilder = true
-
-# Experimental Explore to Dashboard workflow
-explore2Dashboard = true
-
 # feature1 = true
 # feature2 = false

--- a/conf/sample.ini
+++ b/conf/sample.ini
@@ -9,9 +9,6 @@
 # instance name, defaults to HOSTNAME environment variable value or hostname if HOSTNAME var is empty
 ;instance_name = ${HOSTNAME}

-# force migration will run migrations that might cause dataloss
-;force_migration = false
-
 #################################### Paths ####################################
 [paths]
 # Path to where grafana can store temp files, sessions, and the sqlite3 db (if that is used)
@@ -201,20 +198,13 @@
 # The name of the distributor of the Grafana instance. Ex hosted-grafana, grafana-labs
 ;reporting_distributor = grafana-labs

-# Set to false to disable all checks to https://grafana.com
-# for new versions of grafana. The check is used
-# in some UI views to notify that a grafana update exists.
+# Set to false to disable all checks to https://grafana.net
+# for new versions (grafana itself and plugins), check is used
+# in some UI views to notify that grafana or plugin update exists
 # This option does not cause any auto updates, nor send any information
-# only a GET request to https://raw.githubusercontent.com/grafana/grafana/main/latest.json to get the latest version.
+# only a GET request to http://grafana.com to get latest versions
 ;check_for_updates = true

-# Set to false to disable all checks to https://grafana.com
-# for new versions of plugins. The check is used
-# in some UI views to notify that a plugin update exists.
-# This option does not cause any auto updates, nor send any information
-# only a GET request to https://grafana.com to get the latest versions.
-;check_for_plugin_updates = true
-
 # Google Analytics universal tracking code, only enabled if you specify an id here
 ;google_analytics_ua_id =

@@ -233,9 +223,6 @@
 # Rudderstack Config url, optional, used by Rudderstack SDK to fetch source config
 ;rudderstack_config_url =

-# Controls if the UI contains any links to user feedback forms
-;feedback_links_enabled = true
-
 #################################### Security ####################################
 [security]
 # disable creation of admin user on first start of grafana
@@ -305,18 +292,6 @@
 # $ROOT_PATH is server.root_url without the protocol.
 ;content_security_policy_template = """script-src 'self' 'unsafe-eval' 'unsafe-inline' 'strict-dynamic' $NONCE;object-src 'none';font-src 'self';style-src 'self' 'unsafe-inline' blob:;img-src * data:;base-uri 'self';connect-src 'self' grafana.com ws://$ROOT_PATH wss://$ROOT_PATH;manifest-src 'self';media-src 'none';form-action 'self';"""

-# Controls if old angular plugins are supported or not. This will be disabled by default in future release
-;angular_support_enabled = true
-
-[security.encryption]
-# Defines the time-to-live (TTL) for decrypted data encryption keys stored in memory (cache).
-# Please note that small values may cause performance issues due to a high frequency decryption operations.
-;data_keys_cache_ttl = 15m
-
-# Defines the frequency of data encryption keys cache cleanup interval.
-# On every interval, decrypted data encryption keys that reached the TTL are removed from the cache.
-;data_keys_cache_cleanup_interval = 1m
-
 #################################### Snapshots ###########################
 [snapshots]
 # snapshot sharing options
@@ -506,7 +481,6 @@
 ;token_url = https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/token
 ;allowed_domains =
 ;allowed_groups =
-;role_attribute_strict = false

 #################################### Okta OAuth #######################
 [auth.okta]
@@ -885,16 +859,6 @@
 # Enable the Explore section
 ;enabled = true

-#################################### Help #############################
-[help]
-# Enable the Help section
-;enabled = true
-
-#################################### Profile #############################
-[profile]
-# Enable the Profile section
-;enabled = true
-
 #################################### Query History #############################
 [query_history]
 # Enable the Query history
--- a/contribute/architecture/backend/communication.md
+++ b/contribute/architecture/backend/communication.md
@@ -2,8 +2,6 @@

 Grafana uses a _bus_ to pass messages between different parts of the application. All communication over the bus happens synchronously.

-> **Deprecated:** The bus has officially been deprecated, however, we're still using the command/query objects paradigms.
-
 There are three types of messages: _events_, _commands_, and _queries_.

 ## Events
--- a/contribute/architecture/backend/database.md
+++ b/contribute/architecture/backend/database.md
@@ -99,8 +99,6 @@ To add a migration:
 - In the `AddMigrations` function, find the `addXxxMigration` function for the service you want to create a migration for.
 - At the end of the `addXxxMigration` function, register your migration:

-> **NOTE:** Putting migrations behind feature flags is no longer recommended as it may cause the migration skip integration testing.
-
 [Example](https://github.com/grafana/grafana/blob/00d0640b6e778ddaca021670fe851fe00982acf2/pkg/services/sqlstore/migrations/migrations.go#L55-L70)

 ### Implement `DatabaseMigrator`
--- a/contribute/breaking-changes-comment-screenshot.png
+++ b/contribute/breaking-changes-comment-screenshot.png
--- a/contribute/breaking-changes-console-screenshot-1.png
+++ b/contribute/breaking-changes-console-screenshot-1.png
--- a/contribute/breaking-changes-console-screenshot-2.png
+++ b/contribute/breaking-changes-console-screenshot-2.png
--- a/contribute/breaking-changes-console-screenshot-3.png
+++ b/contribute/breaking-changes-console-screenshot-3.png
--- a/contribute/breaking-changes-guide.md
+++ b/contribute/breaking-changes-guide.md
@@ -1,119 +0,0 @@
-# Handling breaking changes in Grafana frontend APIs
-
-This guide tries to help you identify and communicate breaking changes introduced to our frontend API.
-
- [What are our public APIs?](#what-are-our-public-apis)
- [What is Levitate?](#what-is-levitate)
- [How does the CI workflow look like?](#how-does-the-ci-workflow-look-like)
- [I received a comment on my PR, what does it mean?](#i-received-a-comment-on-my-pr-what-does-it-mean)
- [**I know it's a breaking change, what's next?**](#i-know-its-a-breaking-change-whats-next)
-  - [Introduce breaking changes only in major versions](#introduce-breaking-changes-only-in-major-versions)
-  - [Deprecate first](#deprecate-first)
-  - [Communicate](#communicate)
- [I still have questions, who can help me out?](#i-still-have-questions-who-can-help-me-out)
-
---
-
-## What are our public APIs?
-
-The Grafana frontend codebase is exposing functionality through NPM packages to make plugin development easier and faster.
-These packages live in the `/packages` folder and contain packages like:
-
- `@grafana/data`
- `@grafana/runtime`
- `@grafana/toolkit`
- `@grafana/ui`
- etc. ([They can be viewed here](https://github.com/grafana/grafana/tree/main/packages)
-
-Any change that causes dependent software to behave differently is considered to be breaking.
-
-## What is Levitate?
-
-[`@grafana/levitate`](https://github.com/grafana/levitate) is a tool created by Grafana that can show breaking changes between two versions of a **TypeScript** package or a source file.
-
-It can list exported members of an NPM package or imports used by an NPM package,
-**but we are mainly using it for comparing different versions of the same package to see changes in the exported members.**
-
-A Github workflow runs against every pull request and comments a hint in case there are
-possible breaking changes. It also adds the `"breaking change"` label to the pull request.
-
-## How does the CI workflow look like?
-
-<img src="./breaking-changes-workflow.png" alt="CI workflow" width="700" />
-
-## I received a comment on my PR, what does it mean?
-
-![Levitate comment](./breaking-changes-comment-screenshot.png)
-
-Receiving a comment like the one above does not necessarily mean that you actually introduced breaking
-changes (as certain edge cases are still not covered by the tool), but as there is a good chance we rather raise attention.
-
-By clicking the links in the comment ("more info" or "Check console output") you can view more detailed information about what triggered the notification.
-
-**Removed exported members** (console view):<br />
-This means that some previously exported members won't be available in the newer version of the package which can break dependent plugins.
-
-![](./breaking-changes-console-screenshot-1.png)
-
-**Changed an existing member** (console view):<br />
-This means that a member was changed in a way that can break dependent plugins.
-
-![](./breaking-changes-console-screenshot-2.png)
-
-**No breaking changes** (console view):<br />
-Seeing this suggests that whilst changes were made, most probably none of them were breaking. You are good to go! 👏
-
-![](./breaking-changes-console-screenshot-3.png)
-
-## How can I decide if it is really a breaking change?
-
-First go to the console output of the workflow and make sure that the diffs make sense.
-
-It can happen that Levitate highlights a change which is marked with TSDoc tags `// @alpha` or `// @internal` in
-which case you can choose to ignore it - keep in mind though that these flags won't really hold developers back
-from using your code and most likely it is going to cause them problems if we are breaking them.
-
-It can also happen that Levitate marks changing an interface as a possible breaking change.
-For anyone that implements that interface introducing a new property will break their code. Whilst this is correctly marked as a breaking change maybe it is an interface that is never implemented by other developers. In which case you can choose to ignore Levitate's message.
-
-These notifications are only warnings though, and **in the end it's up to the author of the PR to make a decision that makes the most sense.**
-
-## I know it's a breaking change, what's next?
-
-### Introduce breaking changes only in major versions
-
-We can make breaking changes less painful if they are only happening between major releases of Grafana.
-
-### Deprecate first
-
-Whenever possible try to deprecate first what you are about to remove or change. For example:
-
-```javascript
-import { deprecationWarning } from '@grafana/data';
-
-/**
- * @deprecated -- this is no longer necessary and will be removed in Grafana 9.0.0
- */
-myOldFunction(name: string) {
-    deprecationWarning('MyFile', 'myOldFunction', 'myNewFunction');
-    // ...
-}
-```
-
-1. Add a deprecation comment `// @deprecated`
-2. Add info in the comment about **when it is going to be removed**
-3. Add info in the comment about **what should be used instead**
-4. In case it's a function or a method, use `deprecationWarning(<file name>, <old name>, <new name>)` to raise attention during runtime as well
-5. Update the [migration guide](../docs/sources/developers/plugins/migration-guide.md) with your instructions
-
-### Communicate
-
-Reach out to **@grafana/plugins-platform-frontend** to help finding which plugins are using the code that is just about to change, so we try making it smoother by communicating it to them.
-
---
-
-## I still have questions, who can help me out?
-
-We are here to help.
-
-Please either ping us in the pull request by using the **@grafana/plugins-platform-frontend** handle or reach out to us on the internal Slack in `#grafana-plugins-platform`.
--- a/contribute/breaking-changes-workflow.png
+++ b/contribute/breaking-changes-workflow.png
--- a/contribute/developer-guide.md
+++ b/contribute/developer-guide.md
@@ -136,20 +136,6 @@ Running the backend tests on Windows currently needs some tweaking, so use the b
 go run build.go test
 ```

-### Run PostgreSQL and MySQL integration tests
-
-To run PostgreSQL and MySQL integration tests locally, you need to start the docker blocks for MySQL and/or PostgreSQL test data sources by running `make devenv sources=mysql_tests,postgres_tests`. When your test data sources are running, you can execute integration tests by running:
-
-```
-GRAFANA_TEST_DB=mysql go test -covermode=atomic -tags=integration ./pkg/...
-```
-
-and/or
-
-```
-GRAFANA_TEST_DB=postgres go test -covermode=atomic -tags=integration ./pkg/...
-```
-
 ### Run end-to-end tests

 The end to end tests in Grafana use [Cypress](https://www.cypress.io/) to run automated scripts in a headless Chromium browser. Read more about our [e2e framework](/contribute/style-guides/e2e.md).
--- a/contribute/documentation/README.md
+++ b/contribute/documentation/README.md
@@ -212,10 +212,10 @@ of the sentence. When you write in passive voice, the recipient of the action (a
 Active-voice sentences are more direct and clearly identify _who_ is doing _what_. Not all tasks are completed by a user; sometimes the system can also be a performer (and by extension, the subject of the sentence). When you write in active voice you clearly make that distinction, which results in more engaging and less wordy content.

 | Use (active)                                          | Avoid (passive)                                                      |
-| ----------------------------------------------------- | -------------------------------------------------------------------- |
+| ----------------------------------------------------- | -------------------------------------------------------------------- | --- |
 | After you upgrade the software, restart the computer. | After the software has been upgraded, the computer can be restarted. |
 | Click **OK** to save the dashboard.                   | The dashboard is saved when the **OK** button is clicked.            |
-| Create a dashboard.                                   | A dashboard is created by you.                                       |
+| Create a dashboard.                                   | A dashboard is created by you.                                       | .   |

 ### Avoid obscure non-English words and abbreviations

--- a/contribute/merge-pull-request.md
+++ b/contribute/merge-pull-request.md
@@ -93,7 +93,7 @@ If you don't want to backport you need to add a label named **no-backport** to t

 #### Backport

-If your pull request has changes that need to go into one or several existing release branches you need to backport the changes. Please refer to [Backport PR](/.github/bot.md#backport-pr) for detailed instructions.
+If your pull request has changes that need to go into one or several existing release branches you need to backport the changes. Please refer to [Backport PR](.github/bot.md#backport-pr) for detailed instructions.

 The general rule of thumb regarding what changes goes into what release is:

--- a/contribute/style-guides/backend.md
+++ b/contribute/style-guides/backend.md
@@ -58,100 +58,6 @@ code, plus lets you run each test case in isolation when debugging. Don't use `t
 Use [`t.Cleanup`](https://golang.org/pkg/testing/#T.Cleanup) to clean up resources in tests. It's a less fragile choice than `defer`, since it's independent of which
 function you call it in. It will always execute after the test is over in reverse call order (last `t.Cleanup` first, same as `defer`).

-### Mock
-
-Optionally, we use [`mock.Mock`](https://github.com/stretchr/testify#mock-package) package to generate mocks. This is
-useful when you expect different behaviours of the same function.
-
-#### Tips
-
- Use `Once()` or `Times(n)` to make this mock only works `n` times.
- Use `mockedClass.AssertExpectations(t)` to guarantee that the mock is called the times asked.
-  - If any mock set is not called or its expects more calls, the test fails.
- You can pass `mock.Anything` as argument if you don't care about the argument passed.
- Use `mockedClass.AssertNotCalled(t, "FunctionName")` to assert that this test is not called.
-
-#### Example
-
-This is an example to easily create a mock of an interface.
-
-Given this interface:
-
-```go
-func MyInterface interface {
-    Get(ctx context.Context, id string) (Object, error)
-}
-```
-
-Mock implementation should be like this:
-
-```go
-import
-
-func MockImplementation struct {
-    mock.Mock
-}
-
-func (m *MockImplementation) Get(ctx context.Context, id string) error {
-    args := m.Called(ctx, id) // Pass all arguments in order here
-    return args.Get(0).(Object), args.Error(1)
-}
-```
-
-And use it as the following way:
-
-```go
-
-objectToReturn := Object{Message: "abc"}
-errToReturn := errors.New("my error")
-
-myMock := &MockImplementation{}
-defer myMock.AssertExpectations(t)
-
-myMock.On("Get", mock.Anything, "id1").Return(objectToReturn, errToReturn).Once()
-myMock.On("Get", mock.Anything, "id2").Return(Object{}, nil).Once()
-
-anyService := NewService(myMock)
-resp, err := anyService.Call("id1")
-
-assert.Equal(t, resp.Message, objectToReturn.Message)
-assert.Error(t, err, errToReturn)
-
-resp, err = anyService.Call("id2")
-assert.Nil(t, err)
-```
-
-#### Mockery
-
-When an interface to test is too big, it's annoying to mock each function manually. To avoid this, you can
-use [`mockery`](https://github.com/vektra/mockery) library to generate the mocks.
-
-The command is like the following (there are more options documented if you need to use another one):
-
-```
-mockery --name InterfaceName --structname MockImplementationName --inpackage --filename my_implementation_mock.go
-```
-
- `--name`: Interface to mock
- `--structname`: Mock implementation name
- `--inpackage`: To use the same package name as the interface
- `--filename`: Your mock generated file name
-
-If any interface signature changes, executing the command again updates the mock.
-
-Additionally, you can put `go:generate` command on the top of the file as a comment. It's useful because some IDEs
-like Goland and Visual Studio Code allows executing scripts from the IDE.
-
-```
-package <package>
-
-import (
-	...
-)
-
-//go:generate mockery --name InterfaceName --structname MockImplementationName --inpackage --filename my_implementation_mock.go
-```
-
 ## Globals

 As a general rule of thumb, avoid using global variables, since they make the code difficult to maintain and reason
--- a/devenv/datasources.yaml
+++ b/devenv/datasources.yaml
@@ -195,7 +195,7 @@ datasources:
      timeInterval: 10s
      interval: Daily
      timeField: "@timestamp"
-      esVersion: 7.10.0
+      esVersion: 70

  - name: gdev-elasticsearch-v7-logs
    type: elasticsearch
@@ -205,7 +205,7 @@ datasources:
    jsonData:
      interval: Daily
      timeField: "@timestamp"
-      esVersion: 7.10.0
+      esVersion: 70

  - name: gdev-elasticsearch-v7-filebeat
    type: elasticsearch
@@ -215,7 +215,7 @@ datasources:
    jsonData:
      interval: Daily
      timeField: "@timestamp"
-      esVersion: 7.10.0
+      esVersion: 70
      timeInterval: "10s"
      logMessageField: message
      logLevelField: fields.level
@@ -228,7 +228,7 @@ datasources:
    jsonData:
      interval: Daily
      timeField: "@timestamp"
-      esVersion: 7.10.0
+      esVersion: 70
      timeInterval: "10s"

  - name: gdev-mysql
--- a/devenv/dev-dashboards/feature-templating/templating-dashboard-links-and-variables.json
+++ b/devenv/dev-dashboards/feature-templating/templating-dashboard-links-and-variables.json
@@ -16,7 +16,7 @@
  "gnetId": null,
  "graphTooltip": 0,
  "id": null,
-  "iteration": 1601526910610,
+  "iteration": 1646409057541,
  "links": [
    {
      "icon": "external link",
@@ -73,6 +73,61 @@
      "timeShift": null,
      "title": "${custom.text}",
      "type": "text"
+    },
+    {
+      "id": 4,
+      "gridPos": {
+        "h": 9,
+        "w": 9,
+        "x": 12,
+        "y": 0
+      },
+      "type": "stat",
+      "title": "Panel Title",
+      "fieldConfig": {
+        "defaults": {
+          "mappings": [],
+          "thresholds": {
+            "mode": "absolute",
+            "steps": [
+              {
+                "color": "green",
+                "value": null
+              },
+              {
+                "color": "red",
+                "value": 80
+              }
+            ]
+          },
+          "color": {
+            "mode": "thresholds"
+          },
+          "links": [
+            {
+              "title": "Var Link",
+              "url": "/d/vmie2cmWz/bar-gauge-demo?var-custom=$custom"
+            }
+          ]
+        },
+        "overrides": []
+      },
+      "options": {
+        "reduceOptions": {
+          "values": false,
+          "calcs": [
+            "lastNotNull"
+          ],
+          "fields": ""
+        },
+        "orientation": "auto",
+        "textMode": "auto",
+        "colorMode": "value",
+        "graphMode": "area",
+        "justifyMode": "auto"
+      },
+      "pluginVersion": "8.5.0-pre",
+      "datasource": null
    }
  ],
  "schemaVersion": 26,
@@ -112,6 +167,11 @@
            "selected": false,
            "text": "p3",
            "value": "p3"
+          },
+          {
+            "selected": false,
+            "text": "p4",
+            "value": "test%25value"
          }
        ],
        "query": "p1,p2,p3",
--- a/devenv/dev-dashboards/feature-templating/testdata-test-variable-output.json
+++ b/devenv/dev-dashboards/feature-templating/testdata-test-variable-output.json
@@ -1,76 +0,0 @@
-{
-  "__inputs": [],
-  "__elements": [],
-  "__requires": [
-    {
-      "type": "grafana",
-      "id": "grafana",
-      "name": "Grafana",
-      "version": "8.4.0-pre"
-    },
-    {
-      "type": "panel",
-      "id": "text",
-      "name": "Text",
-      "version": ""
-    }
-  ],
-  "annotations": {
-    "list": [
-      {
-        "builtIn": 1,
-        "datasource": "-- Grafana --",
-        "enable": true,
-        "hide": true,
-        "iconColor": "rgba(0, 211, 255, 1)",
-        "name": "Annotations & Alerts",
-        "target": {
-          "limit": 100,
-          "matchAny": false,
-          "tags": [],
-          "type": "dashboard"
-        },
-        "type": "dashboard"
-      }
-    ]
-  },
-  "editable": true,
-  "fiscalYearStartMonth": 0,
-  "graphTooltip": 0,
-  "links": [],
-  "liveNow": false,
-  "panels": [
-    {
-      "gridPos": {
-        "h": 9,
-        "w": 12,
-        "x": 0,
-        "y": 0
-      },
-      "id": 2,
-      "options": {
-        "mode": "markdown",
-        "content": "VariableUnderTest: $VariableUnderTest"
-      },
-      "pluginVersion": "8.4.0-pre",
-      "title": "Panel Title",
-      "type": "text"
-    }
-  ],
-  "schemaVersion": 35,
-  "style": "dark",
-  "tags": [],
-  "templating": {
-    "list": []
-  },
-  "time": {
-    "from": "now-6h",
-    "to": "now"
-  },
-  "timepicker": {},
-  "timezone": "",
-  "title": "Test variable output",
-  "uid": "kVi2Gex7z",
-  "version": 2,
-  "weekStart": ""
-}
--- a/devenv/dev-dashboards/panel-graph/graph-ng-nulls.json
+++ b/devenv/dev-dashboards/panel-graph/graph-ng-nulls.json
@@ -1042,10 +1042,6 @@
      "type": "timeseries"
    },
    {
-      "datasource": {
-        "type": "testdata",
-        "uid": "PD8C576611E62080A"
-      },
      "fieldConfig": {
        "defaults": {
          "color": {
@@ -1147,10 +1143,6 @@
      "type": "timeseries"
    },
    {
-      "datasource": {
-        "type": "testdata",
-        "uid": "PD8C576611E62080A"
-      },
      "fieldConfig": {
        "defaults": {
          "color": {
@@ -1230,95 +1222,6 @@
      ],
      "title": "Always show points between gaps",
      "type": "timeseries"
-    },
-    {
-      "datasource": {
-        "type": "testdata",
-        "uid": "PD8C576611E62080A"
-      },
-      "fieldConfig": {
-        "defaults": {
-          "color": {
-            "mode": "palette-classic"
-          },
-          "custom": {
-            "axisLabel": "",
-            "axisPlacement": "auto",
-            "barAlignment": 0,
-            "drawStyle": "line",
-            "fillOpacity": 0,
-            "gradientMode": "none",
-            "hideFrom": {
-              "legend": false,
-              "tooltip": false,
-              "viz": false
-            },
-            "lineInterpolation": "linear",
-            "lineStyle": {
-              "fill": "solid"
-            },
-            "lineWidth": 1,
-            "pointSize": 5,
-            "scaleDistribution": {
-              "type": "linear"
-            },
-            "showPoints": "never",
-            "spanNulls": false,
-            "stacking": {
-              "group": "A",
-              "mode": "none"
-            },
-            "thresholdsStyle": {
-              "mode": "off"
-            }
-          },
-          "mappings": [],
-          "thresholds": {
-            "mode": "absolute",
-            "steps": [
-              {
-                "color": "green"
-              },
-              {
-                "color": "red",
-                "value": 80
-              }
-            ]
-          }
-        },
-        "overrides": []
-      },
-      "gridPos": {
-        "h": 8,
-        "w": 7,
-        "x": 7,
-        "y": 22
-      },
-      "id": 16,
-      "options": {
-        "legend": {
-          "calcs": [],
-          "displayMode": "list",
-          "placement": "bottom"
-        },
-        "tooltip": {
-          "mode": "single",
-          "sort": "none"
-        }
-      },
-      "targets": [
-        {
-          "datasource": {
-            "type": "testdata",
-            "uid": "PD8C576611E62080A"
-          },
-          "refId": "A",
-          "scenarioId": "csv_metric_values",
-          "stringInput": ",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,60,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,61,,,,,,60,,,,,,,,,,,,,,,,,,61,,,,,,60,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,61,,,,,,60,,,,,,59,,,,,,60,,,,,,,59,,,,,,,,,,,,,,,,,,,,,,,,58,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,57,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,56,,,,,,57,,,,,,56,,,,,,57,,,,,,,,,,,,56,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,55,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,56,,,,,55,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,54,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,53,,,,,54,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,55,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,56,,,,,,,,,,,,,,,,,,55,,,,,,56,,,,,,,,,,,,57,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,56,,,,,,57,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,56,,,,,,,,,,,,57,,,,,,,58,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,57,,,,,,,,,,,,,,,,,,,58,,,,,,59,,,,,,58,,,,,,,,,,,,,,,,,,,,,,,,57,,,,,,58,,,,,,,,,,,,,,,,,,,59,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,60,,,,,,,,,,,,61,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,62,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,61,,,,,,,,,,,,,,,,,,60,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,59,,,,,,60,,,,,,59,,,,,,60,,,,,,,,,,,,,,,,,,,,,,,,,59,,,,,,,,,,,,,,,,,60,,,,,,,,,,,,,59,,,,,,60,,,,,,,,,,,,59,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,58,,,,,,59,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,58,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,57,,,,,,58,,,,,,57,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,56,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,55,,,,,,56,,,,,,55,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,54,,,,,,53,,,,,,,,,,,,,,,,,,,52,,,,,,,,,,,51,,,,,,,,,,,,,,,,,,,,,,,,,52,,,,,,,54,,,,,,55,,,,,,56,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,57,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,58,,,,,,,,,,,,,,,,,,59,,,,,,,,,,,,,,,,,,60,,,,,,,,,,,,61,,,,,,,,,,,,,,,,,,,,,,,,60,,,,,,61,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,62,,,,,,61,,,,,,62,,,,,,61,,,,,,62,,,,,,,,,,,,,,,,,,,63,,,,,,,,,,,,,,,,,,,,,,,,64,,,,,,63,,,,,,64,,,,,,63,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,62,,,,,,,,,,,,,,,,,,,61,,,,,,,,,,,,62,,,,,,,,,,,,,,,,,,,,,,,,,63,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,64,,,,,,,,,,,,63,,,,,,,,,,,,,62,,,,,,,,,,,,,,,,,,,,"
-        }
-      ],
-      "title": "Always show points between gaps",
-      "type": "timeseries"
    }
  ],
  "schemaVersion": 33,
--- a/devenv/dev-dashboards/panel-graph/graph-ng-stacking2.json
+++ b/devenv/dev-dashboards/panel-graph/graph-ng-stacking2.json
--- a/devenv/dev-dashboards/panel-table/table_pagination.json
+++ b/devenv/dev-dashboards/panel-table/table_pagination.json
--- a/devenv/docker/blocks/elastic7/docker-compose.yaml
+++ b/devenv/docker/blocks/elastic7/docker-compose.yaml
@@ -1,7 +1,7 @@
 # You need to run 'sysctl -w vm.max_map_count=262144' on the host machine

  elasticsearch7:
-    image: docker.elastic.co/elasticsearch/elasticsearch-oss:7.10.2
+    image: docker.elastic.co/elasticsearch/elasticsearch-oss:7.0.0
    command: elasticsearch -E "discovery.type=single-node"
    ports:
      - "12200:9200"
@@ -17,7 +17,7 @@
      FD_PORT: 9200

  filebeat7:
-    image: docker.elastic.co/beats/filebeat-oss:7.17.0
+    image: docker.elastic.co/beats/filebeat-oss:7.0.0
    command: filebeat -e -strict.perms=false
    volumes:
      - ./docker/blocks/elastic7/filebeat.yml:/usr/share/filebeat/filebeat.yml:ro
@@ -25,7 +25,7 @@
      - ../data/log:/var/log/grafana:ro

  metricbeat7:
-    image: docker.elastic.co/beats/metricbeat-oss:7.17.0
+    image: docker.elastic.co/beats/metricbeat-oss:7.0.0
    command: metricbeat -e -strict.perms=false
    user: root
    volumes:
--- a/devenv/docker/blocks/loki/promtail-config.yaml
+++ b/devenv/docker/blocks/loki/promtail-config.yaml
--- a/devenv/docker/blocks/loki/docker-compose.yaml
+++ b/devenv/docker/blocks/loki/docker-compose.yaml
@@ -7,7 +7,7 @@
  promtail:
    image: grafana/promtail:latest
    volumes:
-      - ./docker/blocks/loki/promtail-config.yaml:/etc/promtail/docker-config.yaml
+      - ./docker/blocks/loki/config.yaml:/etc/promtail/docker-config.yaml
      - /var/log:/var/log
      - ../data/log:/var/log/grafana
    command:
--- a/devenv/docker/blocks/prometheus/docker-compose.yaml
+++ b/devenv/docker/blocks/prometheus/docker-compose.yaml
@@ -4,12 +4,6 @@
      - "9090:9090"
    extra_hosts:
      - "host.docker.internal:host-gateway"
-    command: >
-      --enable-feature=remote-write-receiver
-      --config.file=/etc/prometheus/prometheus.yml
-      --storage.tsdb.path=/prometheus
-      --web.console.libraries=/usr/share/prometheus/console_libraries
-      --web.console.templates=/usr/share/prometheus/consoles

  node_exporter:
    image: prom/node-exporter
--- a/devenv/docker/ha_test/docker-compose.yaml
+++ b/devenv/docker/ha_test/docker-compose.yaml
@@ -24,7 +24,7 @@ services:
      MYSQL_PASSWORD: password
    command: [mysqld, --character-set-server=utf8mb4, --collation-server=utf8mb4_unicode_ci, --innodb_monitor_enable=all, --max-connections=1001]
    ports:
-      - "3306:3306"
+      - 3306
    healthcheck:
      test: ["CMD", "mysqladmin" ,"ping", "-h", "localhost"]
      timeout: 10s
@@ -47,7 +47,7 @@ services:
  #     POSTGRES_USER: grafana
  #     POSTGRES_PASSWORD: password
  #   ports:
-  #     - "5432:5432"
+  #     - 5432
  #   healthcheck:
  #     test: ["CMD-SHELL", "pg_isready -d grafana -U grafana"]
  #     timeout: 10s
@@ -66,9 +66,13 @@ services:
      - GF_DATABASE_TYPE=mysql
      - GF_DATABASE_HOST=db:3306
      - GF_DATABASE_MAX_OPEN_CONN=300
+      - GF_SESSION_PROVIDER=mysql
+      - GF_SESSION_PROVIDER_CONFIG=grafana:password@tcp(db:3306)/grafana?allowNativePasswords=true
      # - GF_DATABASE_TYPE=postgres
      # - GF_DATABASE_HOST=db:5432
      # - GF_DATABASE_SSL_MODE=disable
+      # - GF_SESSION_PROVIDER=postgres
+      # - GF_SESSION_PROVIDER_CONFIG=user=grafana password=password host=db port=5432 dbname=grafana sslmode=disable
      - GF_SERVER_ROUTER_LOGGING=true
      - GF_LOG_CONSOLE_FORMAT=json
      - GF_LOG_FILTERS=alerting.notifier:debug,alerting.notifier.slack:debug,auth:debug
--- a/docs/README.md
+++ b/docs/README.md
@@ -10,7 +10,7 @@ Yarn >= 1.22.4
 ## Build the doc site

 1. On the command line, first change to the docs folder: `cd docs`.
-1. Run `make docs`. This launches a preview of the website with the current grafana docs at `http://localhost:3002/docs/grafana/next/` which will refresh automatically when changes are made to content in the `sources` directory.
+1. Run `make docs-quick`. This launches a preview of the website with the current grafana docs at `http://localhost:3002/docs/grafana/next/` which will refresh automatically when changes are made to content in the `sources` directory.

 If you have the grafana/website repo checked out in the same directory as the grafana repo, then you can run `make docs-local-static` to use local assets (such as images).

--- a/docs/sources/_index.md
+++ b/docs/sources/_index.md
@@ -1,15 +1,9 @@
---
-aliases:
-  - /docs/grafana/v1.1
-  - /docs/grafana/latest/guides/reference/admin
-  - /docs/grafana/v3.1
-description: Guides, Installation and Feature Documentation
-keywords:
-  - grafana
-  - installation
-  - documentation
-title: Grafana documentation
---
+++
+title = "Grafana documentation"
+description = "Guides, Installation and Feature Documentation"
+keywords = ["grafana", "installation", "documentation"]
+aliases = ["/docs/grafana/v1.1", "/docs/grafana/latest/guides/reference/admin", "/docs/grafana/v3.1"]
+++

 # Grafana documentation

--- a/docs/sources/administration/_index.md
+++ b/docs/sources/administration/_index.md
@@ -1,8 +1,8 @@
---
-description: Administration
-title: Administration
-weight: 40
---
+++
+title = "Administration"
+description = "Administration"
+weight = 40
+++

 # Administration

@@ -12,4 +12,3 @@ This section includes information for Grafana administrators, team administrator
 - [Configuration]({{< relref "configuration" >}})
 - [Configure Docker image]({{< relref "configure-docker" >}})
 - [Security]({{< relref "security" >}})
- [Service accounts]({{< relref "service-accounts" >}})
--- a/docs/sources/administration/api-keys/_index.md
+++ b/docs/sources/administration/api-keys/_index.md
@@ -1,17 +0,0 @@
---
-description: This section contains information about API keys in Grafana
-keywords:
-  - API keys
-  - Service accounts
-menuTitle: API keys
-title: API keys in Grafana
-weight: 300
---
-
-# API keys in Grafana
-
-API Keys can be used to interact with Grafana HTTP APIs.
-
-We recommend using service accounts instead of API keys if you are on Grafana 8.5+, for more information refer to [About service accounts]({{< relref "../service-accounts/about-service-accounts.md#">}}).
-
-{{< section >}}
--- a/docs/sources/administration/api-keys/about-api-keys.md
+++ b/docs/sources/administration/api-keys/about-api-keys.md
@@ -1,12 +0,0 @@
---
-description: Learn about using API keys in Grafana
-menuTitle: About API keys
-title: About API keys in Grafana
-weight: 30
---
-
-# About API keys in Grafana
-
-An API key is a randomly generated string that external systems use to interact with Grafana HTTP APIs.
-
-When you create an API key, you specify a **Role** that determines the permissions associated with the API key. Role permissions control that actions the API key can perform on Grafana resources. For more information about creating API keys, refer to [Create an API key]({{< relref "./create-api-key.md#">}}).
--- a/docs/sources/administration/api-keys/create-api-key.md
+++ b/docs/sources/administration/api-keys/create-api-key.md
@@ -1,34 +0,0 @@
---
-description: How to create an API key in Grafana
-keywords:
-  - API keys
-  - Service accounts
-menuTitle: Create an API key
-title: Create an API key in Grafana
-weight: 50
---
-
-# Create an API key in Grafana
-
-Create an API key when you want to manage your computed workload with a user.
-
-For more information about API keys, refer to [About API keys in Grafana]({{< relref "./about-api-keys.md">}}).
-
-This topic shows you how to create an API key using the Grafana UI. You can also create an API key using the Grafana HTTP API. For more information about creating API keys via the API, refer to [Create API key via API]({{< relref "../../http_api/create-api-tokens-for-org.md#how-to-create-a-new-organization-and-an-api-token">}}).
-
-## Before you begin:
-
- Ensure you have permission to create and edit API keys. For more information about permissions, refer to [About users and permissions]({{< relref "../manage-users-and-permissions/about-users-and-permissions.md#">}}).
-
-**To create an API key:**
-
-1. Sign in to Grafana, hover your cursor over **Configuration** (the gear icon), and click **API Keys**.
-1. Click **New API key**.
-1. Enter a unique name for the key.
-1. In the **Role** field, select one of the following access levels you want to assign to the key.
-   - **Admin**: Enables a user to use APIs at the broadest, most powerful administrative level.
-   - **Editor** or **Viewer** to limit the key's users to those levels of power.
-1. In the **Time to live** field, specify how long you want the key to be valid.
-   - The maximum length of time is 30 days (one month). You enter a number and a letter. Valid letters include `s` for seconds,`m` for minutes, `h` for hours, `d `for days, `w` for weeks, and `M `for month. For example, `12h` is 12 hours and `1M` is 1 month (30 days).
-   - If you are unsure about how long an API key should be valid, we recommend that you choose a short duration, such as a few hours. This approach limits the risk of having API keys that are valid for a long time.
-1. Click **Add**.
--- a/docs/sources/administration/cli.md
+++ b/docs/sources/administration/cli.md
@@ -1,13 +1,9 @@
---
-description: Guide to using grafana-cli
-keywords:
-  - grafana
-  - cli
-  - grafana-cli
-  - command line interface
-title: Grafana CLI
-weight: 400
---
+++
+title = "Grafana CLI"
+description = "Guide to using grafana-cli"
+keywords = ["grafana", "cli", "grafana-cli", "command line interface"]
+weight = 400
+++

 # Grafana CLI

--- a/docs/sources/administration/configuration.md
+++ b/docs/sources/administration/configuration.md
@@ -1,14 +1,10 @@
---
-aliases:
-  - /docs/grafana/latest/installation/configuration/
-description: Configuration documentation
-keywords:
-  - grafana
-  - configuration
-  - documentation
-title: Configuration
-weight: 150
---
+++
+title = "Configuration"
+description = "Configuration documentation"
+keywords = ["grafana", "configuration", "documentation"]
+aliases = ["/docs/grafana/latest/installation/configuration/"]
+weight = 150
+++

 # Configuration

@@ -139,10 +135,6 @@ Options are `production` and `development`. Default is `production`. _Do not_ ch
 Set the name of the grafana-server instance. Used in logging, internal metrics, and clustering info. Defaults to: `${HOSTNAME}`, which will be replaced with
 environment variable `HOSTNAME`, if that is empty or does not exist Grafana will try to use system calls to get the machine name.

-### force_migration
-
-Force migration will run migrations that might cause data loss. Default is `false`.
-
 <hr />

 ## [paths]
@@ -469,13 +461,7 @@ value is `true`.

 ### check_for_updates

-Set to false, disables checking for new versions of Grafana from Grafana's GitHub repository. When enabled, the check for a new version runs every 10 minutes. It will notify, via the UI, when a new version is available. The check itself will not prompt any auto-updates of the Grafana software, nor will it send any sensitive information.
-
-### check_for_plugin_updates
-
-> **Note**: Available in Grafana v8.5.0 and later versions.
-
-Set to false disables checking for new versions of installed plugins from https://grafana.com. When enabled, the check for a new plugin runs every 10 minutes. It will notify, via the UI, when a new plugin update exists. The check itself will not prompt any auto-updates of the plugin, nor will it send any sensitive information.
+Set to false to disable all checks to https://grafana.com for new versions of installed plugins and to the Grafana GitHub repository to check for a newer version of Grafana. The version information is used in some UI views to notify that a new Grafana update or a plugin update exists. This option does not cause any auto updates, nor send any sensitive information. The check is run every 10 minutes.

 ### google_analytics_ua_id

@@ -517,10 +503,6 @@ If you want to track Grafana usage via Azure Application Insights, then specify

 <hr />

-### enable_feedback_links
-
-If set to false will remove all feedback links from the UI. Defaults to true.
-
 ## [security]

 ### disable_initial_admin_creation
@@ -604,21 +586,6 @@ Set Content Security Policy template used when adding the Content-Security-Polic

 <hr />

-### angular_support_enabled
-
-This currently defaults to `true` but will default to `false` in a future release. When set to false the angular framework and support components will not be loaded. This means that
-all plugins and core features that depend on angular support will stop working.
-
-Current core features that will stop working:
-
- Heatmap panel
- Old graph panel
- Old table panel
- Postgres, MySQL and MSSQL data source query editors
- Legacy alerting edit rule UI
-
-Before we disable angular support by default we plan to migrate these remaining areas to React.
-
 ## [snapshots]

 ### external_enabled
@@ -672,7 +639,7 @@ Path to the default home dashboard. If this value is empty, then Grafana uses St

 Set to `false` to prohibit users from being able to sign up / create
 user accounts. Default is `false`. The admin user can still create
-users. For more information about creating a user, refer to [Add a user]({{< relref "../administration/manage-users-and-permissions/manage-server-users/add-user.md" >}}).
+users from the [Grafana Admin Pages]({{< relref "../manage-users/server-admin/server-admin-manage-users.md" >}}).

 ### allow_org_create

@@ -1363,22 +1330,6 @@ For more information about this feature, refer to [Explore]({{< relref "../explo

 Enable or disable the Explore section. Default is `enabled`.

-## [help]
-
-Configures the help section.
-
-### enabled
-
-Enable or disable the Help section. Default is `enabled`.
-
-## [profile]
-
-Configures the Profile section.
-
-### enabled
-
-Enable or disable the Profile section. Default is `enabled`.
-
 ## [metrics]

 For detailed instructions, refer to [Internal Grafana metrics]({{< relref "view-server/internal-metrics.md" >}}).
--- a/docs/sources/administration/configure-docker.md
+++ b/docs/sources/administration/configure-docker.md
@@ -1,15 +1,10 @@
---
-aliases:
-  - /docs/grafana/latest/installation/configure-docker/
-description: Guide for configuring the Grafana Docker image
-keywords:
-  - grafana
-  - configuration
-  - documentation
-  - docker
-title: Configure Grafana Docker image
-weight: 200
---
+++
+title = "Configure Grafana Docker image"
+description = "Guide for configuring the Grafana Docker image"
+keywords = ["grafana", "configuration", "documentation", "docker"]
+aliases = ["/docs/grafana/latest/installation/configure-docker/"]
+weight = 200
+++

 # Configure a Grafana Docker image

--- a/docs/sources/administration/database-encryption.md
+++ b/docs/sources/administration/database-encryption.md
@@ -1,16 +1,10 @@
---
-aliases:
-  - ''
-description: Grafana database encryption
-keywords:
-  - grafana
-  - database
-  - encryption
-  - envelope encryption
-  - documentation
-title: Database encryption
-weight: 450
---
+++
+title = "Database encryption"
+description = "Grafana database encryption"
+keywords = ["grafana", "database", "encryption", "envelope encryption", "documentation"]
+aliases = [""]
+weight = 450
+++

 # Grafana database encryption

--- a/docs/sources/administration/jaeger-instrumentation.md
+++ b/docs/sources/administration/jaeger-instrumentation.md
@@ -1,12 +1,9 @@
---
-description: Jaeger traces emitted and propagation by Grafana
-keywords:
-  - grafana
-  - jaeger
-  - tracing
-title: Jaeger instrumentation
-weight: 900
---
+++
+title = "Jaeger instrumentation"
+description = "Jaeger traces emitted and propagation by Grafana"
+keywords = ["grafana", "jaeger", "tracing"]
+weight = 900
+++

 # Jaeger instrumentation

--- a/docs/sources/administration/manage-organizations/_index.md
+++ b/docs/sources/administration/manage-organizations/_index.md
@@ -1,119 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/manage-users/server-admin/
-  - /docs/grafana/latest/manage-users/server-admin/server-admin-manage-orgs/
-description: Describes how to use organizations to isolate dashboard to users and
-  teams.
-keywords:
-  - organizations
-  - dashboards
-menuTitle: Manage organizations
-title: Manage organizations
-weight: 300
---
-
-# Manage organizations
-
-This topic describes what organizations are, and how to create, edit, and delete them.
-
-## About organizations
-
-An organization is an entity that helps you isolate users and resources such as dashboards, annotations, and data sources from each other. Their purpose is to provide completely separate experiences, which look like multiple instances of Grafana, within a single instance. Multiple organizations are easier and cheaper to manage than multiple instances of Grafana.
-
-Users, configuration settings, and Grafana Enterprise licenses are shared between organizations. Other resources, like dashboards, data sources, annotations, folders, Teams, and Alerts, are isolated within each organization and cannot be easily shared with another organization.
-
-The following table summarizes the resources you can share and/or isolate using organizations.
-
-| Resource                 | Mode             |
-| ------------------------ | ---------------- |
-| Users                    | Share or isolate |
-| Folders                  | Isolate only     |
-| Dashboards               | Isolate only     |
-| Data sources             | Isolate only     |
-| Alerts                   | Isolate only     |
-| Notification channels    | Isolate only     |
-| Annotations              | Isolate only     |
-| Reports                  | Isolate only     |
-| API keys                 | Isolate only     |
-| Authentication providers | Share only       |
-| Configuration settings   | Share only       |
-| Licenses                 | Share            |
-
-The member of one organization cannot view dashboards assigned to another organization. However, a user can belong to multiple organizations.
-
-Grafana Server Administrators are responsible for creating organizations. For more information about the Grafana Server Administrator role, refer to [Grafana server administrators]({{< relref "../manage-users-and-permissions/about-users-and-permissions.md#Grafana server administrators" >}}).
-
-## View a list of organizations
-
-Complete this task when you want to view a list of existing organizations.
-
-### Before you begin
-
- Ensure that you have Grafana Server Administrator permissions
-
-**To view a list of organizations:**
-
-1. Sign in to Grafana as a server administrator.
-1. Hover your cursor over the **Server Admin** (shield) icon until a menu appears, and click **Orgs**.
-
-A list of organizations appears.
-
-![Server Admin organization list](/static/img/docs/manage-users/server-org-list-7-3.png)
-
-## Create an organization
-
-Create an organization when you want to isolate dashboards and other resources from each other.
-
-### Before you begin
-
- Ensure that you have Grafana Server Administrator permissions
-
-**To create an organization:**
-
-1. Sign in to Grafana as a server administrator.
-1. Hover your cursor over the **Server Admin** (shield) icon until a menu appears, and click **Orgs**.
-1. Click **+ New org**.
-1. Enter the name of the new organization and click **Create**.
-
-   Grafana creates the organization and adds you as the organization administrator.
-
-1. On the **Preferences** tab, select a home dashboard, time zone, and week start.
-
-   For more information about preferences, refer to [Preferences]({{< relref "../preferences/_index.md" >}}).
-
-For more information about adding users to an organization, refer to [Add a user to an organization]({{< relref "../manage-users-and-permissions/manage-server-users/add-remove-user-to-org.md" >}}).
-
-## Delete an organization
-
-This action permanently removes an organization from your Grafana server.
-
-> **Warning:** Deleting the organization also deletes all teams and dashboards associated the organization.
-
-### Before you begin
-
- Ensure that you have Grafana Server Administrator permissions
- Because the delete action removes all teams and dashboards associated with the organization, ensure that the users who rely on the organization dashboards are aware of the change
-
-**To delete an organization:**
-
-1. Sign in to Grafana as a server administrator.
-1. Hover your cursor over the **Server Admin** (shield) icon until a menu appears, and click **Orgs**.
-1. Click the red **X** next to the organization that you want to delete.
-1. Click **Delete**.
-
-## Edit an organization
-
-Edit an organization when you want to change its name.
-
-### Before you begin
-
- Ensure that you have Grafana Server Administrator permissions
-
-**To edit an organization:**
-
-1. Sign in to Grafana as a server administrator.
-1. Hover your cursor over the **Server Admin** (shield) icon until a menu appears, and click **Orgs**.
-1. Click the organization you want to edit.
-1. Update the organization name and click **Update**.
-
-![Server admin Edit Organization](/static/img/docs/manage-users/server-admin-edit-org-7-3.png)
--- a/docs/sources/administration/manage-user-preferences/_index.md
+++ b/docs/sources/administration/manage-user-preferences/_index.md
@@ -1,106 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/administration/change-your-password/
-  - /docs/grafana/latest/administration/manage-user-preferences/
-description: Learn how to update your user preferences and switch organizations
-keywords:
-  - password
-  - change
-  - organization
-  - change
-title: Manage user preferences
-weight: 400
---
-
-# Manage user preferences
-
-Grafana allows you to manage certain aspects of your user account, including your user name, email, and password.
-
-You can also view important information about your account, such as the organizations and roles to which you are assigned and the Grafana sessions associated with your account.
-
-## Change your Grafana password
-
-You can change your Grafana password at any time.
-
-> **Note**: If your Grafana instance uses an <!--[external authentication provider]({{< relref "../../auth/_index.md">}})--> external authentication provider, then you might not be able to change your password in Grafana. Contact your Grafana administrator for more information.
-
-**To change your password**:
-
-1. Sign in to Grafana.
-1. Hover your mouse over the user icon in the lower-left corner of the page.
-1. Click **Change Password**.
-   Grafana opens the **Change Password** tab.
-
-1. Enter your old password and a new password.
-1. Confirm your new password.
-1. Click **Change Password**.
-
-## Edit your profile
-
-Your profile includes your name, user name, and email address, which you can update.
-
-**To edit your profile**:
-
-1. Sign in to Grafana.
-1. Hover your cursor over the user icon in the lower-left corner of the page and click **Preferences**.
-1. In the **Edit Profile** section, update your profile and click **Save**.
-
-## Edit your preferences
-
-You can choose the way you would like data to appear in Grafana, including the UI theme, home dashboard, timezone, and first day of the week. You can set these preferences for your own account, for a team, for an organization, or Grafana-wide using configuration settings. Your user preferences take precedence over team, organization, and Grafana default preferences. For more information, see [Grafana preferences]({{< relref "../../administration/preferences/_index.md">}}).
-
- **UI theme** determines whether Grafana appears in light mode or dark mode. By default, UI theme is set to dark mode.
- **Home dashboard** refers to the dashboard you see when you sign in to Grafana. By default, this is set to the Home dashboard.
- **Timezone** is used by dashboards when you set time ranges, so that you view data in your timezone instead of UTC.
- **Week start** is the first day of the week you want to use in dashboard time ranges, for example, `This week`.
-
-**To edit your preferences**:
-
-1. Sign in to Grafana.
-1. Hover your cursor over the user icon in the lower-left corner of the page, and click **Preferences**.
-1. Update any of the values in the **Preferences** section.
-1. Click **Save** at the bottom of the Preferences section.
-
-## Switch organizations
-
-When you sign in to Grafana, the system signs you in to a default organization. If you are assigned to multiple organizations, then you might need to switch organizations. For example, if you need to view a dashboard not associated with your current organization, then you should switch organizations to view associated dashboards.
-
-**To switch organizations**:
-
-1. Sign in to Grafana.
-1. Hover your cursor over the user icon in the lower-left corner of the page and click **Switch organization**.
-1. Next to the organization that you want to sign in to, click **Switch to**.
-
-## View your assigned organizations
-
-Every user is a member of at least one organization. You can have different roles in each organization of which you are a member.
-
-**To view your assigned organizations**:
-
-1. Sign in to Grafana.
-1. Hover your cursor over the user icon in the lower-left corner of the page and click **Preferences**.
-1. Scroll down to the **Organizations** section and review the following information:
-   - **Name**: The name of the organizations of which you are a member.
-   - **Role**: The role to which you are assigned in the organization. For more information about roles and permissions, refer to [Organization users and permissions]({{< relref "../../administration/manage-users-and-permissions/about-users-and-permissions.md#organization-users-and-permissions" >}}).
-   - **Current**: Grafana indicates the organization that you are currently signed into as _Current_. If you are a member of multiple organizations, you can click **Select** to switch to that organization.
-
-## View your Grafana sessions
-
-Grafana logs your sessions in each Grafana instance. You can review this section if you suspect someone has misused your Grafana credentials.
-
-**To view your Grafana sessions**:
-
-1. Sign in to Grafana.
-1. Hover your cursor over the user icon in the lower-left corner of the page, and click **Preferences**.
-1. Scroll down to the **Sessions** section.
-
-## Sign out a user session
-
-You can sign out other sessions using your account in order to prevent other people from accessing Grafana using your credentials.
-
-**To sign out one of your Grafana sessions**:
-
-1. Sign in to Grafana.
-1. Hover your cursor over the user icon in the lower-left corner of the page, and click **Preferences**.
-1. Scroll down to the **Sessions** section.
-1. Click the red "sign out" icon next to the session you would like to sign out.
--- a/docs/sources/administration/manage-users-and-permissions/_index.md
+++ b/docs/sources/administration/manage-users-and-permissions/_index.md
@@ -1,14 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/administration/manage-users-and-permissions/
-title: Manage users and permissions
-weight: 200
---
-
-# Manage users and permissions
-
-A _user_ is defined as any individual who can log in to Grafana. Each user is associated with a _role_ that includes _permissions_. Permissions determine the tasks a user can perform in the system. For example, the **Admin** role includes permissions for an administrator to create and delete users.
-
-The following topics describe how to use permissions to control user access to data sources, dashboards, users, and teams.
-
-{{< section >}}
--- a/docs/sources/administration/manage-users-and-permissions/about-users-and-permissions.md
+++ b/docs/sources/administration/manage-users-and-permissions/about-users-and-permissions.md
@@ -1,157 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/manage-users/
-  - /docs/grafana/latest/administration/manage-users-and-permissions/about-users-and-permissions/
-  - /docs/grafana/latest/permissions/overview/
-  - /docs/grafana/latest/permissions/
-  - /docs/grafana/latest/permissions/organization_roles/
-title: About users and permissions
-weight: 100
---
-
-# About users and permissions
-
-A _user_ is defined as any individual who can log in to Grafana. Each user is associated with a _role_ that includes _permissions_. Permissions determine the tasks a user can perform in the system. For example, the **Admin** role includes permissions for an administrator to create and delete users.
-
-You can assign a user one of three types of permissions:
-
- Grafana server administrator permissions: Manage Grafana server-wide settings and resources
- Organization permissions: Manage access to dashboards, alerts, plugins, teams, playlists, and other resources for an entire organization. The available roles are Viewer, Editor, and Admin.
- Dashboard and folder permission: Manage access to dashboards and folders
-
-> **Note**: If you are running Grafana Enterprise, you can also control access to data sources and use fine-grained access control to grant read and write permissions for specific resources. For more information about access control options available with Grafana Enterprise, refer to [Grafana Enterprise user permissions features](#grafana-enterprise-user-permissions-features).
-
-## Grafana server administrators
-
-A Grafana server administrator manages server-wide settings and access to resources such as organizations, users, and licenses. Grafana includes a default server administrator that you can use to manage all of Grafana, or you can divide that responsibility among other server administrators that you create.
-
-A server administrator can perform the following tasks:
-
- Manage users and permissions
- Create, edit, and delete organizations
- View server-wide settings defined in the [Configuration]({{< relref "../../administration/configuration.md" >}}) file
- View Grafana server statistics, including total users and active sessions
- Upgrade the server to Grafana Enterprise.
-
-> **Note:** The server administrator role does not exist in Grafana Cloud.
-
-## Organization users and permissions
-
-All Grafana users belong to at least one organization. An organization is an entity that exists within your instance of Grafana.
-
-Permissions assigned to a user within an organization control the extent to which the user has access to and can update the following organization resources:
-
- dashboards and folders
- alerts
- playlists
- users within that organization
- data sources
- teams
- organization and team settings
- plugins
- annotations
- library panels
- API keys
-
-### Organization roles
-
-Organization role-based permissions are global, which means that each permission level applies to all Grafana resources within an given organization. For example, an editor can see and update _all_ dashboards in an organization, unless those dashboards have been specifically restricted using [dashboard permissions]({{< relref "manage-dashboard-permissions/_index.md">}}).
-
-Grafana uses the following roles to control user access:
-
- **Organization administrator**: Has access to all organization resources, including dashboards, users, and teams.
- **Editor**: Can view and edit dashboards, folders, and playlists.
- **Viewer**: Can view dashboards and playlists.
-
-The following table lists permissions for each role.
-
-| Permission                     | Organization administrator | Editor | Viewer |
-| :----------------------------- | :------------------------: | :----: | :----: |
-| View dashboards                |             x              |   x    |   x    |
-| Add, edit, delete dashboards   |             x              |   x    |        |
-| Add, edit, delete folders      |             x              |   x    |        |
-| View playlists                 |             x              |   x    |   x    |
-| Add, edit, delete playlists    |             x              |   x    |        |
-| Create library panels          |             x              |   x    |        |
-| View annotations               |             x              |   x    |   x    |
-| Add, edit, delete annotations  |             x              |   x    |        |
-| Access Explore                 |             x              |   x    |        |
-| Add, edit, delete data sources |             x              |        |        |
-| Add and edit users             |             x              |        |        |
-| Add and edit teams             |             x              |        |        |
-| Change organizations settings  |             x              |        |        |
-| Change team settings           |             x              |        |        |
-| Configure application plugins  |             x              |        |        |
-
-## Dashboard permissions
-
-When you want to extend a viewer's ability to edit and save dashboard changes or limit an editor's permission to modify a dashboard, you can assign permissions to dashboards and dashboard folders. For example, you might want a certain viewer to be able to to edit a dashboard. While that user can _see_ all dashboards, you can grant them access to _update_ only one of them.
-
-> Important: The dashboard permissions you specify override the organization permissions you assign to the user for the selected entity.
-
-You can specify the following permissions to dashboards and folders.
-
- **Admin**: Can create, edit, or delete a dashboard or folder. Administrators can also change dashboard and folder permissions.
- **Edit**: Can create and edit dashboards. Editors _cannot_ change folder or dashboard permissions, or add, edit, or delete folders.
- **View**: Can only view dashboards and folders.
-
-For more information about assigning dashboard folder permissions, refer to [Grant dashboard folder permissions]({{< relref "./manage-dashboard-permissions/_index.md#grant-dashboard-folder-permissions" >}}).
-
-For more information about assigning dashboard permissions, refer to [Grant dashboard permissions]({{< relref "./manage-dashboard-permissions/_index.md#grant-dashboard-permissions" >}}).
-
-## Editors with administrator permissions
-
-If you have access to the Grafana server, you can modify the default editor role so that editors can use administrator permissions to manage dashboard folders, dashboards, and teams that they create.
-
-> **Note**: This permission does not allow editors to manage folders, dashboards, and teams that they do not create.
-
-This setting can be used to enable self-organizing teams to administer their own dashboards.
-
-For more information about assigning administrator permissions to editors, refer to [Grant editors administrator permissions]({{< relref "./manage-server-users/grant-editor-admin-permissions.md" >}}).
-
-## Viewers with dashboard preview and Explore permissions
-
-If you have access to the Grafana server, you can modify the default viewer role so that viewers can:
-
- Edit and preview dashboards, but cannot save their changes or create new dashboards.
- Access and use [Explore]({{< relref "../../explore/_index.md" >}}).
-
-Extending the viewer role is useful for public Grafana installations where you want anonymous users to be able to edit panels and queries, but not be able to save or create new dashboards.
-
-For more information about assigning dashboard preview permissions to viewers, refer to [Enable viewers to preview dashboards and use Explore]({{< relref "./manage-dashboard-permissions/_index.md#enable-viewers-to-preview-dashboards-and-use-explore" >}}).
-
-## Teams and permissions
-
-A team is a group of users within an organization that have common dashboard and data source permission needs. For example, instead of assigning five users access to the same dashboard, you can create a team that consists of those users and assign dashboard permissions to the team. A user can belong to multiple teams.
-
-You can assign a team member one of the following permissions:
-
- **Member**: Includes the user as a member of the team. Members do not have team administrator privileges.
- **Admin**: Administrators have permission to manage various aspects of the team, including team membership, permissions, and settings.
-
-Because teams exist inside an organization, the organization administrator can manage all teams. When the `editors_can_admin` setting is enabled, editors can create teams and manage teams that they create. For more information about the `editors_can_admin` setting, refer to [Grant editors administrator permissions]({{< relref "./manage-server-users/grant-editor-admin-permissions.md" >}}).
-
-## Grafana Enterprise user permissions features
-
-While Grafana OSS includes a robust set of permissions and settings that you can use to manage user access to server and organization resources, you might find that you require additional capabilities.
-
-Grafana Enterprise provides the following permissions-related features:
-
- Data source permissions
- Fine-grained access control
-
-### Data source permissions
-
-By default, a user can query any data source in an organization, even if the data source is not linked to the user's dashboards.
-
-Data source permissions enable you to restrict data source query permissions to specific **Users** and **Teams**. For more information about assigning data source permissions, refer to [Data source permissions]({{< relref "../../enterprise/datasource_permissions.md" >}}).
-
-### Fine-grained access control
-
-Fine-grained access control provides you a way of granting, changing, and revoking user read and write access to Grafana resources, such as users, reports, and authentication.
-
-For more information about fine-grained access control, refer to [Fine-grained access control]({{< relref "../../enterprise/access-control" >}}).
-
-### Learn more
-
-Want to know more? Complete the [Create users and teams](https://grafana.com/tutorials/create-users-and-teams) tutorial to learn how to set up users and teams.
--- a/docs/sources/administration/manage-users-and-permissions/manage-dashboard-permissions/_index.md
+++ b/docs/sources/administration/manage-users-and-permissions/manage-dashboard-permissions/_index.md
@@ -1,145 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/permissions/dashboard_folder_permissions/
-  - /docs/grafana/latest/administration/manage-users-and-permissions/manage-dashboard-permissions/
-title: Manage dashboard permissions
-weight: 500
---
-
-# Manage dashboard permissions
-
-Dashboard and dasboard folder permissions enable you to grant a viewer the ability to edit and save dashboard changes, or limit an editor's permission to modify a dashboard.
-
-For more information about dashboard permissions, refer to [Dashboard permissions]({{< relref "../about-users-and-permissions/#dashboard-permissions">}}).
-
-## Grant dashboard folder permissions
-
-When you grant user permissions for folders, that setting applies to all dashboards contained in the folder. Consider using this approach to assigning dashboard permissions when you have users or teams who require access to groups of related dashboards.
-
-### Before you begin
-
- Ensure you have organization administrator privileges
- Identify the dashboard folder permissions you want to modify and the users or teams to which you want to grant access. For more information about dashboard permissions, refer to [Dashboard permissions]({{< relref "../about-users-and-permissions/#dashboard-permissions">}}).
-
-**To grant dashboard folder permissions**:
-
-1. Sign in to Grafana as an organization administrator.
-2. In the sidebar, hover your mouse over the **Dashboards** (squares) icon and click **Browse**.
-3. Hover your mouse cursor over a folder and click **Go to folder**.
-4. Click the **Permissions** tab, and then click **Add Permission**.
-5. In the **Add Permission For** dropdown menu, select **User**, **Team**, or one of the role options.
-6. Select the user or team.
-
-   If you select a role option, you do not select a user or team.
-
-7. Select the permission and click **Save**.
-
-## Grant dashboard permissions
-
-When you grant dashboard folder permissions, that setting applies to all dashboards in the folder. For a more granular approach to assigning permissions, you can also assign user permissions to individual dashboards.
-
-For example, if a user with the viewer organization role requires editor (or admin) access to a dashboard, you can assign those elevated permissions on an individual basis.
-
-> **Note**: If you have assigned a user dashboard folder permissions, you cannot also assign the user permission to dashboards contained in the folder.
-
-Grant dashboard permissions when you want to restrict or enhance dashboard access for users who do not have permissions defined in the associated dashboard folder.
-
-### Before you begin
-
- Ensure you have organization administrator privileges
- Identify the dashboard permissions you want to modify and the users or teams to which you want to grant access
-
-**To grant dashboard permissions**:
-
-1. Sign in to Grafana as an organization administrator.
-1. In the sidebar, hover your mouse over the **Dashboards** (squares) icon and click **Browse**.
-1. Open a dashboard.
-1. In the top right corner of the dashboard, click **Dashboard settings** (the cog icon).
-1. Click **Permissions** and then click **Add Permission**.
-1. In the **Add Permission For** dropdown menu, select **User** or **Team**.
-1. Select the user or team.
-1. Select the permission and click **Save**.
-
-## Enable viewers to edit (but not save) dashboards and use Explore
-
-By default, the viewer organization role does not allow viewers to create dashboards or use the Explore feature. However, by modifying a configuration setting, you can allow viewers to edit a panel and make changes to a dashboard but not save those changes. This setting also enables viewers to use the Explore feature.
-
-This modification is useful for public Grafana installations where you want anonymous users to be able to edit panels and queries but not save or create new dashboards.
-
-### Before you begin
-
- Ensure that you have access to the Grafana server
-
-**To enable viewers to preview dashboards and use Explore**:
-
-1. Open the Grafana configuration file.
-
-   For more information about the Grafana configuration file and its location, refer to [Configuration]({{< relref "../../../administration/configuration">}}).
-
-1. Locate the `viewers_can_edit` parameter.
-1. Set the `viewers_can_edit` value to `true`.
-1. Save your changes and restart Grafana.
-
-## Edit dashboard permissions
-
-Edit dashboard permissions when you are want to enhance or restrict a user's access to a dashboard. For more information about dashboard permissions, refer to [Dashboard permissions]({{< relref "../about-users-and-permissions/#dashboard-permissions">}}).
-
-### Before you begin
-
- Identify the dashboard and user permission you want to change
- Ensure you have organization administrator privileges
-
-**To edit dashboard permissions**:
-
-1. Sign in to Grafana as an organization administrator.
-1. In the sidebar, hover your mouse over the **Dashboards** (squares) icon and click **Browse**.
-1. Open a dashboard.
-1. In the top-right corner of the dashboard, click **Dashboard settings** (the cog icon).
-1. Click **Permissions**.
-1. In the dropdown, update the permissions, and click **Save**.
-
-## Restrict access to dashboards
-
-Grafana applies the highest permission a given user has to access a resource like a dashboard, so if you want to prevent a user from accessing a folder or dashboard you need to consider the user's organization role, folder permissions, and dashboard permissions.
-
- You cannot override organization administrator permissions. Organization administrators have access to all organization resources.
- User permissions set for a dashboard folder propagate to dashboards contained in the folder.
- A lower permission level does not affect access if a more general rule exists with a higher permission.
-
-Refer to the following examples to understand how organization and dashboard permissions impact a user's access to dashboards.
-
-### Example 1
-
-In this example, user1 has the editor organization role.
-
-Dashboard permissions settings:
-
- Everyone with Editor role can edit
- user1 is set to `view`
-
-Result: User1 has edit permissions because the user's organization role is Editor.
-
-### Example 2
-
-In this example, user1 has the viewer organization role and is a member of team1.
-
-Dashboard permissions settings:
-
- Everyone with Viewer role can view
- user1 is set to `edit`
- team1 is set to `admin`
-
-Result: User1 has administrator permissions for the dashboard because user1 is a member of team1.
-
-### Example 3
-
-In this example, user1 has the viewer organization role.
-
-Dashboard permissions settings:
-
- user1 is set to `admin`, which is inherited from the permissions set in parent folder
- user1 is set to `edit`
-
-Result: You receive an error message that cannot override a higher permission with a lower permission in the same dashboard. User1 has administrator permissions.
-
-> Refer to [Fine-grained access Control]({{< relref "../../../enterprise/access-control/_index.md" >}}) in Grafana Enterprise to understand how to use fine-grained permissions to restrict access to dashboards, folders, administrative functions, and other resources.
--- a/docs/sources/administration/manage-users-and-permissions/manage-org-users/_index.md
+++ b/docs/sources/administration/manage-users-and-permissions/manage-org-users/_index.md
@@ -1,15 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/manage-users/org-admin/
-  - /docs/grafana/latest/administration/manage-users-and-permissions/manage-org-users/
-title: Manage users in an organization
-weight: 400
---
-
-# Manage users in an organization
-
-Organization administrators can invite users to join their organization. Organization users have access to organization resources based on their role, which is **Admin**, **Editor**, or **Viewer**. Permissions associated with each role determine the tasks a user can perform in the system.
-
-For more information about organization user permissions, refer to [Organization users and permissions]({{< relref "../about-users-and-permissions/#organization-users-and-permissions">}}).
-
-{{< section >}}
--- a/docs/sources/administration/manage-users-and-permissions/manage-org-users/change-user-org-permissions.md
+++ b/docs/sources/administration/manage-users-and-permissions/manage-org-users/change-user-org-permissions.md
@@ -1,28 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/administration/manage-users-and-permissions/manage-org-users/change-user-org-permissions/
-title: Change a user's organization permissions
-weight: 30
---
-
-# Change a user's organization permissions
-
-Update user permissions when you want to enhance or restrict a user's access to organization resources. For more information about organization permissions, refer to [Organization roles]({{< relref "../about-users-and-permissions/#organization-roles">}}).
-
-## Before you begin
-
- Ensure you have organization administrator privileges
-
-**To change the organization role of a user**:
-
-1. Sign in to Grafana as an organization administrator.
-1. Hover your cursor over the **Configuration** (gear) icon in the side menu and click **Users**.
-1. Find the user account for which you want to change the role.
-
-   If necessary, use the search field to filter the list.
-
-1. Locate the user on the list and in the **Role** column, click the user role.
-1. Select the role that you want to assign.
-1. Click **Update**.
-
-> **Note:** If you have [server administrator]({{< relref "../about-users-and-permissions.md#grafana-server-administrators">}}) permissions, you can also [change a user's organization permissions]({{< relref "../../manage-users-and-permissions/manage-server-users/change-user-org-permissions.md" >}}) in the Server Admin section.
--- a/docs/sources/administration/manage-users-and-permissions/manage-org-users/invite-user-join-org.md
+++ b/docs/sources/administration/manage-users-and-permissions/manage-org-users/invite-user-join-org.md
@@ -1,45 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/administration/manage-users-and-permissions/manage-org-users/invite-user-join-org/
-title: Invite a user to join an organization
-weight: 10
---
-
-# Invite a user to join an organization
-
-When you invite users to join an organization, you assign the **Admin**, **Editor**, or **Viewer** role which controls user access to the dashboards and data sources owned by the organization. Users receive an email that prompts them to accept the invitation.
-
- If you know that the user already has access Grafana and you know their user name, then you issue an invitation by entering their user name.
- If the user is new to Grafana, then use their email address to issue an invitation. The system automatically creates the user account on first sign in.
-
-> **Note:** If you have [server administrator]({{< relref "../about-users-and-permissions.md#grafana-server-administrators">}}) permissions, you can also manually [add a user to an organization]({{< relref "../../manage-users-and-permissions/manage-server-users/add-remove-user-to-org.md" >}}).
-
-## Before you begin
-
- Ensure you have organization administrator privileges.
- If the user already has access to Grafana, obtain their user name.
- Determine the permissions you want to assign to the user. For more information about organization permissions, refer to [Organization roles]({{< relref "../about-users-and-permissions/#organization-roles">}}).
-
-**To invite or add an existing user account to your organization**:
-
-1. Sign in to Grafana as an organization administrator.
-1. To switch to the organization to which you want to invite a user, hover your mouse over your profile and click **Switch organization** and select an organization.
-
-   > **Note**: It might be that you are currently in the proper organization and don't need to switch organizations.
-
-1. Hover your cursor over the **Configuration** (gear) icon in the side menu and click **Users**.
-1. Click **Invite**.
-1. Enter the following information:
-
-   | Field             | Description                                                                                                                                                                                                                                                              |
-   | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-   | Email or username | Either the email or username that the user will use to sign in to Grafana.                                                                                                                                                                                               |
-   | Name              | The user's name.                                                                                                                                                                                                                                                         |
-   | Role              | Click the organization role to assign this user. For more information about organization roles, refer to [Organization roles]({{< relref "../about-users-and-permissions#organization-roles" >}})..                                                                      |
-   | Send invite email | Switch to on if your organization has configured. The system sends an email to the user inviting them to sign in to Grafana and join the organization. Switch to off if you are not using email. The user can sign in to Grafana with the email or username you entered. |
-
-1. Click **Submit**.
-
-If the invitee is not already a user, the system adds them.
-
-![Invite User](/static/img/docs/manage-users/org-invite-user-7-3.png).
--- a/docs/sources/administration/manage-users-and-permissions/manage-org-users/manage-pending-invites.md
+++ b/docs/sources/administration/manage-users-and-permissions/manage-org-users/manage-pending-invites.md
@@ -1,32 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/administration/manage-users-and-permissions/manage-org-users/manage-pending-invites/
-title: Manage a pending invitation
-weight: 20
---
-
-# Manage a pending invitation
-
-Periodically review invitations you have sent so that you can see a list of users that have not yet accepted the invitation or cancel a pending invitation.
-
-> **Note:** The **Pending Invites** button is only visible if there are unanswered invitations.
-
-## Before you begin
-
- Ensure you have organization administrator privileges
-
-**To manage a pending invitation**:
-
-1. Sign in to Grafana as an organization administrator.
-1. Hover your cursor over the **Configuration** (gear) icon in the side menu and click **Users**.
-1. Click **Pending Invites**.
-
-   The **Pending Invites** button appears only when there are unaccepted invitations.
-
-   ![Pending Invites button](/static/img/docs/manage-users/pending-invites-button-7-3.png)
-
-To cancel an invitation, click the red **X** next to the invitation.
-
-To copy an invitation link and send it directly to a user, click Copy Invite. You can then paste the invite link into a message.
-
-![Pending Invites list](/static/img/docs/manage-users/pending-invites-list-7-3.png)
--- a/docs/sources/administration/manage-users-and-permissions/manage-org-users/remove-user-from-org.md
+++ b/docs/sources/administration/manage-users-and-permissions/manage-org-users/remove-user-from-org.md
@@ -1,28 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/administration/manage-users-and-permissions/manage-org-users/remove-user-from-org/
-title: Remove a user from an organization
-weight: 40
---
-
-# Remove a user from an organization
-
-You can remove a user from an organization when they no longer require access to the dashboard or data sources owned by the organization. No longer requiring access to an organization might occur when the user has left your company or has internally moved to another organization.
-
-This action does not remove the user account from the Grafana server.
-
-## Before you begin
-
- Ensure you have organization administrator privileges
-
-**To remove a user from an organization**:
-
-1. Sign in to Grafana as an organization administrator.
-1. Hover your cursor over the **Configuration** (gear) icon in the side menu and click **Users**.
-1. Find the user account that you want to remove from the organization.
-
-   Use the search field to filter the list, if necessary.
-
-1. Click the red **X** to remove the user from the organization.
-
-> **Note:** If you have [server administrator]({{< relref "../about-users-and-permissions.md#grafana-server-administrators">}}) permissions, you can also [remove a user from an organization]({{< relref "../../manage-users-and-permissions/manage-server-users/add-remove-user-to-org.md#remove-a-user-from-an-organization" >}}) on the Users page of the Server Admin section.
--- a/docs/sources/administration/manage-users-and-permissions/manage-org-users/view-list-org-users.md
+++ b/docs/sources/administration/manage-users-and-permissions/manage-org-users/view-list-org-users.md
@@ -1,23 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/administration/manage-users-and-permissions/manage-org-users/view-list-org-users/
-title: View a list of organization users
-weight: 50
---
-
-# View a list of organization users
-
-You can see a list of users with accounts in your Grafana organization. If necessary, you can use the search field to filter the list.
-
-## Before you begin
-
- Ensure you have organization administrator privileges
-
-**To view a list of organization users**:
-
-1. Sign in to Grafana as an organization administrator.
-1. Hover your cursor over the **Configuration** (gear) icon in the side menu and click **Users**.
-
-![Org Admin user list](/static/img/docs/manage-users/org-user-list-7-3.png)
-
-> **Note:** If you have [server administrator]({{< relref "../about-users-and-permissions.md#grafana-server-administrators">}}) permissions, you can also [view a global list of users]({{< relref "../../manage-users-and-permissions/manage-server-users/view-list-users.md" >}}) in the Server Admin section of Grafana.
--- a/docs/sources/administration/manage-users-and-permissions/manage-server-users/_index.md
+++ b/docs/sources/administration/manage-users-and-permissions/manage-server-users/_index.md
@@ -1,20 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/manage-users/server-admin/
-  - /docs/grafana/latest/manage-users/server-admin/server-admin-manage-users/
-  - /docs/grafana/latest/administration/manage-users-and-permissions/manage-server-users/
-title: Manage users globally
-weight: 300
---
-
-# Manage users globally
-
-A _user_ is defined as any individual who can log in to Grafana. Each user is associated with a _role_ that includes _permissions_. Permissions determine the tasks a user can perform in the system.
-
-If you have [server administrator]({{< relref "../about-users-and-permissions.md#grafana-server-administrators">}}) permissions in Grafana, you can manage all users for a Grafana instance in the Server Admin section:
-
-{{< section >}}
-
-If you have [organization administrator]({{< relref "../about-users-and-permissions.md#organization-roles">}}) permissions and _not_ [server administrator]({{< relref "../about-users-and-permissions.md#grafana-server-administrators">}}) permissions, refer to [Manage users in a organization]({{< relref "../../manage-users-and-permissions/manage-org-users/_index.md" >}}).
-
-For more information about users and permissions, refer to [About users and permissions]({{< relref "../about-users-and-permissions">}}).
--- a/docs/sources/administration/manage-users-and-permissions/manage-server-users/add-remove-user-to-org.md
+++ b/docs/sources/administration/manage-users-and-permissions/manage-server-users/add-remove-user-to-org.md
@@ -1,52 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/administration/manage-users-and-permissions/manage-server-users/add-user-to-org/
-title: Add or remove a user from an organization
-weight: 30
---
-
-# Add a user to an organization
-
-Add a user to an organization when you want the user to have access to organization resources such as dashboards, data sources, and playlists. A user must belong to at least one organization.
-
-You are required to specify an Admin role for each organization. The first user you add to an organization becomes the Admin by default. After you assign the Admin role to a user, you can add other users to an organization as either Admins, Editors, or Viewers.
-
-## Before you begin
-
- [Create an organization]({{< relref "../../manage-organizations/_index.md">}})
- [Add a user]({{< relref "./add-user.md">}}) to Grafana
- Ensure you have Grafana server administrator privileges
-
-**To add a user to an organization**:
-
-1. Sign in to Grafana as a server administrator.
-1. Hover your cursor over the **Server Admin** (shield) icon until a menu appears, and click **Users**.
-1. Click a user.
-1. In the **Organizations** section, click **Add user to organization**.
-1. Select an organization and a role.
-
-   For more information about user permissions, refer to [Organization roles]({{< relref "../about-users-and-permissions/#organization-roles">}}).
-
-1. Click **Add to organization**.
-
-The next time the user signs in, they will be able to navigate to their new organization using the Switch Organizations option in the user profile menu.
-
-> **Note:** If you have [organization administrator]({{< relref "../about-users-and-permissions.md#organization-roles">}}) permissions and _not_ [server administrator]({{< relref "../about-users-and-permissions.md#grafana-server-administrators">}}) permissions, you can still [invite a user to join an organization]({{< relref "../../manage-users-and-permissions/manage-org-users/invite-user-join-org.md" >}}).
-
-# Remove a user from an organization
-
-Remove a user from an organization when they no longer require access to the dashboards, data sources, or alerts in that organization.
-
-## Before you begin
-
- Ensure you have Grafana server administrator privileges
-
-**To remove a user from an organization**:
-
-1. Sign in to Grafana as a server administrator.
-1. Hover your cursor over the **Server Admin** (shield) icon until a menu appears, and click **Users**.
-1. Click a user.
-1. In the **Organization** section, click **Remove from organization** next to the organization from which you want to remove the user.
-1. Click **Confirm removal**.
-
-> **Note:** If you have [organization administrator]({{< relref "../about-users-and-permissions.md#organization-roles">}}) permissions and _not_ [server administrator]({{< relref "../about-users-and-permissions.md#grafana-server-administrators">}}) permissions, you can still [remove a user from an organization]({{< relref "../../manage-users-and-permissions/manage-org-users/remove-user-from-org.md" >}}) in the Users section of organization configuration.
--- a/docs/sources/administration/manage-users-and-permissions/manage-server-users/add-user.md
+++ b/docs/sources/administration/manage-users-and-permissions/manage-server-users/add-user.md
@@ -1,29 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/administration/manage-users-and-permissions/manage-server-users/add-user/
-title: Add a user
-weight: 10
---
-
-# Add a user
-
-Add users when you want to manually provide individuals with access to Grafana.
-
-When you create a user using this method, you must create their password. The user does not receive a notification by email. To invite a user to Grafana and allow them to create their own password, [invite a user to join an organization]({{< relref "../manage-org-users/invite-user-join-org.md">}}).
-
-When you configure advanced authentication using Oauth, SAML, LDAP, or the Auth proxy, users are created automatically.
-
-## Before you begin
-
- Ensure that you have Grafana server administrator privileges
-
-**To add a user**:
-
-1. Sign in to Grafana as a server administrator.
-1. Hover your cursor over the **Server Admin** (shield) icon until a menu appears, and click **Users**.
-1. Click **New user**.
-1. Complete the fields and click **Create user**.
-
-When you create a user, the system assigns the user viewer permissions in a default organization, which you can change. You can now [add a user to a second organization]({{< relref "./add-remove-user-to-org.md">}}).
-
-> **Note:** If you have [organization administrator]({{< relref "../about-users-and-permissions.md#organization-roles">}}) permissions and _not_ [server administrator]({{< relref "../about-users-and-permissions.md#grafana-server-administrators">}}) permissions, you can still add users by [inviting a user to join an organization]({{< relref "../../manage-users-and-permissions/manage-org-users/invite-user-join-org.md" >}}).
--- a/docs/sources/administration/manage-users-and-permissions/manage-server-users/assign-remove-server-admin-privileges.md
+++ b/docs/sources/administration/manage-users-and-permissions/manage-server-users/assign-remove-server-admin-privileges.md
@@ -1,28 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/administration/manage-users-and-permissions/manage-server-users/assign-remove-server-admin-privileges/
-title: Assign or remove Grafana server administrator privileges
-weight: 20
---
-
-# Assign or remove Grafana server administrator privileges
-
-Grafana server administrators are responsible for creating users, organizations, and managing permissions. For more information about the server administration role, refer to [Grafana server administrators]({{< relref "../about-users-and-permissions/#grafana-server-administrators">}}).
-
-> **Note:** Server administrators are "super-admins" with full permissions to create, read, update, and delete all resources and users in all organizations, as well as update global settings such as licenses. Only grant this permission to trusted users.
-
-## Before you begin
-
- [Add a user]({{< relref "./add-user.md">}})
- Ensure you have Grafana server administrator privileges
-
-**To assign or remove Grafana administrator privileges**:
-
-1. Sign in to Grafana as a server administrator.
-1. Hover your cursor over the **Server Admin** (shield) icon until a menu appears, and click **Users**.
-1. Click a user.
-1. In the **Grafana Admin** section, click **Change**.
-1. Click **Yes** or **No**, depending on whether or not you want this user to have the Grafana server administrator role.
-1. Click **Change**.
-
-The system updates the user's permission the next time they load a page in Grafana.
--- a/docs/sources/administration/manage-users-and-permissions/manage-server-users/change-user-org-permissions.md
+++ b/docs/sources/administration/manage-users-and-permissions/manage-server-users/change-user-org-permissions.md
@@ -1,23 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/administration/manage-users-and-permissions/manage-server-users/change-user-org-permissions/
-title: Change a user's organization permissions
-weight: 50
---
-
-# Change a user's organization permissions
-
-Update organization permissions when you want to enhance or restrict a user's access to organization resources. For more information about organization permissions, refer to [Organization roles]({{< relref "../about-users-and-permissions/#organization-roles">}}).
-
-## Before you begin
-
- [Add a user to an organization]({{< relref "./add-remove-user-to-org.md">}})
- Ensure you have Grafana server administrator privileges
-
-**To change a user's organization permissions**:
-
-1. Sign in to Grafana as a server administrator.
-1. Hover your cursor over the **Server Admin** (shield) icon until a menu appears, and click **Users**.
-1. Click a user.
-1. In the **Organizations** section, click the role you want to change, and then select another role.
-1. Click **Update**.
--- a/docs/sources/administration/manage-users-and-permissions/manage-server-users/force-user-logout.md
+++ b/docs/sources/administration/manage-users-and-permissions/manage-server-users/force-user-logout.md
@@ -1,25 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/administration/manage-users-and-permissions/manage-server-users/force-user-logout/
-title: Force a user to logout from Grafana
-weight: 90
---
-
-# Force a user to log out of Grafana
-
-If you suspect a user account is compromised or is no longer authorized to access the Grafana server, then you can force the user to log out of Grafana.
-
-The force logout action can apply to one device that is logged in to Grafana, or all devices logged in to Grafana.
-
-## Before you begin
-
- Ensure you have Grafana server administrator privileges
-
-1. Sign in to Grafana as a server administrator.
-1. Hover your cursor over the **Server Admin** (shield) icon until a menu appears, and click **Users**.
-1. Click a user.
-1. Scroll down to the **Sessions** section.
-1. Perform one of the following actions:
-   - Click **Force logout** next to the session entry that you want logged out of Grafana.
-   - Click **Force logout from all devices**.
-1. Confirm the logout.
--- a/docs/sources/administration/manage-users-and-permissions/manage-server-users/grant-editor-admin-permissions.md
+++ b/docs/sources/administration/manage-users-and-permissions/manage-server-users/grant-editor-admin-permissions.md
@@ -1,31 +0,0 @@
---
-aliases:
-  - /docs/grafana/latest/administration/manage-users-and-permissions/manage-server-users/grant-editor-admin-permissions/
-title: Grant editors administrator permissions
-weight: 60
---
-
-# Grant editors administrator permissions
-
-By default, the editor organization role does not allow editors to manage dashboard folders, dashboards, and teams, which you can change by modifying a configuration parameter. You can allow them to do so using the `editors_can_admin` configuration option.
-
-This setting can be used to enable self-organizing teams to administer their own dashboards.
-
-When `editors_can_admin` is enabled:
-
- Users with the Editor role in an organization are Administrators for new dashboards and folders they create, meaning they can edit dashboard permissions. To learn more about dashboard permissions, refer to [Manage dashboard permissions]({{< relref "../manage-dashboard-permissions/_index.md" >}}).
- Users with the Editor role in an organization can create teams, and they are Administrators of the teams they create. To learn more about team permissions, refer to [Manage teams]({{< relref "../manage-teams/_index.md" >}})
-
-## Before you begin
-
- Ensure that you have access to the Grafana server
-
-**To enable editors with administrator permissions**:
-
-1. Log in to the Grafana server and open the Grafana configuration file.
-
-   For more information about the Grafana configuration file and its location, refer to [Configuration]({{< relref "../../../administration/configuration">}}).
-
-1. Locate the `editors_can_admin` parameter.
-1. Set the `editors_can_admin` value to `true`.
-1. Save your changes and restart the Grafana server.
--- a/Show More
+++ b/Show More