Running Backstage day to day: metrics and traces, health checks, backups, and fixing the catalog, sign-in, scaffolder and configuration errors teams hit most.
Instrumenting the backend: the instrumentation file, Prometheus metrics and OTLP traces, histogram units, the catalog and scaffolder metrics worth alerting on, and shipping the setup in the Docker image.
Finding why an entity is missing, stale or broken: processing errors attached to entities, location and provider failures, rejected kinds, orphans and the processing loop.
Diagnosing 'not configured to support sign-in' and 'unable to resolve user identity', resolver mismatches, missing org data, and checking configuration with config:check.
What needs backing up when catalog files live in Git: the PostgreSQL databases per plugin, scaffolder task history, TechDocs storage and configuration, and testing a restore.
Enabling health checks, wiring readiness and liveness probes to /healthcheck, startup time for large catalogs and avoiding restart loops.
Reading step logs, common publish and permission failures, cancelling and re-running tasks with Start Over, and making failing actions easier to debug.
Catching configuration errors before deploy: config:check --strict in CI, configuration schemas from plugins, environment-specific files and secrets that should never be committed.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.