Skip to main content

11 Web Services

Web Services answers whether monitored web services show degradation, errors, or unavailability signals.

Operations Web Services with anonymized data
Web Services domain with anonymized service state.

What appears​

  • Delay + Runtime in one multi-query chart with unambiguous labels for both signals.
  • Operational inventory as a complete table of monitored services.

The composition retains the series, filters, and overlays of each query. The table is not reduced or converted into a time-series metric.

How to interpret it​

  • OK: calls are stable and there is no relevant service error.
  • WARN: errors are intermittent, latency is increasing, or a subset of services is degraded.
  • KO: failure is sustained or integrations are likely impacted.

Web service failures can originate in the service implementation, ICM/Gateway, network path, authentication, or a backend dependency. Use the domain to decide whether the issue is service-specific or part of a broader communication incident.

Filters and next screens​

Cross-check ICM / Gateway first when communication errors rise. Use Events to inspect SAP messages, Metrics for the raw service series, and the Landing map when one instance carries most of the failures.