One thing I forgot to ask:
how bad is that query (since for now it does what is needed)
performance-wise?
my_metric{label="value"}[100y]
On Tue, Jan 5, 2021 at 8:57 PM Roman Dodin wrote:
> Thanks Ben, it is clear now.
> I will check if it makes sense to add a "metric-replay" feature in the
>
Thanks Ben, it is clear now.
I will check if it makes sense to add a "metric-replay" feature in the
collector to monotonously export the on_change-type values.
On Tue, Jan 5, 2021 at 8:13 PM Ben Kochie wrote:
>
>
> On Tue, Jan 5, 2021 at 5:36 PM Roman Dodin wrote:
>
>> Thank you for your
On Tue, Jan 5, 2021 at 5:36 PM Roman Dodin wrote:
> Thank you for your comments, Stuart, maybe I expressed myself a bit vague.
> Let me be more precise and maybe then it will be easier to answer my
> question.
>
> The metric I am talking about is the number of routes a network element
> has in
Thank you for your comments, Stuart, maybe I expressed myself a bit vague.
Let me be more precise and maybe then it will be easier to answer my
question.
The metric I am talking about is the number of routes a network element has
in its routing table. This integer is reported to the collector
On 05/01/2021 15:35, Roman Dodin wrote:
Hello community,
I have a telemetry system that sends data into Prometheus when the
data changes (i.e. its a push-on-event mechanism, not a
sample/interval push)
That means, if a system is stable, then the last reported value can be
reported quite some
Hello community,
I have a telemetry system that sends data into Prometheus when the data
changes (i.e. its a push-on-event mechanism, not a sample/interval push)
That means, if a system is stable, then the last reported value can be
reported quite some time back.
Let's say this metric is called
6 matches
Mail list logo
