Thanks for sharing your wisdom and for correcting my misunderstanding about
registering from init causing duplicate registration. I demonstrated both
collectors as package level variables (package flipper) and struct members
(package flopper) at https://github.com/vickleford/promex as an
Thank you so much for the pointer Christian.
It resolved the issue.
Thanks
Sunil Sagar
On Sun, Apr 5, 2020 at 12:58 AM Christian Hoffmann <
m...@hoffmann-christian.info> wrote:
> On 4/4/20 6:42 PM, Sagar wrote:
> > relabel_configs:
> > - action: drop
> >source_labels:
Hi,
On 4/4/20 6:54 PM, Adso Castro wrote:
> I'm trying to create a silence using regex from the AlertManager UI and
> I want to silence alarms from deployments (from my Kubernetes cluster)
> like below:
>
> *new-batch-stream-**g1343*
> *super-batch-pipeline-g1273*
> *
> *
> The match would be
On 4/4/20 6:42 PM, Sagar wrote:
> relabel_configs:
> - action: drop
> source_labels: [replica]
> regex: (.*)
[...]
>
> For other server, replica is secondary
> I want to drop only label in alert manager , but it drops entire alert
> in alert_manager.
Ah, now I see the
Hi all,
I'm trying to create a silence using regex from the AlertManager UI and I
want to silence alarms from deployments (from my Kubernetes cluster) like
below:
*new-batch-stream-**g1343*
*super-batch-pipeline-g1273*
The match would be the word "batch". I've tried a few times using the
Hi Christian,
Thank you for the helping hand .
My prometheus.yml file looks like this :
global:
external_labels:
dc: europe
replica: primary
alerting:
alertmanagers:
- static_configs:
- targets:
- am:9093
relabel_configs:
- action: drop
It is marathon_sd_config (
https://prometheus.io/docs/prometheus/latest/configuration/configuration/#marathon_sd_config),
prometheus get instances from service discovery (marathon), and call them
directly, i think it something wrong with prometheus merathon_sd module.
суббота, 4 апреля 2020
I assume you're hitting the metrics through some kind of load balancer.
Prometheus assumes direct access to each instance of an application, rather
than through a load balancer.
On Sat, Apr 4, 2020 at 2:53 PM Ivan Pohodnya wrote:
>
> Hello everyone, i have question about rolling update
On Saturday, 4 April 2020 10:43:27 UTC+1, Belmark Caday wrote:
>
> Here are the udpdated tests :
>
> - series: 'node_filesystem_free{fstype="ext4"}'
>values: '1+0x120'
>
> - expr: 'predict_linear(node_filesystem_free{fstype!~"tmpfs"}[1h], 4 *
> 3600) > 0'
Here are the udpdated tests :
- series: 'node_filesystem_free{fstype="ext4"}'
values: '1+0x120'
- expr: 'predict_linear(node_filesystem_free{fstype!~"tmpfs"}[1h], 4 *
3600) > 0'
Here are the test's ive updated :
Series and values:
[image: Capture1.PNG]
Expr :
[image: Capture2.PNG]
And here is the error message :
[image: Capture3.PNG]
On Saturday, April 4, 2020 at 5:05:49 PM UTC+8, Brian Candler wrote:
>
> Put at least two data points in the time series.
>
--
Put at least two data points in the time series.
--
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 prometheus-users+unsubscr...@googlegroups.com.
To view this
On Sat, 4 Apr 2020 at 00:27, Victor Watkins wrote:
> Hi! This question is about best practices for testing applications that
> use client_golang to instrument with custom metrics and avoiding the
> dreaded "duplicate metrics collector registration attempted".
>
> Let's say I have an HTTP handler
13 matches
Mail list logo
