Re: [prometheus-users] Prometheus using AWS Timestream

2020-11-25 Thread 'ellis...@googlemail.com' via Prometheus Users
and thanks Ryan. I am just in the process of building the adapter into a container at the moment and haven't tested throughput. Good to know. On Thursday, 26 November 2020 at 07:28:40 UTC ellis...@googlemail.com wrote: > I agree. I'm not too concerned about the alerting side of things as this >

Re: [prometheus-users] Prometheus using AWS Timestream

2020-11-25 Thread 'ellis...@googlemail.com' via Prometheus Users
I agree. I'm not too concerned about the alerting side of things as this is covered by Grafana, the recording rules help filter out the noise where possible. I've had a bash at altering the dashboard in Prometheus but it isn't that user friendly to configure, hence the swap over to Grafana.

Re: [prometheus-users] Prometheus using AWS Timestream

2020-11-25 Thread Ryan Booz
Sorry - just realized I mistyped that second sentence in the midst of trying to spell it out and crossed terminology. It should have read: For our tests, we used TSBS and used the "cpu-only" use case to simulate 100 hosts. That test creates 10 CPU time-series for 100 hosts, every 10 seconds -

Re: [prometheus-users] Prometheus using AWS Timestream

2020-11-25 Thread Ryan Booz
I can't speak to CrateDB's tests, but the article I linked to said it took them 3 days to load ~3 billion metrics using 20 clients, which is on-par with our findings too. For our tests, we used TSBS and used the "cpu-only" use case to simulate 100 hosts. That test creates 1,000 time-series acro

Re: [prometheus-users] Prometheus using AWS Timestream

2020-11-25 Thread Stuart Clark
On 25/11/2020 16:27, Ryan Booz wrote: As the makers of Promscale, we're very attuned to the needs of effective Prometheus deployments. With that in mind, one thing to consider with Timestream is that ingest performance from a single client seems to be a current limitation. The creator of this a

Re: [prometheus-users] Prometheus using AWS Timestream

2020-11-25 Thread Ryan Booz
As the makers of Promscale, we're very attuned to the needs of effective Prometheus deployments. With that in mind, one thing to consider with Timestream is that ingest performance from a single client seems to be a current limitation. The creator of this adaptor doesn't mention his his setup o

Re: [prometheus-users] Prometheus using AWS Timestream

2020-11-24 Thread Stuart Clark
On 24/11/2020 14:06, 'ellis...@googlemail.com' via Prometheus Users wrote: the guy that wrote the adapter suggests that a Grafana plugin would be used to read the information from Timestream in AWS. Yes, but that doesn't help for alerting, recording rules, etc. which are in Prometheus. -- Y

Re: [prometheus-users] Prometheus using AWS Timestream

2020-11-24 Thread 'ellis...@googlemail.com' via Prometheus Users
the guy that wrote the adapter suggests that a Grafana plugin would be used to read the information from Timestream in AWS. On Tuesday, 24 November 2020 at 12:47:12 UTC Stuart Clark wrote: > On 24/11/2020 09:53, 'ellis...@googlemail.com' via Prometheus Users wrote: > > Hi all, > > > > Is anyone

Re: [prometheus-users] Prometheus using AWS Timestream

2020-11-24 Thread Stuart Clark
On 24/11/2020 09:53, 'ellis...@googlemail.com' via Prometheus Users wrote: Hi all, Is anyone using Prometheus in AWS to monitor and if so have you thought about using Timestream as a remote storage solution? I can see that there is a remote write adapter available at https://github.com/dpat

[prometheus-users] Prometheus using AWS Timestream

2020-11-24 Thread 'ellis...@googlemail.com' via Prometheus Users
Hi all, Is anyone using Prometheus in AWS to monitor and if so have you thought about using Timestream as a remote storage solution? -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails