The presentation discusses the challenges of using Prometheus as the standard for collecting and storing time series in serverless architectures and the need for a better solution.
- Prometheus assumes that the system lives long enough to be discovered and scraped, that the service is network-enabled, and that the user can do their own aggregation.
- Prometheus uses a pull-based model for metrics collection, which requires the service to live for at least 5-15 seconds.
- Exposing things over the network requires the ability to listen on a port, spin up a server, and secure communication with firewall rules and TLS certificates.
- Prometheus assumes that the user can do their own aggregation, which can be problematic for metrics like request counts.
- There is a need for a better solution that can handle the challenges of serverless architectures and provide more accurate metrics.