Changes for page Grafana

Summary

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

Details

Page properties

Content

...	...	@@ -19,25 +19,28 @@
19	19
20	20	= Accessing Grafana =
21	21
22		-Grafana as part of the DevOps-as-a-Service toolchain can be accessed by either
23		-
24		-* DevOps Portal Homepage ~-~-> Grafana Tile
	22	+* Grafana as part of the DevOps-as-a-Service toolchain can be accessed by either
	23	+** DevOps Portal Homepage ~-~-> Grafana Tile
25	25	[[image:1744266164249-840.png]]
26		-* or directly use the URL [[https:~~/~~/grafana-<customer~>.devops.t-systems.net>>https://grafana-<customer>.devops.t-systems.net]]
27		-
28		-A Grafana license must be assigned to the user in the DevOps portal to see the Grafana tile resp. to get access to Grafana.
29		-
30		-If you are not already logged in to another tool in the toolchain, then you have to login using your configured SSO credentials.
31		-
32		-If you see this message after entering your credentials, then you don't have a Grafana license assigned in the DevOps portal:
33		-
	25	+** or directly use the URL [[https:~~/~~/grafana-<customer~>.devops.t-systems.net>>https://grafana-<customer>.devops.t-systems.net]]
	26	+* A Grafana license must be assigned to the user in the DevOps portal to see the Grafana tile resp. to get access to Grafana.
	27	+* If you are not already logged in to another tool in the toolchain, then you have to login using your configured SSO credentials.
	28	+* When you see this message after entering your credentials, then you don't have a Grafana license assigned in the DevOps portal:
34	34	[[image:1744266590219-161.png||height="242" width="293"]]
35	35
36	36	= Users, Projects, Organizations and Roles =
37	37
38		-* Projects, Users, their roles
	33	+* Projects, users and their roles in projects are managed in the DevOps portal, the corresponding functions in Grafana are disabled (UI and API)
39	39	* Projects in DevOps portal are mapped to Organizations in Grafana. This means, 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.
40		-*
41		-*
	35	+** Role mapping: (((
	36	+|=Project Role in DevOps Portal|=Grafana Organization Role|=Permissions in Grafana
	37	+|Viewer|Viewer|Can view dashboards and alerts
	38	+|Developer / Master|Editor|Can create/edit dashboards and alerts and use the Explore function
	39	+|Admin|Admin|Has full permissions within the Grafana org, e.g. can setup datasources, manage folders, teams and service accounts
42	42
	41	+A detailed description of the Grafana role model can be found [[here>>https://grafana.com/docs/grafana/latest/administration/roles-and-permissions/]].
	42	+)))
	43	+* 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.
	44	+* 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.
	45	+
43	43