Thanos has the following components:
* Query
* Store - Not needed unless you want long term storage stored in a remote
backend (GCS, S3, etc)
* Compactor - Not needed because you are not using Store.
* Sidecar
You only need the Query and Sidecar components and they are fairly easy to
run. Thanos is written in Go and every component can be executed using a
single binary.
On Thursday, 27 February 2020 13:39:17 UTC+1, Riyan Shaik wrote:
>
> Thanks for your inputs, i recently started exploring Thanos, starting with
> the sidecar just like you mentioned. Would really like to know what your
> overall prometheus architecture is like and your experiences with Thanos.
> Isn't Thanos and its myriad of components an overkill if all you've is 1
> baremetal prometheus setup ?
>
> On Thursday, 27 February 2020 01:40:04 UTC+5:30, John Bryan Sazon wrote:
>>
>> Using Thanos, each Prometheus can scrape and write data within its own VM
>> filesystem. You then deploy the Thanos sidecar within each of these
>> Prometheus VM. Then, you use Thanos query and connect these sidecars in it.
>> Thanos query provides a Prometheus API with global view with automatic
>> de-duplication.
>>
>> If you use Grafana, you then use the Thanos Query HTTP API endpoint as
>> your Prometheus datasource URL.
>>
>> I have been using this kind of setup in Production and have been very
>> happy with it. See https://thanos.io/
>>
>> Other choices are Cortex and VictoriaMetrics (advertised to have easier
>> setup and better performance than Cortex and Thanos).
>>
>>
>>
--
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/bed01ce9-07d7-4ef5-b681-885f206e412f%40googlegroups.com.
