New Engineer Onboarding

Welcome to the Observability Platform Team! This guide provides a practical path through the service and its repositories.

Week 1: Getting Started

• Request Grafana and Splunk access through the Operations guides.
• Read the Platform Architecture, Inventory, Monitoring, Logging, and Alerting overviews.
• Learn the difference between inventory scope, expected audit coverage, and live telemetry health.
• Shadow one NOC/TAC incident and reproduce its Grafana and Splunk evidence.

Week 2: Understanding the Stack

Choose a mature device category such as CUCM and trace it end to end:

1. Source and generated target inventory.
2. Device audit YAML.
3. Prometheus/exporter deployment configuration.
4. Mimir/Grafana dashboards and alerts.
5. Splunk syslog/CDR/trap evidence.
6. EMS notification routing.

Week 3: First Contribution

Make a low-risk documentation, audit, or test improvement. Start from current main, produce before/after evidence, request domain review, and observe deployment verification. Avoid using a first contribution for broad production routing, credentials, or target generation changes.

Key Contacts

Team rosters and escalation contacts change frequently. Use the approved internal ownership/on-call system rather than copying names or phone numbers into this public repository.

Resources

• Device inventory
• Monitoring
• Logging
• Alerting
• Operations guide
• observability-audit