Changes for page Grafana

Last modified by Peter Wurbs on 2025/05/07 11:36

From version 36.1
edited by Peter Wurbs
on 2025/04/14 12:27
Change comment: Review with Boris
To version 33.1
edited by Peter Wurbs
on 2025/04/14 12:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -42,18 +42,17 @@
42 42  Projects in DevOps portal are mapped to Grafana Organizations. These are not related to the organizations in the portal.
43 43  )))
44 44  
45 -* When there is a new project in the portal having Grafana as a configured tool, then there is a new Grafana Organization. Users assigned to a project in the portal are then assigned to a Grafana Organization applying the configured roles.
45 +* When there is a new project in the portal having Grafana as a configured tool, then there is a new Grafana "Org". Users assigned to a project in the portal are then assigned to a Grafana Org applying the configured roles.
46 46  ** Role mapping: (((
47 -(% class="active" %)|=Project Role in DevOps Portal|=Grafana Organization Role|=Permissions in Grafana
48 -|Admin|Admin|Has full permissions within the Grafana org, e.g. can setup datasources, manage folders, teams and service accounts
49 -|Master|(% colspan="1" rowspan="2" %)Editor|(% colspan="1" rowspan="2" %)Can create/edit dashboards and alerts and use the Explore function
50 -|Developer
47 +|=Project Role in DevOps Portal|=Grafana Organization Role|=Permissions in Grafana
51 51  |Viewer|Viewer|Can view dashboards and alerts
49 +|Developer / Master|Editor|Can create/edit dashboards and alerts and use the Explore function
50 +|Admin|Admin|Has full permissions within the Grafana org, e.g. can setup datasources, manage folders, teams and service accounts
52 52  
53 53  A detailed description of the Grafana role model can be found [[here>>https://grafana.com/docs/grafana/latest/administration/roles-and-permissions/]].
54 54  )))
55 55  * There is an additional permission management possible on folder level. A folder contains a set of dashboards. A project admin can create folders and manage specific permissions for this folder using Grafana. See this [[link >>https://grafana.com/docs/grafana/latest/dashboards/manage-dashboards/#create-a-dashboard-folder]]for further information. Folder permissions management is out of scope of the user management in the DevOps portal.
56 -* A project admin is entitled to create and manage "Service Accounts" in Grafana and grant permissions in the specific organization. A Service Account belongs to an Organization and not to an user. Service Accounts can be used for systems which want to work wit the Grafana API for any automation purposes. See this [[link >>https://grafana.com/docs/grafana/latest/administration/service-accounts/]]for further information. Service Account management is done directly in Grafana and is out of scope of the user management in the DevOps portal. This function is comparable with the Technical Users feature in the DevOps portal.
55 +* A project admin is entitled to create and manage "Service Accounts" in Grafana and grant permissions in the specific organization. A Service Account belongs to an Organization (Project) and not to an user. Service Accounts can be used for systems which want to work wit the Grafana API for any automation purposes. See this [[link >>https://grafana.com/docs/grafana/latest/administration/service-accounts/]]for further information. Service Account management is done directly in Grafana and is out of scope of the user management in the DevOps portal.
57 57  * If you are assigned to more than one project in the DevOps portal, having Grafana configured as tool, then you can switch between Organizations in Grafana. Go to the top left corner, click on the Org list and select any other Grafana Organization (project), you want to switch to.
58 58  [[image:1744272203893-682.png||height="272" width="255"]]
59 59  
... ... @@ -77,13 +77,12 @@
77 77  When a datasource is available in an Organization, every user assigned to this Organization (Project) with Admin or Edit role can access/explore the data provided by this datasource.
78 78  )))
79 79  
80 -* Most common datasources are available for
79 +* Most common datasources are configured for
81 81  ** Prometheus to visualize metrics
82 82  ** Loki to search and visualize logs
83 83  ** MySQL, PostgreSQL to access and visualize database data
84 -** ...
85 85  * Many possible datasource types are preinstalled as built-in plugins and can be used
86 -* Datasource are set up via Menu panel → Connections → Datasources
84 +* Datasource are set up via Menu panel ~-~-> Connections ~-~-> Datasources
87 87  [[image:1744273328067-517.png||height="273" width="222"]]
88 88  * Detailed information can be found via this [[link>>https://grafana.com/docs/grafana/latest/datasources/]].
89 89  
... ... @@ -102,9 +102,9 @@
102 102  
103 103  * Dashboards are the way to visualize metrics, logs and other data.
104 104  * Dashboards are a collection of "Panels". Each panel is of a specific type (stat, time series, table, log...). Many Panel Plugins are preinstalled and can be used.
105 -* Data is displayed based on queries which are the main part of a panel configuration.
103 +* Data are displayed based on queries which are the main part of a panel configuration.
106 106  * Dashboards can be created and edited by users owning the Editor or Admin role
107 -* "Dashboard" function can be found in the Menu panel
105 +* "Dashboard" function can be in the Menu panel
108 108  * There is a good [[guideline >>https://grafana.com/docs/grafana/latest/getting-started/build-first-dashboard/]]about the first steps.
109 109  * Detailed information can be found via this [[link>>https://grafana.com/docs/grafana/latest/dashboards/build-dashboards/]].
110 110