The single-instance design of Prometheus makes it impractical to maintain large datasets of historical data, as it is limited by the amount of storage that's available locally. Having time series that span large periods allows seasonal trend analysis and capacity planning, and so, when the dataset doesn't fit into local storage, Prometheus provides this by pushing data to third-party clustered storage systems. In this chapter, we will look into remote read and write APIs, as well as shipping metrics for object storage with the help of Thanos. This will provide options on how to tackle this requirement, enabling several architecture choices.
In brief, the following topics will be covered in this chapter:
- Test environment for this chapter
- Remote write and remote read
- Options for metrics storage
- Thanos remote storage and ecosystem...