Grafana v5.0的新功能
這是Grafana有史以來最重大的更新。 本文將詳細介紹主要的新功能和增強功能。
- New Dashboard Layout Engine enables a much easier drag, drop and resize experience and new types of layouts.
● 新的儀表板布局引擎可以更輕松地拖放，調整體驗和新類型的布局。
- New UX. The UI has big improvements in both look and function.
● 新UX。 用戶界面在外觀和功能上都有很大的改進。
- New Light Theme is now looking really nice.
- 新燈主題現在看起來非常好。
- Dashboard Folders helps you keep your dashboards organized.
- 儀表板文件夾可幫助您保持儀表板的有序。
- Permissions on folders and dashboards helps manage larger Grafana installations.
- 文件夾和儀表板上的權限有助於管理較大的Grafana安裝。
- Group users into teams and use them in the new permission system.
- 將用戶分組並在新的權限系統中使用它們。
- Datasource provisioning makes it possible to setup datasources via config files.
- 數據源配置使得可以通過配置文件設置數據源。
- Persistent dashboard url’s makes it possible to rename dashboards without breaking links.
- 持久性儀表板網址可以在不中斷鏈接的情況下重命名儀表板。
- Graphite Tags & Integrated Function Docs.
- Graphite標簽和集成功能文檔。
Video showing new features
在官網上查看相關新功能動畫
New Dashboard Layout Engine
新的儀表盤布局引擎
The new dashboard layout engine allows for much easier movement and sizing of panels, as other panels now move out of the way in a very intuitive way. Panels are sized independently, so rows are no longer necessary to create layouts. This opens up many new types of layouts where panels of different heights can be aligned easily. Checkout the new grid in the video above or on the play site. All your existing dashboards will automatically migrate to the new position system and look close to identical. The new panel position makes dashboards saved in v5.0 incompatible with older versions of Grafana.
新的儀表板布局引擎允許更輕松地移動和調整面板大小，因為其他面板現在以非常直觀的方式移開。 面板的大小是獨立的，因此不再需要行來創建布局。 這打開了很多新的布局類型，其中不同高度的面板可以輕松對齊。 在上面的視頻或播放網站上簽出新的網格。 你現有的所有儀表板都將自動遷移到新位置系統，並且看起來接近完全相同。 新的面板位置使保存在v5.0中的儀表板與早期版本的Grafana不兼容。
New UX
Almost every page has seen significant UX improvements. All pages (except dashboard pages) have a new tab-based layout that improves navigation between pages. The side menu has also changed quite a bit. You can still hide the side menu completely if you click on the Grafana logo.
幾乎每個頁面都看到了重大的UX改進。 所有頁面（儀表板頁面除外）都有一個新的基於選項卡的布局，可改善頁面之間的導航。 側面菜單也發生了很大變化。 如果您點擊Grafana標記，你仍然可以完全隱藏側面菜單。
Dashboard Settings
儀表板設置
Dashboard pages have a new header toolbar where buttons and actions are now all moved to the right. All the dashboard settings views have been combined with a side nav which allows you to easily move between different setting categories.
儀表板頁面有一個新的標題欄，其中按鈕和操作現在全部移動到右側。 所有的儀表板設置視圖已經與側面導航相結合，可以讓您輕松地在不同的設置類別之間移動。
New Light Theme
新亮度主題
This theme has not seen a lot of love in recent years and we felt it was time to give it a major overhaul. We are very happy with the result.
這個主題近年來都不太受我們待見，我們覺得是時候給它一個重大的改革。 我們對結果非常滿意。
Dashboard Folders
儀表板文件夾
The big new feature that comes with Grafana v5.0 is dashboard folders. Now you can organize your dashboards in folders, which is very useful if you have a lot of dashboards or multiple teams.
Grafana v5.0附帶的新功能是儀表板文件夾。 現在我們可以將我們的儀表盤整理到文件夾中，在我們有很多儀表盤或多個團隊，這非常有用。
- New search design adds expandable sections for each folder, starred and recently viewed dashboards.
- 新的搜索設計為每個文件夾，加星標和最近查看的儀表板添加了可擴展部分
- New manage dashboard pages enable batch actions and views for folder settings and permissions.
- 新的管理儀表板頁面為文件夾設置和權限啟用批處理操作和視圖。
- Set permissions on folders and have dashboards inherit the permissions.
設置文件夾權限並讓儀表板繼承權限。
Teams
小組
A team is a new concept in Grafana v5. They are simply a group of users that can be used in the new permission system for dashboards and folders. Only an admin can create teams. We hope to do more with teams in future releases like integration with LDAP and a team landing page.
一個團隊是Grafana v5中的一個新概念。 它們是簡單的一組可用於儀表盤和文件夾新權限系統的用戶。 只有管理員可以創建團隊。 我們希望在未來的版本中與團隊一起做更多的事情，例如與LDAP集成和團隊着陸頁。
Permissions
權限
You can assign permissions to folders and dashboards. The default user role-based permissions can be removed and replaced with specific teams or users enabling more control over what a user can see and edit.
您可以為文件夾和儀表板分配權限。可以刪除默認的基於用戶角色的權限，並替換為特定的團隊或用戶，以更好地控制用戶可以查看和編輯的內容。
Dashboard permissions only limits what dashboards & folders a user can view & edit not which data sources a user can access nor what queries a user can issue.
儀表板權限僅限制用戶可以查看和編輯哪些儀表板和文件夾，而不是用戶可以訪問哪些數據源以及用戶可以發出什么查詢。
Provisioning from configuration
從配置文件配置
In previous versions of Grafana, you could only use the API for provisioning data sources and dashboards. But that required the service to be running before you started creating dashboards and you also needed to set up credentials for the HTTP API. In v5.0 we decided to improve this experience by adding a new active provisioning system that uses config files. This will make GitOps more natural as data sources and dashboards can be defined via files that can be version controlled. We hope to extend this system to later add support for users, orgs and alerts as well.
在之前的Grafana版本中，您只能使用API來配置數據源和儀表板。但是，這需要在開始創建儀表板之前運行該服務，並且還需要為HTTP API設置憑據。在v5.0中，我們決定通過添加一個使用配置文件的新主動配置系統來改善這種體驗。這將使GitOps更加自然，因為數據源和儀表板可以通過可以版本控制的文件來定義。我們希望擴展這個系統，以便稍后添加對用戶，組織和警報的支持。
Data sources
數據源
Data sources can now be setup using config files. These data sources are by default not editable from the Grafana GUI. It’s also possible to update and delete data sources from the config file. More info in the
data source provisioning docs
.
數據源現在可以使用配置文件進行設置。這些數據源在默認情況下不能從Grafana GUI進行編輯。也可以從配置文件更新和刪除數據源。數據源配置文檔中的更多信息。
Dashboards
儀表板
We also deprecated the [dashboard.json] in favor of our new dashboard provisioner that keeps dashboards on disk in sync with dashboards in Grafana’s database. The dashboard provisioner has multiple advantages over the old [dashboard.json] feature. Instead of storing the dashboard in memory we now insert the dashboard into the database, which makes it possible to star them, use one as the home dashboard, set permissions and other features in Grafana that expects the dashboards to exist in the database. More info in the
dashboard provisioning docs
我們還棄用了[dashboard.json]，轉而使用我們的新儀表板配置程序，該儀表板配置程序使儀表板磁盤上的數據與Grafana數據庫中的儀表板保持同步。與舊的[dashboard.json]功能相比，儀表板配置器具有多種優勢。我們現在不將儀表板存儲在內存中，而是將儀表板插入到數據庫中，這樣就可以將它們加上星號，將其用作主頁儀表板，在Grafana中設置權限和其他功能，以期望儀表板存在於數據庫中。儀表板配置文檔中的更多信息查看提供的文檔
Graphite Tags & Integrated Function Docs
Graphite標簽和集成功能文檔
The Graphite query editor has been updated to support the latest Graphite version (v1.2) that adds many new functions and support for querying by tags. You can now also view function documentation right in the query editor!
Graphite查詢編輯器已更新為支持最新的Graphite版本（v1.2），該版本添加了許多新功能並支持通過標簽進行查詢。 您現在也可以在查詢編輯器中查看功能文檔了！
閱讀關於Graphite Tag支持的更多信息。
Dashboard model, persistent url’s and API changes
儀表板模型，持久性URL和API更改
We are introducing a new unique identifier (uid) in the dashboard JSON model. It’s automatically generated if not provided when creating a dashboard and will have a length of 9-12 characters.
我們在儀表板JSON模型中引入了一個新的唯一標識符（uid）。 如果創建儀表板時未自動生成，並且長度為9-12個字符。
The unique identifier allows having persistent URL’s for accessing dashboards, sharing them between instances and when using
dashboard provisioning
. This means that dashboard can be renamed without breaking any links. We’re changing the url format for dashboards from /dashboard/db/:slug to /d/:uid/:slug. We’ll keep supporting the old slug-based url’s for dashboards and redirects to the new one for backward compatibility. Please note that the old slug-based url’s have been deprecated and will be removed in a future release.
唯一標識符允許擁有用於訪問儀表板的持久性URL，在實例之間和使用儀表板供應時共享它們。 這意味着儀表板可以重命名而不會破壞任何鏈接。 我們正在將儀表板的網址格式從/ dashboard / db /：slug更改為/ d /：uid /：slug。 我們將繼續支持舊的基於slug的網址的儀表板和重定向到新的向后兼容性。 請注意，舊的基於slug的url已被棄用，並將在未來的版本中刪除。
Sharing dashboards between instances becomes much easier since the uid is unique (unique enough). This might seem like a small change, but we are incredibly excited about it since it will make it much easier to manage, collaborate and navigate between dashboards.
在實例之間共享儀表板變得容易得多，因為uid是唯一的（足夠獨特）。 這看起來可能只是一個小小的改變，但我們對它感到非常興奮，因為它將使它在儀表板之間的管理，協作和導航變得更容易。
API changes
API改變
New uid-based routes in the dashboard API have been introduced to retrieve and delete dashboards. The corresponding slug-based routes have been deprecated and will be removed in a future release.
已引入儀表板API中新的基於uid的路線以檢索和刪除儀表板。 相應的基於段落的路線已被棄用，並將在未來版本中刪除。