Monitor services and hosts in Splunk Infrastructure Monitoring 🔗
See the following pages for more information about using navigators to monitor public cloud, container, or host integrations:
Public clouds
Containers
My Data Center
Scenarios for navigators
Splunk Observability Cloud also provides metrics and other data for the following host and application monitors.
Displayed data: Traffic considerations 🔗
Information is displayed only if data is streamed in. If there’s no data coming in from a stream for more than 3 hours, that stream stops being counted in Splunk Observability Cloud.
Kubernetes monitoring holds tiles in a deactivated state until it goes inactive, which happens 25 hours after the last data point is received.
Some metrics, like those related to CPU utilization, are always reported. Splunk Observability Cloud uses these metrics on the Navigator summary page.
A few metrics are not sent continuously. For example, metrics related to the number of errors are only sent when errors happen.
Don’t try to get a list of entities using one of the few metrics not sent continuously, because entities with no errors might be hidden.
Counts are sensitive to the time range, the calculated resolution of the job that runs, and the frequency of the data that is coming in.
A typical cloud integration reports a new data point every 5 minutes.
As the job is running, reporting instances that are turned off drop off after the time range that they are part of passes.