|
Description |
Returns a count of the number of input time-series reporting at each time sample |
|
|
Input |
Time Series: Multiple (Single or multiple time-series) |
|
|
Parameters |
None |
|
|
Output |
Transformed Time Series: Single |
|
|
Available in |
Alerts, Composites, Dashboards |
|
The CountSeries function returns the number of metric values streaming to Anodot for any given time sample. This is useful for data validation purposes; when you want to make sure data is streaming and updating continuously, you can use this function to verify there is no drop in the number of updated metrics.
Usage Example
An e-commerce company wants to monitor the bookings for multiple currencies and make sure no data is missing.
They create an alert with the following bookings measurement (2169 booking metrics):
After grouping by currency_name, the result shows 40 different currency groups of bookings:
After applying the CountSeries function, the result is a single metric that counts how many booking updates were registered each hour:
It’s clear from the graph that the number of updated metrics per hour varies between 16 and 35, which means several booking metrics are not reporting regularly every hour. This is expected, as bookings in some currencies are more frequent than others.
In addition, it seems that there is a daily seasonality, but some drops are deeper than others and should be investigated:
