Observability (logs/metrics/traces, alerting)

Why important?

Without logs, metrics and tracing, operations, security monitoring and troubleshooting hardly scale. Observability is a core building block for regulated workloads.

How measured?

• 0 = No or very little observability
• 1 = Basic logs/metrics, no traces/integration
• 2 = Partial observability, gaps in integration/export
• 3 = Good observability for the core scope + export/integration possible
• 4 = Strong observability suite + governance/retention/export well documented
• 5 = Comprehensive + mature + verifiably evidenced (incl. security/compliance requirements)
• N/A = no reliable evidence

Sources / Evidence

• https://docs.ionos.com/cloud/observability/logging-service
• https://docs.ionos.com/cloud/observability/monitoring-service
• https://docs.ionos.com/cloud/observability/activity-logs
• https://docs.stackit.cloud/products/logging-and-monitoring/observability/
• https://docs.stackit.cloud/products/logging-and-monitoring/logs/
• https://www.scaleway.com/en/security-and-resilience/
• https://docs.syseleven.de/syseleven-stack/en/reference/get-quota-info
• https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits

Validation questions (RFP)

• Is end-to-end tracing available? Which retention/export options exist (e.g. bulk export)? IAM/RBAC on telemetry? Audit logs for configuration changes?

Scores comparison