Docs » Glossary for Splunk Observability Cloud

Glossary for Splunk Observability Cloud πŸ”—

Agent (deployment method) πŸ”—
agent (deployment method) πŸ”—

Agent is a deployment method where an instance of Splunk Distribution of OpenTelemetry runs with the application or on the same host as the application. For example, when you configure Splunk OpenTelemetry Connector for Linux, Kubernetes, or Windows, you are using the agent deployment method.

Counter metric πŸ”—

The counter metric type represents data that is a count of occurrences in a time interval.

Cumulative counter metric πŸ”—

The cumulative counter metric type represents a running count of occurrences.

Detector πŸ”—

A detector monitors a signal for conditions or issues that you care about.

Those conditions or issues are expressed as one or more rules that trigger an alert when the conditions in the rules are met. Individual rules in a detector are labeled according to criticality: Info, Warning, Minor, Major, and Critical.

For example, a detector that monitors the latency of an API call may go into a critical state when the latency is significantly higher than normal, as defined in the detector rules.

For more information, see Introduction to alerts and detectors in Splunk Observability Cloud.

Dimension πŸ”—

A dimension is a key/value pair that, along with the metric name, is part of the identity of a time series. You can filter and aggregate time series by those dimensions across Infrastructure Monitoring.

Flappy πŸ”—

A detector is said to be β€œflappy” when it triggers and clears alerts too frequently. For example, if you have a detector set to trigger an alert when a value reaches 90%, and the signal you are monitoring regularly spikes and dips around this value, alerts will be triggered and cleared too often to be of value. To reduce this flappiness, you might want to specify that the value must remain at 90% for a specified amount of time before triggering an alert.

Gateway (deployment method) πŸ”—
gateway (deployment method) πŸ”—

Gateway is a deployment method where Splunk Distribution of OpenTelemetry is running by itself. When you configure Splunk Distribution of OpenTelemetry as a standalone package, you are using the gateway deployment method.

Gauge metric πŸ”—

The gauge metric type represents data that has a specific value at each point in time.

Integration πŸ”—
integration πŸ”—
Integrations πŸ”—
integrations πŸ”—

An integration is a configurable component of Observability Cloud that connects Observability Cloud to a third-party service. Most integrations connect third-party data services, but Observability Cloud also offers SSO and notification integrations.

Property πŸ”—

Properties are key-value pairs that can be bound to metrics, dimensions, or time series. They define arbitrary text data that can be used to provide additional operational information on the objects they are associated with. Properties are different from dimensions in the sense that they do not take part in the identity of a time series; changing the value of a property does not affect the identity of that time series.

Property values are most frequently used as dynamic filters for charts (for example, show 90th percentile of CPU utilization for servers with a location property value of β€œSeattle”), or for groupings (for example, show 90th percentile of CPU utilization for servers, grouped by location value).

Rollup πŸ”—

A rollup in colloquial terms (for metrics, that is) typically refers to an accumulation of datapoints, with some mathematical or statistical expression applied to it, for example, a 95th percentile calculation over a 1-week window. In an Infrastructure Monitoring plot, rollups determine how Infrastructure Monitoring prepares data points for use in charts or analytic computations. For more information, see Rollups.

For example, if you change the time range from -1m (past minute) to -1w (past week), multiple datapoints may be rolled up into one using a rollup function, such as Average, so the datapoints for the wider timeframe can be effectively displayed.

For more information, see Rollups:.

Splunk Distribution of OpenTelemetry Collector πŸ”—

A Splunk Observability Cloud version of the open-source OpenTelemetry Collector, this service provides a unified way to receive, process, and export traces, metrics, and logs data for Splunk Observability Cloud. Configuring Splunk Distribution of OpenTelemetry Collector uses the gateway deployment method. Splunk Distribution of OpenTelemetry Collector is hosted on a public GitHub repository.

Splunk OpenTelemetry Connector πŸ”—

A Splunk OpenTelemetry Connector is a package that bundles Splunk Distribution of OpenTelemetry Collector with additional components to provide integrated collection and forwarding of traces, metrics, and logs for a specific platform. Configuring a Splunk OpenTelemetry Connector uses the agent deployment method.

Tag πŸ”—

Tags can be thought of as labels or keywords assigned to dimensions, metrics, and other objects. They are not key/value pairs.

The primary use case for tags is when there is a one-to-many relationship between the tag and the object you are assigning it to. For example, suppose you have hosts that are running multiple apps. You can create a tag for each app, then apply multiple tags to each host to specify the apps that are running on that host.