Anodot data streams and agent pipelines that send data points using the Metric 3.0 format can also include information about the gap filling policy they require.
Based on the gap filling settings, Anodot should then fill the data for each stream/pipeline.
Defining the gap fill policy in Anodot data streams
Anodot data streams provide the information in the Missing Data section of the stream query page, as shown in the example below.
Note that for backward compatibility purposes, when first accessing the Missing Data section, the Data gaps should not be filled option is selected by default.
To define a gap fill policy, select Fill in the gaps, and then fill in the maximum duration (in hours or days), and Gauge and Counters value(s).
The Gauge (the average aggregation type) and Counters (the sum aggregation type) values can be defined using the Last Value or a Custom Value:
- Last Value: Use the last value known for the measure.
- Custom value: Specify the fixed value you wish to use.
Need to know:
- The gap filling is done at the closest aggregation level to the stream's collection interval. For example: If the collection interval is hourly, the gap filling will be done on the hourly level.
- To prevent endless gap filling by Anodot, even for metrics you do not sent anymore, the gap filling maximal period is defined in the schema definitions, see maxDVPDurationHours in our API documentation
