Changes for page Grafana

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -53,7 +53,7 @@
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 (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.
	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.
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,12 +77,13 @@
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 configured for
	80	+* Most common datasources are available 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	+** ...
84	84	* Many possible datasource types are preinstalled as built-in plugins and can be used
85		-* Datasource are set up via Menu panel ~-~-> Connections ~-~-> Datasources
	86	+* Datasource are set up via Menu panel → Connections → Datasources
86	86	[[image:1744273328067-517.png||height="273" width="222"]]
87	87	* Detailed information can be found via this [[link>>https://grafana.com/docs/grafana/latest/datasources/]].
88	88
...	...	@@ -101,7 +101,7 @@
101	101
102	102	* Dashboards are the way to visualize metrics, logs and other data.
103	103	* 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.
104		-* Data are displayed based on queries which are the main part of a panel configuration.
	105	+* Data is displayed based on queries which are the main part of a panel configuration.
105	105	* Dashboards can be created and edited by users owning the Editor or Admin role
106	106	* "Dashboard" function can be in the Menu panel
107	107	* There is a good [[guideline >>https://grafana.com/docs/grafana/latest/getting-started/build-first-dashboard/]]about the first steps.