Skip to content

How We Store Data

Anomify stores metric data at a frequency of 1 data point per 1 minute. You should send data-points to Anomify at this frequency to avoid gaps in your metrics.

If Anomify stops receiving data a gap will appear in affected metrics. Gaps negatively affect analysis. When this happens the issue is most likely outside of Anomify’s control. Consider enabling Admin Alerts to notify you when Anomify stops receiving metric data so that you can address the issue.

Anomify can aggregate the raw values into 1 minute intervals if you send data more frequently. If you wish to run aggregation for now get in touch with the team. We can turn aggregation on for your metrics and choose to SUM or AVERAGE the raw data in the aggregation settings page.

If you send data more frequently than once a minute without turning on aggregation then the last value you submit for the interval will be recorded.

For example if you sent the following 3 data points in the same minute to flux for a metric:

{
    "metric": "test.multiple_timestamps_per_period.3",
    "timestamp": 1478021701,
    "value": 3.0,
    "key": "Rmv0dd9Sh06KbXzCFL3wFskxSrtUhwUu"
}

{
    "metric": "test.multiple_timestamps_per_period.3",
    "timestamp": 1478021715,
    "value": 6.0,
    "key": "Rmv0dd9Sh06KbXzCFL3wFskxSrtUhwUu"
}

{
    "metric": "test.multiple_timestamps_per_period.3",
    "timestamp": 1478021745,
    "value": 1.0,
    "key": "Rmv0dd9Sh06KbXzCFL3wFskxSrtUhwUu"
}

Anomify would only store the last submitted value for minute period, e.g:

[
    {
      "target": "test.multiple_timestamps_per_period.3",
      "datapoints": [[1.0, 1478021700]]
    }
]