Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 1
    Note ArcticDB.io is now just-s3 (no MongoDB dependency). It's a python data frame database optimised for storing tables of (primarily) numeric values as time series. Commented Jul 25 at 7:18
  • The traditional way to monitor this in infrastructure would be a metrics store - prometheus, influxdb etc. Cardinality can be quite painful. If you can group your data in a table, and are happy reading / writing data in Python, ArcticDB would be a trivial tool to try. Demos on the website. colab.research.google.com/github/man-group/ArcticDB/blob/v4.5.1/… Commented Jul 25 at 7:19
  • 1
    @James I wanted to suggest "Arctic" but they changed to "ArcticDB" (which is better, but different). I wanted to suggest open source and a simple upgrade to an existing database, rather than a standalone and complex offering: tdengine.com/how-to-choose-the-best-time-series-database - so I'd prefer Prometheus over the expense of Influx. Commented Jul 25 at 9:43
  • Here's a comparison of Prometheus and Influx influxdata.com/comparison/influxdb-vs-prometheus (on Influx's website). Commented Jul 25 at 9:53
  • 2
    Great suggestion, thank you. To maintain the key map table my thinking is to use a mysql table, with primarily key on (job_id, timeseries_id) so I can get atomically incremented IDs. Commented Jul 25 at 16:44