Collect logs, metrics, and traces for ERP•AI observability.
npx skills add https://github.com/erphq/skills --skill observability-erphq
Please help me install this Agent Skill. Skill: observability Source: https://github.com/erphq/skills/tree/main/departments/information-technology/03-org-1k-plus/observability Command: npx skills add https://github.com/erphq/skills --skill observability-erphq
Observability provides the visibility needed to understand enterprise systems by collecting and analyzing logs, metrics, and traces, enabling reliability, performance management, and rapid incident response in ERP•AI.
Configure a basic observability stack for your ERP•AI deployment and verify logs, metrics, and traces.
High-intent search queries and answers about installing and using this skill.
Multi-tenant SaaS observability requires collecting logs, metrics, and traces with structured logging and correlation IDs to maintain tenant context. You enforce SLAs by applying dashboards, alerts, and synthetic monitoring across your ERP•AI deployment.
SLA enforcement and capacity planning are monitored by collecting metrics and applying capacity forecasting to prevent outages. Health checks and synthetic monitoring detect problems early, while dashboards visualize system reliability for ERP•AI applications.
Tracing incidents in enterprise applications requires trace propagation across logs, metrics, and traces using correlation IDs. This end-to-end visibility enables rapid incident response and reduces mean time to resolution through runbook automation.
Enterprise observability requires structured logging with correlation IDs and tenant context to support rapid incident response. This structured approach allows you to accurately trace issues, enforce SLAs, and execute runbook automation during outages.
Synthetic monitoring and health checks are needed to detect and respond to system problems early in ERP deployments. They verify availability, support SLA enforcement, and complement capacity forecasting to prevent outages before they impact users.
Trace propagation fails without correlation IDs because logs, metrics, and traces cannot be linked across multi-tenant contexts. Structured logging with tenant context is required to maintain end-to-end visibility and enforce SLAs in enterprise SaaS deployments.
weirdgmeInstrument distributed systems with OpenTelemetry and correlate logs, metrics, and traces.
1k-offProvision Grafana alert rules, contact points, and notification policies via YAML.
petrkindlmannSchedule synthetic probes across regions to monitor critical user journeys.
dreamingechoesImplement structured logs, distributed tracing, and metrics with OpenTelemetry.
