Service Certificate – STACKIT Argus
Service Name
STACKIT Argus
High level service description
STACKIT Argus („Argus”) is a managed service, which provides the customer with a high-performance observability toolset. Argus can observe Targets that provide data in an OpenTelemetry format. Telemetry data (metrics, logs and traces) can be sent to Argus. For metrics, retrieval is also possible. All telemetry data can be visualized and seen by the customer in an adapted dashboard using different types of diagram. An alarm system is also integrated; the system can notify user groups via various communication channels as soon as a threshold value, defined by the customer, is exceeded.
Key Features
- Customer systems and applications for monitoring can be added via a user-friendly configuration screen such as the STACKIT Argus API
- All dashboards are easy to create and use and are highly adaptable
- Long-term storage (see service plans) for monitoring system and application data
- As soon as user-defined alarms are triggered, the customer can be notified via several pre-determined communication channels
- Pre-configured auto-update functions keep components up-to-date
Service Plans
Within the framework of the order, the customer has the option to choose from different service configurations. These mainly differ in their performance capabilities or storage capacity.
Service Plan | Frontend | Monitoring | Monitoring | Monitoring | Monitoring | Monitoring | Monitoring |
---|---|---|---|---|---|---|---|
Starter | Starter | Basic | Medium | Large | XL | XXL | |
Metric Limits | Metric Limits | Metric Limits | Metric Limits | Metric Limits | Metric Limits | Metric Limits | Metric Limits |
Metric values per minute | 0 | 5.000 | 30.000 | 100.000 | 300.000 | 150,0000 | 300,0000 |
Storage in days | 0 | 780 | 780 | 780 | 780 | 780 | 780 |
Alerting Limits | Alerting Limits | Alerting Limits | Alerting Limits | Alerting Limits | Alerting Limits | Alerting Limits | Alerting Limits |
Notification rules | 0 | 10 | 50 | 100 | 200 | 400 | 800 |
Receivers1 | 0 | 5 | 10 | 50 | 100 | 100 | 100 |
Matchers2 | 0 | 5 | 10 | 50 | 100 | 100 | 100 |
Frontend Limits | Frontend Limits | Frontend Limits | Frontend Limits | Frontend Limits | Frontend Limits | Frontend Limits | Frontend Limits |
Users | 5 | 5 | 30 | 100 | 100 | 200 | 200 |
Logs Limits | Logs Limits | Logs Limits | Logs Limits | Logs Limits | Logs Limits | Logs Limits | Logs Limits |
Size (GB) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Storage in days | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Traces Limits | Traces Limits | Traces Limits | Traces Limits | Traces Limits | Traces Limits | Traces Limits | Traces Limits |
Size (GB) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Storage in days | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Service Plan | Observability | Observability | Observability | Observability |
---|---|---|---|---|
Starter | Basic | Medium | Large | |
Metric Limits | Metric Limits | Metric Limits | Metric Limits | Metric Limits |
Metric values per minute | 5.000 | 30.000 | 100.000 | 300.000 |
Storage in days | 780 | 780 | 780 | 780 |
Alerting Limits | Alerting Limits | Alerting Limits | Alerting Limits | Alerting Limits |
Notification rules | 10 | 50 | 100 | 200 |
Receivers1 | 5 | 10 | 50 | 100 |
Matchers2 | 5 | 10 | 50 | 100 |
Logs Limits | Logs Limits | Logs Limits | Logs Limits | Logs Limits |
Size (GB) | 50 | 200 | 400 | 1.000 |
Storage in days | 30 | 30 | 30 | 30 |
Traces Limits | Traces Limits | Traces Limits | Traces Limits | Traces Limits |
Size (GB) | 50 | 200 | 400 | 1.000 |
Storage in days | 30 | 30 | 30 | 30 |
1Receiver: A Receiver is a communication channel for an alarm. Different communication channels, such as Webhook, email, Microsoft Teams and Atlassian Opsgenie, can be configured.
2Matcher: A Matcher determines to which Receiver an alarm is transmitted.
Metric
- Billing per Argus service customer commissioned by the customer and per hour commenced
SLA Specifics
- Argus is considered available as long as the Frontend and the telemetry data (metrics, logs and traces) are accessible for the Argus service at the service transfer point.
Backup
There is no backup of telemetry data (metrics, logs and traces). Argus configuration files and dashboards are backed up automatically according to a schedule specified by STACKIT in accordance with the general service description of the STACKIT Cloud. This schedule cannot be changed by the customer. However, customers have the possibility to restore created backups.
Additional Terms
- The customer is responsible for the configuration of Argus (in particular the management of accounts, visibilities and alerts)
- The following conditions also apply:
- https://github.com/prometheus/prometheus/blob/main/LICENSE (Apache License 2.0)
- https://github.com/prometheus/alertmanager/blob/main/LICENSE (Apache License 2.0)
- https://github.com/thanos-io/thanos/blob/main/LICENSE (Apache License 2.0)
- https://github.com/grafana/loki/blob/main/LICENSE (GNU Affero General Public License v3.0)
- https://github.com/grafana/tempo/blob/main/LICENSE (GNU Affero General Public License v3.0)