awesome-mobile-observability-agent-skills

Emit JSON-structured logs on mobile with correlation ids, consistent field names, and redaction. Use when setting up logging in Kotlin, Swift, Dart, or TypeScript mobile code.

Emit counters, gauges, and histograms from mobile apps using OpenTelemetry metrics, with patterns for batching, labels, and avoiding cardinality explosions. Use when adding product or engineering metrics beyond the core RUM set.

Design actionable metric alerts for mobile telemetry that deep-link to traces and sessions, avoid paging noise, and page only for symptoms users feel. Use when creating or cleaning up Datadog / Grafana / Sentry alerts.

Define and capture the core mobile RUM SLIs (startup time, jank, ANR, crash, network error rate, battery) with Firebase, Sentry, Datadog, or OTel. Use when setting up client-side performance metrics.

Compare and configure mobile APM vendors (Firebase Performance, Sentry Performance, Datadog RUM Mobile, Embrace, New Relic Mobile) and pick the right one for the app. Use when selecting or migrating a performance-monitoring stack.

Measure mobile UX quality with frozen frames, slow frames, ANRs, app hangs, and interaction-to-next-paint style metrics. Use when diagnosing jank, adopting JankStats / MetricKit, or reporting UX health.

How mobile session replay works (view-hierarchy reconstruction, not screen recording), how to configure privacy masking, and the cost / privacy tradeoffs. Use when evaluating or enabling Sentry, Datadog, or LogRocket session replay on mobile.

Build funnel analytics and user-journey graphs on top of the mobile event taxonomy. Use when analyzing conversion, drop-off, or retention in Amplitude, Mixpanel, PostHog, or GA4.

Instrument mobile apps with OpenTelemetry client SDKs so traces start on the device and propagate to the backend. Use when wiring up tracing on Android, iOS, Flutter, or React Native.

Propagate W3C traceparent and baggage headers from mobile HTTP clients (OkHttp, URLSession, Dio, fetch) to backend services. Use when adding network instrumentation or debugging why client traces don't connect to backend spans.

Define SLIs, SLOs, error budgets, and rollout halts for mobile apps, with multi-window burn-rate alerts. Use when formalizing reliability targets or gating staged releases.

Runbooks, severity levels, and escalation policy for mobile on-call, covering crash spikes, ANR spikes, store rejections, and bad release rollback. Use when setting up or refining a mobile on-call rotation.

Apply consent gating, data minimization, App Tracking Transparency (ATT), DMA compliance, and COPPA/GDPR rules to mobile analytics. Use when launching in the EU, UK, or US, or before enabling new telemetry.

Define versioned, validated analytics-event schemas with type-safe wrappers so clients and warehouses agree on shape. Use when formalizing or migrating an existing tracking plan.

Design a mobile product-analytics event taxonomy with consistent naming, governance, and a registry. Use when introducing new events or cleaning up an existing Amplitude / Mixpanel / Segment / Firebase Analytics setup.

Set up Firebase Crashlytics correctly across Android (Kotlin), iOS (Swift), Flutter, and React Native with custom keys, user ids, and release tagging. Use when adding or auditing Crashlytics integration.

Set up Sentry on mobile with error reporting, performance tracing, and session replay. Includes the iOS/Android/Flutter/RN SDKs and the privacy and cost caveats of session replay on mobile.

Automate symbol uploads for iOS dSYMs, Android ProGuard/R8 mapping files, NDK native symbols, Dart obfuscation symbols, and Hermes source maps across Crashlytics, Sentry, and Datadog. Use when crashes show as addresses, unreadable class names, or minified JS frames.

Rules for choosing log levels, keeping signal/noise healthy, managing on-device log retention, and avoiding logger abuse on mobile. Use whenever adding or reviewing log statements.

Ship mobile logs to a remote backend (Datadog, Grafana Loki, Elastic, OTel collector) with batching, sampling, PII redaction, offline buffering, and backpressure. Use when introducing or reviewing remote log shipping.