The Status Page API is part of the ARGO Monitoring Service, developed and maintained by GRNET.
It provides REST endpoints for creating, updating, and displaying service status pages, integrating with ARGO’s monitoring reports and data sources.
The API allows authenticated users to manage status pages and groups, while relying on Keycloak for authentication and access control.
The Status Page API enables:
- Management of Status Pages (create, list, update, delete)
- Retrieval of Status Groups and Reports from ARGO Monitoring
- Configuration of Public Status Pages for external visibility
- Management of User Profiles linked with Keycloak identities
This project is a REST API built with Quarkus and Maven, following a modular architecture and the service–repository pattern.
-
api
Exposes REST endpoints for client interaction. -
dto
Defines Data Transfer Objects used between API and service layers. -
entity
Contains ORM entities representing database tables. -
enum
Contains enumeration definitions used across the API. -
exception
Defines custom exceptions used throughout the application. -
handler
Centralizes error handling and exception mapping. -
mapper
Uses MapStruct for entity-to-DTO conversions. -
repository
Provides data access logic and database queries. -
service
Contains the business logic of the API. -
util
Contains utility classes and helpers such as configuration utilities.
All protected resources require authentication through Keycloak.
Clients must include a Bearer token in each request to access restricted endpoints.
Since the API’s endpoints must only be accessible to verified clients, every client who wants to access the API must be authenticated.
Communication with protected endpoints is performed using Bearer Authentication — a token-based authentication method commonly used in HTTP APIs.
Include the access token in your HTTP requests using the Authorization header:
Authorization: Bearer {{token}}
The ARGO Mon Status Pages API allows users to obtain an access token for authentication purposes.
By following these steps, users can retrieve an access token to authenticate API requests.
-
Open the Web Page
Navigate to the ARGO Mon Status Pages API page. -
Locate the Access Token Button
Once the page loads, locate the button that retrieves the access token. -
Click the “Obtain an Access Token” Button
Clicking this button initiates the retrieval process from the authentication server. -
Provide Required Information
Choose your preferred identity provider and log in with your credentials. -
Retrieve the Access Token
After successful authentication, the token will appear on the page. -
Use the Access Token
Include it in your API requests as described above.
Ensure the following software is installed on your development environment:
- Java Development Kit (JDK) 17
- Apache Maven 3.9
- Docker
After cloning the repository, navigate to the root directory and execute:
mvn clean install -DskipTests=true -UThis command installs all required dependencies in your local Maven repository.
To launch the application in development mode:
mvn clean quarkus:devThis will start the API along with supporting services (PostgreSQL, Keycloak, etc.) using Quarkus Dev Services.
Connect to the automatically started PostgreSQL instance using:
psql -h localhost -U status -d statusDefault development password:
status
Or connect directly inside the running container:
docker exec -it <container_id> psql -U status -d statusTo get a development token, follow the Quarkus guide
or access the Keycloak instance automatically launched by Dev Services.
Default credentials:
- Username:
alice - Password:
alice
Once logged in, copy the Access Token and include it in API requests.
ARGO Mon Status Pages is a service developed and maintained by GRNET.
Distributed under the Apache 2.0 License.