Learn about Wavefront terms.
This glossary introduces common Wavefront terms. Click the links or search this doc set for details.
|Access management||By default, Wavefront users can access objects based on their permissions. Wavefront allows administrators to limit access to Wavefront objects (initially dashboards). With this strict security setting, only the creator (e.g. dashboard creator) and invited users/groups have access to new objects.|
|Alert||An alert defines the condition under which metric values indicate a system problem and one or more alert targets. When the condition evaluates to true or false for a specified period of time, the alert sends an alert notification to the alert target(s).|
|Alert notification||When an alert fires, Wavefront sends an alert notification to the alert target you specified when you created the alert. You can customize alert notifications.|
|Alert target||Specifies when and how to send notifications in response to alert activity. You can use our built-in alert targets by specifying an email address or a PagerDuty key in the alert, or you can create a custom alert target.|
|Application tags||Application tags describe the architecture of an application that was instrumented for tracing. Application tags are span tags with the names
|Bucket size||In Wavefront charts, point buckets represent data that have been summarized over a certain length of time. Chart resolution is the bucket time interval, and it displays in the Horizontal Scale field in the lower-left corner of a chart.|
|Chart||Charts allow you to view and examine your telemetry data. Wavefront supports a rich set of chart types and chart configuration options. You can interact directly with charts–-zoom in, zoom out, change the time window, and so on, and share a link to the chart.|
|Collector agent||Many Wavefront customers set up their environment to use a collector agent such as Telegraf for data collection. The collector agent sends the metrics to the Wavefront proxy. We support integrations for commonly used collector agents.|
|Continuous time series||A time series that contains one data point per second. Because Wavefront accepts and stores data at up to 1 second resolution, a continuous time series has a data value for each moment in time that can be represented on the X-axis of a chart. See also: Discrete time series.|
|Counter||A cumulative counter, or simply counter, is a monotonically increasing counter. These counters are useful for aggregating metric information such as the number of hits on a web page, how many users log into a portal, etc. They're usually used with `rate()` or a similar function. See also:**Delta counter.**</td>
||Dashboards allow you to group and prioritize a set of charts. All charts in a dashboard share certain display preferences and dashboard variables. All Wavefront users have permission to search and interact with dashboards.
||A dashboard variable allows you to dynamically change the components of a query. Dashboard variables can contain metric names, filters, advanced functions, and strings.
||Delta counters bin metrics to a minute timestamp and they treat write operations to the same bin as deltas. Wavefront delta counters are especially useful in serverless Function-as-a-Service environments or if you want to combine points that come in at the same time from several sources. Use a `cs()` query to have your metric treated as a delta counter. See also:**Delta counter.**
||The derived metrics functionality allows you to run a query and ingest it back into Wavefront. All users can then use the result of the query, that is, the derived metric, in their queries.
||The direct data ingestion mechanism supports sending data directly to the Wavefront service instead of a Wavefront proxy. While the Wavefront proxy has many benefits, direct data ingestion can be the best approach for some use cases.
||Discrete time series
||A time series whose data points are separated by time intervals that are greater than one second. These longer intervals may be due to reporting that is infrequent, irregular, or interrupted. See also: Continuous time series.
||You can embed an interactive chart outside of Wavefront. When you use the UI, we generate an HTML code snippet and you can adjust the width and height.
||An event is a record that something of interest has happened. For example, the event might show that an alert has changed state. Wavefront supports system events and user events.
||An expression describes data of a particular type: time series, histograms, events, traces, or spans. Expressions can be complete queries or building blocks of queries.
||External links allow you to go from a Wavefront chart to an external system such as a log. You can in effect connect your streaming metrics to logs and other external info.
||A Wavefront histogram is a series of distributions that Wavefront has computed from the data points of a time series. Each distribution summarizes the points in a particular time interval (minute, hour, or day) by organizing their values into bins (value ranges). You can send histograms to a histogram proxy port or directly to the Wavefront service.
||Integrations are one easy way to get data from external systems into Wavefront. Wavefront supports over 160 integrations with common Web, cloud, monitoring, and other applications and services. For cloud integrations such as AWS, setup is automated. For other integrations, you follow setup steps which usually involve changes to a configuration file.
||You can create a maintenance window to prevent alerts from firing. That's useful if you expect to perform disruptive operations that result in conditions where alerts would fire.
||Metadata is a collection of values that uniquely describes a particular set of observability data, but which are not themselves part of the data set. For example, every time series is uniquely described by its metric name, source name, and point tags.
||Metrics are data points that measure the same thing over time. They are well suited for gaining a real-time and historical understanding of system health and trends.
||If a Wavefront customers uses an Identity Provider (IP), all users authenticate with that IP and see the same information by default. Multi-tenant SSO allows customers to request multiple tenants, each with a tenant administrator. Tenant administrators can invite other users. Users who authenticate to the IP can then access the tenant(s) to which they have been invited.
||Object tags help you filter your display. You apply an object tag to Wavfront UI objects such as dashboards. You can later find and display groups of objects based on their object tag.
||Refers to all data you can store and analyze with the Wavefront observability platform. Metrics (including delta counters), histograms, and tracing spans are collectively described as observability data. (Sometimes called telemetry data.)
||An operation is a distinct segment of work that a microservice performs. An operation's name is typically the name of a function, method, or procedure that the microservice invokes. An operation might be part of a higher-level request or transaction, and might invoke other, lower-level operations. When you instrument an operation for distributed tracing, each invocation of the operation emits a span.
||Wavefront permissions determine the tasks that a user can perform.||Point tag
||Point tags are key-value pairs (strings) that are associated with a point. Point tags allow you to fine-tune your queries so the output shows only the information you're interested in.
||Points per Seconds. Telemetry data points per second ingested by the Wavefront Service. All customers are billed based on their PPS. We support dashboards and tools to Find Actionable Usage Information
||A Wavefront proxy ingests metrics and forwards them to the Wavefront service in a secure, fast, and reliable manner. Using a Wavefront proxy has several benefits, but you can also send data to Wavefront using direct ingestion.
||Queries are requests that you submit to find and visualize data. A query consists of expressions built from the Wavefront Query Language. You can compose queries with the Chart Builder UI, or you can write queries directly in Query Editor. Queries let you retrieve and transform ingested data, as well as create and display synthetic data for the duration of the query.
||RED metrics are key health metrics for applications that are instrumented for distributed tracing. RED metrics measure the Request Rate (number of requests per minute), Errors (number of failed requests per minute), and Duration of the spans that are generated by an application or one of its services. See also: Span RED metrics, Trace RED metrics.
||Sampling is a technique for limiting the volume of trace data that is actually sent to Wavefront for storage and visualization. A sampling strategy is a policy for deciding which traces to send.
||An SDK (software development kit) is a library that you can include with your application code. Wavefront supports observability SDKs in different programming languages to enable you to instrument applications to report telemetry data to Wavefront.
||A source is a unique application, host, container, or instance that emits observability data. A source is part of the unique metadata that identifies a data set. For cloud integrations, the source is extracted automatically from service properties or dimensions.
||Source tags allow you to group your sources. For example, you can tag production hosts and development hosts with different source tags, and later run a query over only one group of sources.
||A span is a named, timed representation of a contiguous segment of work in a trace. Every span corresponds to a unique invocation of an operation in an instrumented application, and belongs to exactly one trace.
||Span RED metrics
||Span RED metrics measure the individual operations that originated in a service or application that was instrumented for tracing. For example, a span RED metric for a
||Span tags are key-value pairs (strings) that are associated with a span. Certain span tags are required for a span to be valid. An application can be instrumented to include custom span tags, as well.
||Tags are metadata that is associated with your observability data. You can use tags to filter the results of a query, or to apply an operation to a group of objects (such as suppressing a group of alerts during a maintenance window). Wavefront supports several types of tags, including source tags, point tags, event tags, alert tags, and span tags. See also: Point tag, Source tag.
||See Observability data.
|| If your company has several teams, and if each team wants to work independently, you can request a multi-tenant SSO setup. Afterwards, users can be invited to individual tenants only - and users who belong to multiple teams can be invited to multiple tenants. See also: Multi-tenant SSO.
||A time series is a data set that consists of a sequence of data points over time. Each data point in a time series combines a single data value with a unique timestamp. Every time series is identified by unique metadata (combination of metric name, source name, and point tag values). In the Wavefront query language, you use the ts() function to describe and visualize a time series. See also: Continuous time series and Discrete time series.
||A trace allows you to follow and examine a transaction or workflow in your application. As a result, you might be able to locate errors in context or improve execution speed. In OpenTracing, a trace is a directed, acyclic graph of spans.
||Trace RED metrics
||Trace RED metrics measure the traces that start with a given root operation in a service or application that has been instrumented for tracing. For example, a trace RED metric for a service might measure the number of traces that each start with a call to the
||The Wavefront service runs the metrics collection engine. It can receive telemetry data from a Wavefront proxy or through direct ingestion.