Skip to Content

Changes for page Grafana

Last modified by Peter Wurbs on 2025/05/07 11:36
From version 32.2
edited by Peter Wurbs
on 2025/04/14 12:07
Change comment: There is no comment for this version
To version 26.1
edited by Peter Wurbs
on 2025/04/10 09:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -22,7 +22,7 @@
22 22  = Accessing Grafana =
23 23  
24 24  * Grafana as part of the DevOps-as-a-Service toolchain can be accessed by either
25 -** DevOps Portal Homepage → Grafana Tile
25 +** DevOps Portal Homepage ~-~-> Grafana Tile
26 26  [[image:1744266164249-840.png]]
27 27  ** or directly use the URL [[https:~~/~~/grafana-<customer~>.devops.t-systems.net>>https://grafana-<customer>.devops.t-systems.net]]
28 28  * Preconditions in DevOps portal to access Grafana:
... ... @@ -32,17 +32,10 @@
32 32  * When you see this message after entering your credentials, then you don't have a Grafana license assigned in the DevOps portal:
33 33  [[image:1744266590219-161.png||height="242" width="293"]]
34 34  
35 -= Users, Projects and Roles =
35 += Users, Projects, Organizations and Roles =
36 36  
37 37  * Projects, users and their roles in projects are managed in the DevOps portal, the corresponding functions in Grafana are disabled (UI and API)
38 -
39 -(% class="box warningmessage" %)
40 -(((
41 -⚠ **Note**
42 -Projects in DevOps portal are mapped to Grafana.
43 -)))
44 -
45 -* 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.
38 +* 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.
46 46  ** Role mapping: (((
47 47  |=Project Role in DevOps Portal|=Grafana Organization Role|=Permissions in Grafana
48 48  |Viewer|Viewer|Can view dashboards and alerts
... ... @@ -54,14 +54,9 @@
54 54  * 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.
55 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.
56 56  * 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.
50 +**When you work in Grafana, always make sure that you chose the intended Organization.**
57 57  [[image:1744272203893-682.png||height="272" width="255"]]
58 58  
59 -(% class="box warningmessage" %)
60 -(((
61 -⚠ **Note**
62 -When you work in Grafana, always make sure that you chose the intended Organization.
63 -)))
64 -
65 65  = Main Functions =
66 66  
67 67  == Datasources ==
... ... @@ -69,13 +69,10 @@
69 69  * Before you can setup dashboards and alerts, you have to setup datasources. Grafana itself is only a visualization tool, for data gathered via datasources.
70 70  * Datasources are created/managed per Grafana Organization.
71 71  * The Admin role is required to setup and manage datasources.
72 -
73 -(% class="box warningmessage" %)
60 +* (% class="box warningmessage" %)
74 74  (((
75 -⚠ **Note**
76 76  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.
77 77  )))
78 -
79 79  * Most common datasources are configured for
80 80  ** Prometheus to visualize metrics
81 81  ** Loki to search and visualize logs
... ... @@ -134,11 +134,7 @@
134 134  ** Click on folder "DevOps-as-a-Service Metrics"
135 135  ** Choose the dashboard you want to see
136 136  ** [[image:1744278056971-203.png||height="285" width="826"]]
137 -** Alternatively, you can use the link in the "Useful Links" panel of the Grafana Home page.
138 -[[image:1744285635938-113.png||height="127" width="350"]]
139 -
140 -(% class="box warningmessage" %)
122 +* (% class="box infomessage" %)
141 141  (((
142 - ⚠ **Note**
143 143  Every user assigned a Grafana license in the DevOps portal is able to access them, independent of any project assignment.
144 144  )))
1744285635938-113.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.peterwurbst-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -16.0 KB
Content
© 2018-2025 T-Systems International GmbH