Harkishen, thank you very much for the design document!
My initial thoughts are to agree with Stuart (as well as some users in the
linked github issue) that it makes the most sense to start with dropping
data that is older than some configured age. The default being to never
drop data. For most
Great - I made a PR at https://github.com/prometheus/prometheus/pull/8552.
I added /storage/remote, but at that point maybe we want to add all the
other dirs with specific maintainers as well?
On Mon, Mar 1, 2021 at 9:10 PM Tom Wilkie wrote:
> Yes! I was chatting to Beorn about this the other
On 01 Mar 21:05, Julius Volz wrote:
> Heya all,
>
> Julien often helpfully pings me on PRs that touch the React UI, but it
> would be much nicer if I could somehow get auto-notified by GitHub
> specifically of those that touch anything under /web/ui/. Others might feel
> the same about their
Yes! I was chatting to Beorn about this the other week... Big +1 from me.
Mind adding a line for /storage/remote too?
Thanks
Tom
On Mon, Mar 1, 2021 at 8:05 PM Julius Volz wrote:
> Heya all,
>
> Julien often helpfully pings me on PRs that touch the React UI, but it
> would be much nicer if I
Heya all,
Julien often helpfully pings me on PRs that touch the React UI, but it
would be much nicer if I could somehow get auto-notified by GitHub
specifically of those that touch anything under /web/ui/. Others might feel
the same about their areas of purview.
GitHub has a CODEOWNERS file
Hi all,
In contrast to what was announced previously (see below), the deadline
for the PromCon online 2021 will be this Friday, 2021-03-05.
See https://promcon.io/2021-online/submit/ .
On 09.02.21 14:42, Richard Hartmann wrote:
> Dear all,
>
> * CfP runs until 2021-04-02
> * Event co-hosted
On Thu, Feb 18, 2021 at 10:10 PM Julien Pivotto
wrote:
>
> I would also note that generally we have agreed that it will be possible
> to split the prometheus config in multiple file, currently pending a
> design document.
I think this would only work nicely if your file with the secret
contains
Hello everyone,
I am facing strange issue with SNMP Exporter.
Approx 100 devices are added in prometheus.yml to get SNMP data via SNMP
Exporter however there is one node is showing down all the times in
prometheus Targets
When I ran URL(
http://XX:9116/snmp?target=XX&=dell) to debug further
If a remote write receiver is unable to ingest, wouldn't this be something
to fix on the receiver side? The receiver could have a policy where it
drops data rather than returning an error.
This way Prometheus sends, but doesn't have to need to know or deal with
ingestion policies. It sends a bit
On 01/03/2021 07:25, Harkishen Singh wrote:
Hi Tom,
I have tried to answer the comments. Please comment on their
satisfactoriness. I am happy for a call if required (or discussion
gets tough).
I think, the lossless nature can be controlled by the user based on
the config (limit_retries),
10 matches
Mail list logo
