Did you try having only one entry of `targets` where you put both addresses
in one list ?
On Monday, September 14, 2020 at 3:42:41 PM UTC+2 suryapr...@gmail.com
wrote:
> Yes, /var/lib/prometheus is owned by the "prometheus" user.
>
> And /etc/prometheus/prometheus.yml content is below
>
>
Hello
1- you can use a CMS tool like ansible to salt to manage prometheus config
and update it in //
2- alertmanager will take care of deduplicating the alert
On Wednesday, October 14, 2020 at 9:32:20 PM UTC+2 yagyans...@gmail.com
wrote:
> Hi. I am moving from vanilla Prometheus setup to HA
:
> sayf.eddi...@gmail.com wrote:
> > Hi, you need a proper exporter
> > You can use https://github.com/prometheus/blackbox_exporter, it can
> > monitor DNS
>
> Do you have a sample configuration?
> Thanks.
>
> --
> Amari CH
> https://maddoghost.com/
&g
this is my systemd file
```
[Unit]
After=network.target
Description=prometheus server
Documentation=http://prometheus.io
[Service]
User=prometheus
Type=simple
EnvironmentFile=/etc/sysconfig/prometheus
ExecStart=/usr/bin/prometheus --config.file=/etc/prometheus/prometheus.yml
$EXTRA_ARGS
Hi, you need a proper exporter
You can use https://github.com/prometheus/blackbox_exporter, it can monitor
DNS
On Thursday, September 17, 2020 at 10:09:08 AM UTC+2 Amari CH wrote:
> Hello
>
> How can I setup prometheus to monitor the availability of name servers?
>
> regards.
>
> --
> Amari CH
Nice tip, thanks !
On Thursday, September 17, 2020 at 9:06:51 AM UTC+2 b.ca...@pobox.com wrote:
> Under [Service] I'd also recommend
>
> TimeoutStopSec=300
>
> This is to give prometheus more time to finish writing out its WAL if you
> do "systemctl stop" or "systemctl restart".
>
--
You
Hello, the proper way imho is to use a configuration management system like
saltstack, ansible etc. I would also package those exporters in OS packages
(rpm, deb) but that is not required given most of them do not have
dependencies
On Wednesday, September 23, 2020 at 2:05:15 AM UTC+2
The initial release of Prometheus was in 2012 so no one have tried it yet
:D. I am not super expert but I think 50 metrics is manageable on such
retention period (in your formula you forgot to take the labels into
consideration). But keep in mind prometheus has no data protection schemes
given
Hello, You can simply run 5 instances of Prometheus each with its own
configuration file, just make sure every instance is listening on a
different port
On Friday, September 18, 2020 at 11:58:07 AM UTC+2 karthiga...@gmail.com
wrote:
> Is it possible to create multiple target
Hello,
1- start by reading the guidelines and best practices from Prometheus
website https://prometheus.io/docs/instrumenting/writing_exporters/
Then check the Python prometheus_client (used to write exporters) which is
the best entry-level tool you can use
2- Before you start writing an
Hello,
Can you explain what you tried and how did you setup your monitoring system?
On Thursday, October 29, 2020 at 9:06:01 AM UTC+1 jorge.fer...@gmail.com
wrote:
> Hello, I am a Spanish guy trying to understand this tool! (Sorry for my
> English)
>
> My question is... why I can’t see in the
http://www.catb.org/~esr/faqs/smart-questions.html
On Monday, December 14, 2020 at 8:23:45 AM UTC+1 minhlu...@gmail.com wrote:
>
>
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails
Hi,
It depends on how the pods from the same node are sharing the GPU, but I
think it is doable if you configure the hpa to spawn new pods and the pods
to `request` GPU resources, this will force the GKE cluster autoscaler into
creating new nodes to locate the new pods.
Are you using KubeFlow
If you have an error in the config file, prometheus will just ignore the
new config and stays with the old one, check the logs of the container and
make sure there are not errors
On Friday, April 9, 2021 at 12:22:18 PM UTC+2 shutima.p...@geotwin.io wrote:
> Hello all,
>
> I am new to
Hello,
I want to test the behavior of my Prometheus setup (HA, and/or federation)
on large setup (resource consumption, possible crashes, latencies etc).
Are there any tool available for that?
I am thinking about using a small number of servers but configure them
multiple times in Prometheus
thanks I ll take a look
On Thursday, September 23, 2021 at 9:47:08 AM UTC+2 sup...@gmail.com wrote:
> Take a look at https://github.com/prometheus/test-infra
>
> This is what we use to benchmark changes and each release.
>
> On Thu, Sep 23, 2021 at 9:28 AM sayf.eddi...@gmail.co
Hello,
No I am not aware of such tool, but it shouldnt be hard to write a simple
exporter (maybe using python prometheus_client lib) to replay historical
data and expose it to a Prometheus/Alertmanager setup.
Or, given the alerts are also stored in the TSDB, you can build sth that
navigate the
I use the following jinja template to expose alertmanagers on
`/alertmanager`
*
Alertmanager###Header
add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e;
As a rule of thumb always start by looking in this page
https://prometheus.io/docs/instrumenting/exporters/
On Sunday, October 23, 2022 at 11:03:33 AM UTC+2 olivier...@outscale.com
wrote:
> Hello Giorgi !
>
> You have multiple SQL / query exporters that works with Psql, MySQL and
> even
Hello,
Monitoring the health of the system with Prometheus is fine. but I think
you are trying to include it as a functional brick in the application,
which I am not very keen with. imo The monitoring system should not coupled
with the functionning of your system (as in your system should
Hello
We have a large product with multiple exporters within different teams.
I was wondering if there is a standard on how to document each
application/exporter metrics and alerts. If not, Did you already encounter
such issue and what direction did you choose.
Cheers
--
You received this
If you have control on the version of systemd you can update and use the
credentials module https://systemd.io/CREDENTIALS/
On Friday, January 6, 2023 at 7:06:34 PM UTC+1 natach...@gmail.com wrote:
> Aaah, that is lovely. Thank you so much for pointing me in the right
> direction.
>
> On
I faced this issue in the design phase too, found this
https://github.com/beorn-/highlander but it looks a bit dead now...
else you can push duplicated metrics to thanos (while setting a unique
label for every prometheus instance) and then configure thanos querier to
deduplicate when serving
FWIW, we use saltstack based jinja2 templating with a configured systemd
reload (ExecReload=/bin/kill -HUP $MAINPID) to update the thresholds, and
it works fine
On Tuesday, February 28, 2023 at 9:31:12 AM UTC+1 Brian Candler wrote:
> After changing the rules file, you'll need to trigger a
Hello, I have looked online and I cant find any best practices for filling
up the description and the summary. from the examples I see that Summary
should be the shortest (plus the minimum usage of labels). But maybe it is
an observation bias.
I am trying to generate some automatic
readable the result.
I am considering the addition of an extra annotation field for that purpose
I think it is better to separate the concerns here.
On Monday, March 27, 2023 at 3:46:11 PM UTC+2 Stuart Clark wrote:
> On 2023-03-27 14:43, sayf.eddi...@gmail.com wrote:
> > Hello, I have look
mments be sufficient?
>
> On Monday, 27 March 2023 at 15:00:47 UTC+1 sayf.eddi...@gmail.com wrote:
>
>> Thanks for the response
>>
>> By generating automatic documentation I meant automatically creating
>> developer documentation of the existing alerts and their descript
Hello,
I am working on adding recording rules. But I dont see how to document them
in the code.
We have `HELP` entry for metrics, `description` and `summary` for alerts.
what about recording rules?
Best regards
--
You received this message because you are subscribed to the Google Groups
3 at 3:27 PM sayf.eddi...@gmail.com <
> sayf.eddi...@gmail.com> wrote:
>
>> Hello,
>>
>> I am working on adding recording rules. But I dont see how to document
>> them in the code.
>> We have `HELP` entry for metrics, `description` and `summary` for aler
29 matches
Mail list logo