Hi srikanth ,
Could you share the solution.
On Tuesday, 29 December 2020 at 02:55:01 UTC+5:30 srikanth rangan wrote:
> I got it to work finally.
>
>
>
>
> On Thu, Dec 24, 2020 at 8:18 PM srikanth rangan
> wrote:
>
>> Hi all,
>> I have a case wherein I have to poll a target and its normal for
Just judging from the Prometheus config above, Prometheus was scraping the
401 status code targets directly, vs. probing them through the blackbox
exporter, since the necessary relabeling rules (
https://github.com/prometheus/blackbox_exporter#prometheus-configuration)
for that were missing.
On Fr
Can you provide the solution?
On Tuesday, 29 December 2020 at 02:55:01 UTC+5:30 srikanth rangan wrote:
> I got it to work finally.
>
>
>
>
> On Thu, Dec 24, 2020 at 8:18 PM srikanth rangan
> wrote:
>
>> Hi all,
>> I have a case wherein I have to poll a target and its normal for the site
>> to
I got it to work finally.
On Thu, Dec 24, 2020 at 8:18 PM srikanth rangan
wrote:
> Hi all,
> I have a case wherein I have to poll a target and its normal for the site
> to send me "401" code.
> However, when I add the entries in prometheus.yml and a new module in
> blackbox_exporter.yml, prom
Hi all,
I have a case wherein I have to poll a target and its normal for the site
to send me "401" code.
However, when I add the entries in prometheus.yml and a new module in
blackbox_exporter.yml, prometheus does not like the 401 error and does not
seem to use the blackbox_exporter at all. (I'v
5 matches
Mail list logo