Skip to content

Concepts

Service Description

Last updated: October 19, 2026


Summary

SysEleven Observability (OaaS) is a centrally managed observability service within the Secunet Cloud. The service collects and stores performance and operational data in the form of metrics and logs and makes this data available for analysis and visualization. Its purpose is to support oversight of service and resource operations and enable analysis over defined periods.

Data Categories

The following data categories are considered in the context of observability:

  • Logs: Text-based event records, for example including timestamps and contextual information.
  • Metrics: Structured time-series measurements collected at defined intervals.

Scope of Services & Objectives

  • Collection and retention of observability data
  • Collection and storage of metrics and logs.

  • Analysis

  • Queries and analyses covering time periods, incidents, and trends through the provided interfaces.

  • Access and use

  • Primarily intended to support self-service projects in which customers operate their own services, monitor resources, and troubleshoot issues.

  • Interfaces

  • Provision of the Mimir API for metrics and the Loki API for logs.

Service Features

Data Protection & Security

  • Tenant isolation: The technology used protects each customer's data against access by other tenants.
  • Encryption: Data is accessed exclusively through encrypted connections (data in transit). Stored data is also encrypted at rest.
  • Data location: All data processing and retention take place in German data centers.
  • Operating region: OaaS is operated within the HAM region (single-region operation). Cross-region operation of the service is currently outside the scope of service.

Compatibility & APIs

  • Provision of the Mimir API for metrics and the Loki API for logs.

Documentation & Open Source

  • Provision of detailed documentation for integration and use.
  • Use of open-source technologies; publicly available external documentation may also be used.

Data Retention

Collected data is retained for the following standard periods:

  • Metrics: 180 days.
  • Logs: 30 days.

Retention periods are configured centrally for each cluster. Requests to change data retention must be submitted through the Service Desk.

Backups

SysEleven does not create backups of the stored log and metric data. Data is replicated in the S3 Object Storage used by the service. This replication does not replace an independent backup.

If the customer requires additional backups, particularly outside the operating region (off-site backups), the customer must create these using the provided read interfaces and store them in a separate backup environment. The customer is responsible for setting up and operating these backups.


Service Levels (SLA/SLO)

Availability

  • 99.5% availability for SysEleven Observability.

Service Availability and Service Hours

  • The service is available 24/7 under the agreed SLA.
  • Installation, provisioning, troubleshooting, and changes are performed during service hours.¹ ²
  • Incident resolution: Incidents are handled through the communication and escalation channels established in the support plan. Resolution is provided on a best-effort basis. The SLA defines service availability and maintenance windows.
  • Maintenance work is not considered downtime when calculating availability.

Operations & Maintenance

  • Maintenance is generally performed monthly following the release of new vendor updates.
  • Maintenance may be announced at short notice if critical security vulnerabilities are identified.
  • At least 24 hours' notice is provided if a service interruption is expected.
  • Emergency maintenance, for example to defend against ongoing attacks, may be performed without prior notice.

Responsibilities (Shared Responsibility)

Responsibilities of SysEleven

  • Operate the centrally managed observability service at platform level under the agreed SLA and during the agreed service hours.
  • Ensure tenant isolation, including separation of customer data, and provide the access model.
  • Provide encrypted access channels for data use.
  • Operate data processing and retention in German data centers.
  • Operate the S3 replication described in the Backups section. Backups of log and metric data are outside the scope of service.
  • Perform regular maintenance, security maintenance, and emergency maintenance following the procedures described.
  • Provide incident resolution on a best-effort basis through the applicable communication and support processes.
  • Provide the service interfaces—the Mimir API for metrics and the Loki API for logs—and the associated documentation.
  • Handle service requests, for example for data deletion or changes to data retention, through the Service Desk.

Responsibilities of the Customer

  • Integrate and use the provided interfaces—the Mimir and Loki APIs—for queries, analysis, and visualization.
  • Configure, operate, and maintain the customer's own systems and services that supply observability data, such as data sources, exporters, and log sources.
  • Set up and operate any required additional backups, including off-site backups, using the provided read interfaces.
  • Interpret and analyze the data, for example to investigate trends and incidents and identify measures to optimize resources and costs.
  • Submit feature requests and service requests through the Service Desk.
  • Review and track the implementation of changes within the customer's area of responsibility, such as changes to data sources, dashboards, and queries.
  • Ensure that internal procedures and access controls are followed within the customer's area of responsibility, for example when handling credentials or tokens, where applicable.

Pricing & Billing

Usage-Based Pricing Model

Observability as a Service is billed on a usage basis (pay-per-use). The standard model has no fixed monthly base fee.

Billing distinguishes between four types of data processing usage:

Billing Item Billing Basis
Metrics Ingest Number of collected metric samples.
Metrics Query Amount of metric data retrieved for queries, according to the defined billing unit.
Logs Ingest Amount of log data received before compression.
Logs Query Amount of log data retrieved for queries, according to the documented measurement.

Data ingestion and queries are billed separately. Query charges are based on the measured amount of data according to the relevant billing unit; the number of individual queries is not billed separately. Automated queries, such as those triggered by regularly refreshed dashboards, may also generate billable usage.

Data Retention and Storage Charges

The standard retention period is 180 days for metrics and 30 days for logs.

The Object Storage used to retain metric and log data is billed separately from the ingestion and query charges, according to the applicable price list. Storage costs are not included in the ingestion or query prices.

Billing and Units

Usage is recorded per tenant and region for each calendar month and billed monthly in arrears.

Partial billing units for ingestion and queries are charged proportionally and are not rounded up to whole units. The standard model uses fixed prices per billing unit for these processing charges, without automatic volume-based pricing tiers.

Storage is billed according to the measurement and calculation rules applicable to the relevant Object Storage item in the price list.

Log data volumes are measured in gibibytes (GiB). One GiB equals 1,073,741,824 bytes.

The applicable billing units and prices are specified in the current price list.


Support & Availability

  • Support plan: Self-Service, including product and platform support as defined in the support plan.
  • Service availability: 24/7.
  • Incident resolution: Best effort; escalation channels are defined in the support plan.
  • Engineering services not included in support are billed based on time spent at the applicable hourly rates.

Roadmap & Changes

We continuously develop and improve the OaaS service. Information about planned features and enhancements is provided through the product roadmap.

The current roadmap is available here:

Observability Roadmap


Only the terms set out in the applicable General Terms and Conditions (AGB), SLA, and price list are binding. This service description sets out the product-level scope of service and may change. Regional availability and feature sets may vary.


Disclaimer

This service relies on open-source software. The nature and scope of the service follow the capabilities of the underlying software and may change as that software evolves.

We continuously improve our products and services. Implementation changes may occur as a result of technical advancements, provided they do not materially change the functionality of the product or service. Errors and omissions excepted.

Feedback about services or documentation is welcome: produktfeedback@syseleven.de.


Footnotes

  1. Support availability: Working days, excluding public holidays in Berlin, from 09:00 to 17:00 at +49 30 233 2012 30.
  2. Outside service hours: Emergency contact at +49 30 609 89 22 11 (voicemail).