Metrics feels like another area where you should allow exception. Prometheus is like a tank, I’ve never seen it misbehave and if you set retention short it’s very close to a fire and forget deployment with very little configuration, especially if you only use it to monitor two other static services.
These metrics will be invaluable to tell you how close to the limit you are running your single dependency, to avoid adding premature cache in front or whatnot.
The integration of Prometheus with other tools also make it worth the extra component, rather than reinventing your own time series in PG.
Logging is a whole different beast. Especially if you even think about Elastic.
> Logging is a whole different beast. Especially if you even think about Elastic.
I think you kinda have to have something like Elastic. (Not necessarily Elastic, but honestly, I've yet to see anything better. Which … isn't great.) As soon as you're dealing with multiple services or multiple instances of a service, you'll want some way to aggregate logs. Even for a single service, on a single instance, some way to search logs (no, grep does not count), and at some point, alert.
Take a look at Grafana Loki. It’s a log aggregator designed for ease of operation. With some compromises on query capabilities instead, well worth it as it’s still incredibly powerful.
These metrics will be invaluable to tell you how close to the limit you are running your single dependency, to avoid adding premature cache in front or whatnot.
The integration of Prometheus with other tools also make it worth the extra component, rather than reinventing your own time series in PG.
Logging is a whole different beast. Especially if you even think about Elastic.