Skip to content
Log inContact sales

Works with the tools you already run.

P1INC-20931Card checkout failingMajor13:59:40 ICT

1/7The provider reports trouble first

detect
  • InCloud and SaaS providers

The provider's status page shows degraded card authorisation. None of your own alerts have fired yet.

  1. 13:59:40InCloud and SaaS providersStatus page polled · card authorisation degraded since 13:59
  2. 13:59:40MonitOpsMonitOpsHeld as context. A provider notice alone does not open an incident.
Fig. 1 — INC-20931 on 30 September 2026, 13:59 to 14:10 ICT, as the integrations saw it. A shaped dot marks an integration that was not fully healthy.
Available integrations

Built first for the platforms customer operations run on.

MonitOps reads each platform’s own health, limits and operational events, so a provider-side fault is detected and classified as the provider’s, not yours.

Salesforce

Health and limits
Status
Instance status, incidents and maintenances from Salesforce Trust, polled every minute
Limits
API limit usage, with a forecast of time to exhaustion and a predicted-breach alert
Events and audit
Events
Real-time operational events from Event Monitoring, used for detection and as evidence
Log files
Hourly event log files, used as evidence and for trends, never for real-time alerting
Show
SalesforceSaaS · org 00D5j000001xCx · instance AP24
Degraded
Provider statusSalesforce saysOperationalno incident reported · 14:19:12
Source freshnessObserved 14:20:01 ICT · 4 s behind
Synthetic probes
sf-oauth-loginPassOAuth login · 1.1 s · 14:19:40
sf-case-lookupFailHTTP 401 at step 2 · 6 of last 6 failed · 14:19:40
Fig. 2a — Classified: yours · not the providerCase lookups fail with HTTP 401 while Salesforce Trust reports no incident on instance AP24. MonitOps does not blame the provider.

Genesys Cloud

Health
Status
Platform status by region and component
Health
Authenticated platform API checks
Events
Events
Operational events delivered through your cloud event bus
Show
Genesys CloudSaaS · org cx-th-prod · Asia Pacific (Tokyo)
Degraded
Provider statusGenesys saysDegraded performanceData actions · since 14:04
Source freshnessObserved 14:20:01 ICT · 4 s behind
Synthetic probes
gc-webchat-startPassStart web chat · 2.4 s · 14:19:40
gc-data-action-caseFailHTTP 401 at step 2 · 6 of last 6 failed · 14:19:40
Fig. 2b — Classified: provider's · Genesys CloudGenesys reports degraded data actions since 14:04, matching the failures MonitOps sees. The incident is classified as the provider's, with the status notice as evidence.
Any OpenTelemetry source

If it sends OpenTelemetry, it connects.

MonitOps receives logs, metrics and traces over OpenTelemetry, with a credential per source. Applications instrumented with an OpenTelemetry SDK in Java, .NET, Node.js, Python or Go send directly. Everything else arrives through the OpenTelemetry Collector or a shipper that speaks OTLP.

  • OpenTelemetrySDKs and Collector
  • Fluent Bitnative OTLP output
  • Kubernetesvia the Collector
  • Prometheusvia the Collector
  • Envoynative OTLP traces and access logs
  • Istiothrough Envoy

These are open standards and open-source projects. Compatibility is by protocol; MonitOps is not endorsed by or affiliated with them. Other product names are trademarks of their respective owners and are used only to identify the platforms MonitOps integrates with.

Integration health

Every integration shows whether it is working.

In the console, each integration shows its own freshness, errors and backlog. A quiet integration is never mistaken for a quiet system.

14:04 ICT
  • Application telemetry1 source silentcrm-sync silent since 13:48 · shown as unknown
  • Cloud and SaaS providersHealthyPolling every 60 s
  • Synthetic checksHealthy2 probes reporting failures
  • ChangesHealthyLast record 13:12
  • TicketingBacklog214 queued · oldest 3 min · retrying
  • Fault managementDeliveringOwn queue · not held up by ticketing
  • Log platformDelivering4 s behind ingestion
  • Security toolingDelivering0 queued
  • AutomationReadyRB-PAY-004 available · approval required
Fig. 3 — The same moment in INC-20931, two ways. Drag the handle across the status column. Without integration health, a silent source and a stuck ticket queue look calm.
New and custom integrations

Need something that is not listed? Ask.

We build new integrations during implementation, or you add your own adapter. Identity, masking and storage are handled by MonitOps either way.

Contact salesConnecting sources in the documentation