Platform For AI:Logging, monitoring, and alerting

Overview

Logs, monitoring, and alerts each play a distinct role in incident response:

• Logs: Capture detailed service output—startup messages, request handling, and error stack traces—so you can pinpoint the root cause of an issue.

• Monitoring: Surface service trends through metrics and charts (QPS, latency, error rate, resource usage) so you can detect anomalies and plan capacity.

• Alerts: Apply thresholds to monitoring metrics and notify you when something goes wrong, prompting timely action.

A typical troubleshooting path: an alert fires → monitoring narrows down the affected metric and time window → logs reveal the root cause.

Logs

EAS provides three logging options:

• Historical logs: View past logs on the Log tab of the service details page, with per-instance filtering, keyword search, and time-range filtering. Best for log retrieval and analysis.

• Real-time logs: Select an instance in the Service Instance list, then click Real-time Logs to stream the container's rolling output. Best for interactive debugging or scenarios requiring immediate visibility, such as watching token-by-token inference output.

  Note

  Real-time logs aren't available for services created before this feature launched. Recreate the service to use them.

• SLS log delivery: Deliver logs to SLS for long-term retention, cross-service correlation, and compliance archiving. Configure delivery rules in the resource group first. For details, see Configure log collection for a resource group.

Monitoring

EAS provides four monitoring options:

• Service monitoring: View basic runtime metrics such as QPS, latency, error rate, and resource usage. Works out of the box—open the Monitoring tab on the service details page. For details, see View service monitoring metrics.

• Custom metrics: Report business metrics such as inference token count, batch size, and hit rate by adding instrumentation to your service code. For details, see Custom monitoring and auto scaling metrics.

• Dashboards: Aggregate key metrics from multiple services onto a unified board. Best for routine health checks across services. For details, see Monitoring dashboard.

• ARMS integration: Connect to Application Performance Monitoring (APM) for distributed tracing and pinpointing performance bottlenecks across components. For details, see Customize observability dashboards and alerts using ARMS.

Alerts

EAS supports two alerting methods:

• Metric alerts: Notify you when monitoring metrics—such as error rate, latency, or resource usage—exceed a configured threshold. Build rules from service monitoring metrics. For details, see Configure service monitoring alerts.

• CloudMonitor events: Listen for service lifecycle events—such as deployment completion, scaling, and unexpected instance exits—and send notifications. For details, see View EAS events in CloudMonitor.

FAQ