Best way to filter the data to be sent to the object storage #4048
Unanswered
Mojito2110
asked this question in
Questions & Answers
Replies: 1 comment
-
Sorry for the late response. IMO, either way sounds good to me. From the perspective of deployment and configuration, the first option is easier to maintain. As you already have some experience using Sidecar and Prometheus. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
My deployment includes several Prometheus servers. Each one collects different technical domain metrics. I don't want to load all of the metrics into the object store, but select only a few.
With the Thanos Sidecar it is not possible to filter, the Prometheus data blocks are loaded in their entirety.
There are two approaches to filtering if I understand correctly.
first option: set up a Prometheus federation to collect only the metrics from the Prometheus servers that we want to put in the object storage and install the Sidecar on this federation server.
second option : use the remote_write API and a Thanos Receiver and play with the match[] directive in the Prometheus server configuration to select only the metrics I want.
What do you think would be the best solution in terms of scalability, ease of deployment and configuration, scalability etc...
Beta Was this translation helpful? Give feedback.
All reactions