On Wed, Oct 14, 2020 at 6:12 PM Al <[email protected]> wrote: > For this specific use-case, it's understood that we wouldn't have alerting > rules as the metrics would ingested only after they've been created. It > would be used purely for inspecting historical trends and identifying > outliers over weeks, months. etc. I'm leaning more towards TimescaleDB as > we already have many instances of Postgres internally so it would end up > being less work to get this up vs implementing something new such as > VictoriaMetrics.
I'd recommend trying both solutions in parallel - TimescaleDB and VictoriaMetrics - and then choosing the most suitable solution for your case. --- Best Regards, Aliaksandr Valialkin, CTO VictoriaMetrics -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/CAPbKnmAp_t_cGXGXU-V3skqzg4%3DV%2Bw7dA_eA9zfhfTA_TAXsBw%40mail.gmail.com.
