Re: [prometheus-developers] Removing fuzzit from Prometheus

2020-12-09 Thread Julien Pivotto 


Thanks all.

Fuzzit has been removed from Prometheus, thanks to them for having us on
board!

The PR that removed fuzzit also enables oss-fuzz in PR's.
https://github.com/prometheus/prometheus/pull/8269


On 09 Dec 19:52, Bartłomiej Płotka wrote:
> Yes please (:
> 
> Kind Regards,
> Bartek Płotka (@bwplotka)
> 
> 
> On Wed, 9 Dec 2020 at 18:43, Julius Volz  wrote:
> 
> > Yeah, since we also have oss-fuzz now, it's fine to remove fuzzit IMO.
> >
> > On Tue, Dec 8, 2020 at 6:03 PM Brian Brazil <
> > brian.bra...@robustperception.io> wrote:
> >
> >> On Tue, 8 Dec 2020 at 16:04, Julien Pivotto 
> >> wrote:
> >>
> >>> Hi all,
> >>>
> >>> I'd like to remove fuzzit from Prometheus/prometheus.
> >>>
> >>> The CI job is causing CI issues:
> >>> https://circleci.com/workflow-run/a12eb33e-84a1-4eb0-9b9b-57c89b53271d
> >>>
> >>> Additionally, the image we are using is not maintained and is blocking
> >>> us on go 1.12 for the packages covered by fuzzing:
> >>> fuzzitdev/golang:1.12.7-buster
> >>>
> >>> It is also not clear how long the fuzzit service will work in the
> >>> future:
> >>> https://fuzzit.dev/2020/06/11/news-fuzzit-is-acquired-by-gitlab/
> >>>
> >>>
> >>> Last, Prometheus is being fuzzed by https://github.com/google/oss-fuzz
> >>> so we are not giving up on fuzzing.
> >>>
> >>
> >> Sounds reasonable to me.
> >>
> >> Brian
> >>
> >>
> >>>
> >>>
> >>> --
> >>> Julien Pivotto
> >>> @roidelapluie
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google
> >>> Groups "Prometheus Developers" group.
> >>> To unsubscribe from this group and stop receiving emails from it, send
> >>> an email to prometheus-developers+unsubscr...@googlegroups.com.
> >>> To view this discussion on the web visit
> >>> https://groups.google.com/d/msgid/prometheus-developers/20201208160405.GA717510%40oxygen
> >>> .
> >>>
> >>
> >>
> >> --
> >> Brian Brazil
> >> www.robustperception.io
> >>
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "Prometheus Developers" group.
> >> To unsubscribe from this group and stop receiving emails from it, send an
> >> email to prometheus-developers+unsubscr...@googlegroups.com.
> >> To view this discussion on the web visit
> >> https://groups.google.com/d/msgid/prometheus-developers/CAHJKeLq1M_wfGj%3D90ZMOCKYoZGj%2BTgNGQWY4duyJ%3DTQxYB9n6Q%40mail.gmail.com
> >> 
> >> .
> >>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Prometheus Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to prometheus-developers+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/prometheus-developers/CA%2BT6Yox%2B%2BPKPLxhtWevJZjyEbNvFqgbXXJbnmuM-7Ytdpw2P3A%40mail.gmail.com
> > 
> > .
> >
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Prometheus Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to prometheus-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/prometheus-developers/CAMssQwYiCY_SyAE0Wwm%3Dref330JdxoUe%2BMEApySbB7TLbd0_Sg%40mail.gmail.com.

-- 
Julien Pivotto
@roidelapluie

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prometheus-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-developers/20201209234223.GA427586%40oxygen.

Re: [prometheus-developers] Removing fuzzit from Prometheus

2020-12-09 Thread Bartłomiej Płotka 
Yes please (:

Kind Regards,
Bartek Płotka (@bwplotka)


On Wed, 9 Dec 2020 at 18:43, Julius Volz  wrote:

> Yeah, since we also have oss-fuzz now, it's fine to remove fuzzit IMO.
>
> On Tue, Dec 8, 2020 at 6:03 PM Brian Brazil <
> brian.bra...@robustperception.io> wrote:
>
>> On Tue, 8 Dec 2020 at 16:04, Julien Pivotto 
>> wrote:
>>
>>> Hi all,
>>>
>>> I'd like to remove fuzzit from Prometheus/prometheus.
>>>
>>> The CI job is causing CI issues:
>>> https://circleci.com/workflow-run/a12eb33e-84a1-4eb0-9b9b-57c89b53271d
>>>
>>> Additionally, the image we are using is not maintained and is blocking
>>> us on go 1.12 for the packages covered by fuzzing:
>>> fuzzitdev/golang:1.12.7-buster
>>>
>>> It is also not clear how long the fuzzit service will work in the
>>> future:
>>> https://fuzzit.dev/2020/06/11/news-fuzzit-is-acquired-by-gitlab/
>>>
>>>
>>> Last, Prometheus is being fuzzed by https://github.com/google/oss-fuzz
>>> so we are not giving up on fuzzing.
>>>
>>
>> Sounds reasonable to me.
>>
>> Brian
>>
>>
>>>
>>>
>>> --
>>> Julien Pivotto
>>> @roidelapluie
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Prometheus Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to prometheus-developers+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/prometheus-developers/20201208160405.GA717510%40oxygen
>>> .
>>>
>>
>>
>> --
>> Brian Brazil
>> www.robustperception.io
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Prometheus Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to prometheus-developers+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/prometheus-developers/CAHJKeLq1M_wfGj%3D90ZMOCKYoZGj%2BTgNGQWY4duyJ%3DTQxYB9n6Q%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Prometheus Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to prometheus-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-developers/CA%2BT6Yox%2B%2BPKPLxhtWevJZjyEbNvFqgbXXJbnmuM-7Ytdpw2P3A%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prometheus-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-developers/CAMssQwYiCY_SyAE0Wwm%3Dref330JdxoUe%2BMEApySbB7TLbd0_Sg%40mail.gmail.com.

Re: [prometheus-developers] Removing fuzzit from Prometheus

2020-12-09 Thread Julius Volz 
Yeah, since we also have oss-fuzz now, it's fine to remove fuzzit IMO.

On Tue, Dec 8, 2020 at 6:03 PM Brian Brazil <
brian.bra...@robustperception.io> wrote:

> On Tue, 8 Dec 2020 at 16:04, Julien Pivotto 
> wrote:
>
>> Hi all,
>>
>> I'd like to remove fuzzit from Prometheus/prometheus.
>>
>> The CI job is causing CI issues:
>> https://circleci.com/workflow-run/a12eb33e-84a1-4eb0-9b9b-57c89b53271d
>>
>> Additionally, the image we are using is not maintained and is blocking
>> us on go 1.12 for the packages covered by fuzzing:
>> fuzzitdev/golang:1.12.7-buster
>>
>> It is also not clear how long the fuzzit service will work in the
>> future:
>> https://fuzzit.dev/2020/06/11/news-fuzzit-is-acquired-by-gitlab/
>>
>>
>> Last, Prometheus is being fuzzed by https://github.com/google/oss-fuzz
>> so we are not giving up on fuzzing.
>>
>
> Sounds reasonable to me.
>
> Brian
>
>
>>
>>
>> --
>> Julien Pivotto
>> @roidelapluie
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Prometheus Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to prometheus-developers+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/prometheus-developers/20201208160405.GA717510%40oxygen
>> .
>>
>
>
> --
> Brian Brazil
> www.robustperception.io
>
> --
> You received this message because you are subscribed to the Google Groups
> "Prometheus Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to prometheus-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-developers/CAHJKeLq1M_wfGj%3D90ZMOCKYoZGj%2BTgNGQWY4duyJ%3DTQxYB9n6Q%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prometheus-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-developers/CA%2BT6Yox%2B%2BPKPLxhtWevJZjyEbNvFqgbXXJbnmuM-7Ytdpw2P3A%40mail.gmail.com.

Re: [prometheus-developers] Multiple metrics path for Prometheus

2020-12-09 Thread Christian Hoffmann 

Hi,

On 12/9/20 12:42 PM, rakshit gupta wrote:
How can (is it possible) I use multiple endpoints for metrics scraping 
in a job ?


# The HTTP resource path on which to fetch metrics from targets.
  [ metrics_path:  
 
| default = /metrics ]


In my use case, a service( registered to consul) can expose metrics in 
any one of the endpoints - /metrics, /actuator/info, etc, and I need 
generic configuration in Prometheus to scrape data by probably iterating 
through the endpoints. I cannot hard code the endpoint there that 
/metrics is my endpoint.


I don't think this is possible or a good idea. You would need to decide 
which metrics path to use. If you have this information (e.g. during 
service discovery), then you can place those targets in different scrape 
jobs or even re-use the sample scrape job and relabel __metrics_path__ 
accordingly.


If SD doesn't provide this information, another option would be to 
provide it via your configuration management system (e.g. probe your 
targets regularly and see what endpoint is the right one; then record 
this information).


If this information is not available to you, then the only other option 
would be to create scrape jobs for all variants. Two of those three 
would always fail. I don' think it would be a good idea or simple to 
work with.


Kind regards,
Christian

--
You received this message because you are subscribed to the Google Groups 
"Prometheus Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prometheus-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-developers/e51af840-f9cf-e4c8-a511-e6eac7e4ec4e%40hoffmann-christian.info.

[prometheus-developers] Multiple metrics path for Prometheus

2020-12-09 Thread rakshit gupta 
Hi, 

How can (is it possible) I use multiple endpoints for metrics scraping in a 
job ?

# The HTTP resource path on which to fetch metrics from targets.
 [ metrics_path:  

 
| default = /metrics ]  

In my use case, a service( registered to consul) can expose metrics in any 
one of the endpoints - /metrics, /actuator/info, etc, and I need generic 
configuration in Prometheus to scrape data by probably iterating through 
the endpoints. I cannot hard code the endpoint there that /metrics is my 
endpoint.

Thanks for your help in advance!


-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prometheus-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-developers/cfc2735e-26e5-4930-b20e-3a1915b3d8aan%40googlegroups.com.