Understanding your tracing license consumption helps identify where you're spending the most money on your tracing data.
Datasets are a control mechanism that allow you to map sets of traces to named groups relevant to your organization, and then track processed and persisted bytes for those groups over time.
For example, you might create a Shopper dataset based on data like services, operations, customer IDs, and tags that relate to your shopping app. Viewing that dataset provides a snapshot of trace data volume associated with the entire business unit related to your shopping app.
Understanding data consumption for individual business units can highlight which sampling rules to adjust so you can better control your trace data license consumption and remain within defined data limits.
Datasets are part of the Trace Control Plane, which also includes head and tail sampling rules. To access the Trace Control Plane, in the navigation menu select Shaping > Trace Control Plane.
The Overview tab displays your total license consumption for the selected period, which defaults to the current month. This view includes graphs that display the daily volume breakdown and the cumulative breakdown over the current week. A table includes all available datasets. The row for each dataset displays the underlying query that defines the dataset, the total data volume, and the percent of data overlap. You can take any of the following actions:
Click Processed or Persisted to toggle between processed and persisted bytes.
On either of the graphs, click the more icon and select Open in Metrics Explorer to visualize the underlying query.
Toggle Show unique volume to display only the volume of data that doesn't overlap with another dataset.
In the datasets table, select one or more datasets to update the graphs. You can click and drag a section of either graph to zoom in on the selected time period.
To view an individual dataset, click the name of the dataset you want to view from the list. The individual dataset page includes a definition of the underlying Trace Explorer query and the services at the root of all traces in the dataset. To view the underlying queries, in either the Definition or Root services, click Go to Trace Explorer.
You must contact Chronosphere Support to create a dataset and have it display in your Chronosphere app.
To create a dataset:
Define a query in Trace Explorer that represents the data you want included in the dataset. For example, the following query returns all traces where at least one span includes a service called
shopping-svc, an operation that starts with
checkout, and a tag named
service="shopping-svc" operation=~"^checkout*." tag:env=prod*"
After defining the underlying query, work with Chronosphere Support to map the query to a dataset that represents the business unit you want to track trace data for.