Runtime Metrics

The runtime metrics shown in the ODJ are providing 3 of the 4 so called Four Golden Signals:

Latency

The amount of time it takes to serve a request.

Traffic

A measure of how much demand is being placed on your system, measured in a high-level system-specific metric. For a web service, this measurement is usually HTTP requests per second, perhaps broken out by the nature of the requests (e.g., static versus dynamic content). For an audio streaming system, this measurement might focus on network I/O rate or concurrent sessions. For a key-value storage system, this measurement might be transactions and retrievals per second.

Errors

The rate of requests that fail, either explicitly (e.g., HTTP 500s), implicitly (for example, an HTTP 200 success response, but coupled with the wrong content), or by policy (for example, "If you committed to one-second response times, any request over one second is an error").

Every application created via the ODJ will receive a runtime and therefore per default receive a global HTTPS load balancer. This ensures that the mentioned metrics can be provided without any further effort other than creating a runtime.