Questions about synthetic checks, incidents, and reports

Do we need a Magento module?

Yes, recommended. Install vendoracs/module-ops-monitor-connector via Composer to send heartbeat and metrics to Ops Monitor reliably.

What synthetic steps are checked?

Homepage, product page, cart entry, and checkout page checks with status, HTTP code, and latency.

How are incidents created?

Critical anomalies and repeated checkout failures open or update incidents with dedup windows.

Can we assign incidents?

Yes. Incident Center supports acknowledge, assign to org members, and resolve with reason.

How does Alerting 2.0 reduce noise?

Quiet hours and maintenance windows suppress immediate sends while recording suppression events.

Which channels are supported?

Telegram is supported natively. Email and webhook routing are available via alerting rules.

What are advanced metric streams?

HTTP, DB, Redis, and Search telemetry streams with strict payload validation and aggregation.

How is SLA/SLO computed?

Daily SLI combines health-critical intervals with checkout synthetic failures. If synthetic data is missing, health-only fallback applies.

Who gets weekly reports?

By default, organization owner and billing/admin members with valid email addresses.

Are API keys stored in plaintext?

No. Store ingest keys are hashed at rest and raw values are shown only once during creation/rotation.