Sync service maturity manifest

This MR is automatically generated by Scalability team, as a part of maturity model automation project.

The service maturity model page shows the output of our service maturity model for each service in our metrics catalog. The model itself is part of the metrics catalog, and uses information from the metrics catalog and the service catalog to score each service. The purpose of this MR is to re-compute and sync the manifest from the runbook.

Significant changes

• ci-runners

  • ✅ Level 2 → Level 3
  • ✅ Apdex built from multiple sources: failed → passed

• redis-sessions

  • ✅ Not exist → Level 0
  • ✅ Exists in the service catalog: Not exist → passed
  • ✅ Structured logs available in Kibana: Not exist → passed
  • ❌ Service exists in the dependency graph: Not exist → failed
  • ✅ SLO monitoring: apdex: Not exist → passed
  • ✅ SLO monitoring: error rate: Not exist → passed
  • ✅ SLO monitoring: request rate: Not exist → passed
  • ❌ Service health dashboards: Not exist → unimplemented
  • ❌ SLA calculations driven from SLO metrics: Not exist → unimplemented
  • ❌ Apdex built from multiple sources: Not exist → failed
  • ❌ Logging includes metadata for measuring scalability: Not exist → unimplemented
  • ❌ Developer guides exist in developer documentation: Not exist → unimplemented
  • ✅ SRE guides exist in runbooks: Not exist → passed
  • ❌ Metrics on downstream service usage: Not exist → unimplemented
  • ❌ Prepared Kibana dashboards: Not exist → unimplemented
  • ❌ Dashboards linked from metrics catalogs: Not exist → unimplemented
  • ❌ Automatic alert routing: Not exist → unimplemented
  • ❌ Long-term forecasting utilization and usage: Not exist → unimplemented
  • ❌ 70% of requests covered by at least one SLI: Not exist → unimplemented

• search

  • ✅ Level 0 → Level 1
  • ✅ Structured logs available in Kibana: failed → passed

• woodhouse

  • ✅ Level 0 → Level 3
  • ✅ Structured logs available in Kibana: failed → skipped