Skip to content

Commit 8a084b4

Browse files
authored
Merge pull request #206 from ESA-APEx/grafana_docs
grafana: added docs
2 parents fcb5d5e + 63acbcc commit 8a084b4

5 files changed

Lines changed: 92 additions & 0 deletions

File tree

‎_quarto.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,8 @@ website:
9191
- section: Admin Guides
9292
contents:
9393
- href: guides/account.md
94+
- href: guides/grafana_monitoring.md
95+
text: Grafana monitoring dashboards
9496
- href: guides/custom_domain.md
9597
text: Custom domains for your project environment
9698
- href: guides/geospatial_explorer/index.qmd

‎guides/grafana_monitoring.md‎

Lines changed: 88 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,88 @@
1+
---
2+
title: Grafana Monitoring Dashboards
3+
---
4+
5+
## Overview
6+
7+
APEx provides Grafana dashboards for project-level operational monitoring.
8+
The Grafana instance for each project follows this URL pattern:
9+
10+
- `https://grafana.<project>.apex.esa.int/`
11+
12+
Example:
13+
14+
- [https://grafana.demo.apex.esa.int/](https://grafana.demo.apex.esa.int/)
15+
16+
This guide explains how to access the dashboards and what information is available.
17+
18+
## Access and Authentication
19+
20+
To access Grafana:
21+
22+
1. Open your project URL, for example `https://grafana.demo.apex.esa.int/`.
23+
2. Select **Sign in with APEx SSO** on the Grafana login page.
24+
3. Complete authentication using your APEx account.
25+
26+
If you do not yet have an APEx account, follow the
27+
[Creating an APEx account guide](account.md).
28+
29+
Note that having an APEx account is required but not sufficient on its own.
30+
Your account must also be explicitly authorised for the target project environment.
31+
32+
If authentication succeeds but you do not see your project dashboards,
33+
request environment access through APEx support.
34+
35+
## Available Dashboards
36+
37+
Two dashboards are available for day-to-day operational monitoring:
38+
39+
- **Ingress list**
40+
- **Project monitoring**
41+
42+
### Ingress list dashboard
43+
44+
The Ingress list dashboard provides a quick inventory of exposed endpoints
45+
for your namespace/project.
46+
47+
Main capabilities:
48+
49+
- Lists ingress host names currently configured for the selected project.
50+
- Shows which application each host name routes to.
51+
- Supports filtering by datasource, namespace, ingress name, and project name.
52+
- Supports standard Grafana time-window filtering for recent changes.
53+
54+
Use this dashboard when you need to:
55+
56+
- confirm the public host name of a deployed service,
57+
- verify whether a specific endpoint exists,
58+
- cross-check which component is behind a given ingress host.
59+
60+
![Grafana Ingress list dashboard](./images/grafana_ingress_list.png)
61+
62+
### Project monitoring dashboard
63+
64+
The Project monitoring dashboard provides workload health and usage indicators
65+
for core deployed components in the project namespace.
66+
67+
Main capabilities:
68+
69+
- CPU usage trends per component.
70+
- Memory usage trends per component.
71+
- Container readiness overview.
72+
- Restart counters to detect instability.
73+
- Per-project filtering to focus on one environment.
74+
75+
Use this dashboard when you need to:
76+
77+
- check whether services are healthy and ready,
78+
- identify resource pressure (CPU or memory growth),
79+
- investigate recurring restarts,
80+
- validate platform state during incident triage.
81+
82+
![Grafana Project monitoring dashboard](./images/grafana_project_monitoring.png)
83+
84+
## Tips
85+
86+
- Start with **Ingress list** to validate endpoint routing.
87+
- Continue with **Project monitoring** to inspect runtime health.
88+
- Keep the dashboard time range aligned with the time of an observed issue.
135 KB
Loading
328 KB
Loading

‎instantiation/index.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,8 @@ The specific components of the APEx Project Environments include:
5959
Supporting customisation and interactive visualisation using the Quarto framework.
6060
* [**User Forum**](forum.md)\
6161
Providing a community-building platform based on the open-source software Discourse.
62+
* [**Grafana Monitoring Dashboards**](../guides/grafana_monitoring.md)\
63+
Providing operational visibility into project ingress endpoints and runtime component health.
6264

6365
The APEx Project Environments will be essential for ensuring that the results of EO projects are effectively shared and
6466
utilised, fostering greater collaboration and innovation within the EO community. By providing robust, scalable, and

0 commit comments

Comments
 (0)