PRs welcome.
But remember, any changes need to support mmap for efficient caching of
stored data.
On Fri, Aug 26, 2022 at 7:10 AM Mega Rajan wrote:
> Thanks for the reply.
>
> I digged in and saw that Prometheus uses Gorilla compression.
>
> Do we have option to change the compression method
Thanks for the reply.
I digged in and saw that Prometheus uses Gorilla compression.
Do we have option to change the compression method to something else . I
see that Gorilla compression is an efficient one but wanted a confirmation
on whether there is a way to change it to something else
Yes, Prometheus uses compression.
See: https://www.youtube.com/watch?v=b_pEevMAC3I
Also, I highly recommend upgrading to the latest release. The version you
are running is from 2018 and has numerous bugs.
On Fri, Aug 26, 2022 at 7:03 AM Mega Rajan wrote:
> hi
>
> we are using prometheus 2.3.1
hi
we are using prometheus 2.3.1 .
Does prometheus use compression to store its data ?
>From the documentation I see that its being compacted but no reference to
compression and any compression algorithm as such .
could anyone please clarify on the compression and compression algorithm
used
Ben,
Thank you, I was able to proceed after upgrading go version, but the latest
errors are when I do "make build". Do you have any idea? the mibs directory
was created but nothing inside.
#make mibs
mkdir: created directory ‘mibs’
>> Downloading apc-powernet-mib
make: ***
Hi Brian,
We will have a look at the suggestions.
Thanks!
On Thursday, August 25, 2022 at 12:05:00 PM UTC-7 Brian Candler wrote:
> If you read your error message carefully:
>
> > I am getting 'Get "http://blackbox-dev.xyz.com:443/metrics: context
> deadline exceeded"
>
> then it looks like
If you read your error message carefully:
> I am getting 'Get "http://blackbox-dev.xyz.com:443/metrics: context
deadline exceeded"
then it looks like Prometheus is trying to talk to an http:// endpoint; but
you said it was https://.
Put "scheme: https" in your scrape job config to use https.
Hi Brian,
Any inputs on this issue ?
Thanks!
On Wednesday, August 24, 2022 at 11:04:26 AM UTC-7 Santanu Mishra wrote:
> Hi Team,
> I have a blackbox container running as "
> https://blackbox-dev.xyz.com/; in a OpenShift cluster. I have Prometheus
> running as separate container
On Thursday, 25 August 2022 at 14:39:57 UTC+1 sando...@gmail.com wrote:
>
> Since our targets has unique naming per cluster (For eg: router111, router
> 112, hypervisor111, hypervisor112, instance111, instance112), is there a
> way to group them based on their naming? Like all nodes which has
On Thursday, 25 August 2022 at 11:36:59 UTC+1 melee.j...@gmail.com wrote:
> 1) [image: 2022-08-25_20-10-14.png]
>
> 2) I was checking with tcpdump. Don't know if I'm on pair with your theory
> cause client (blackbox) sending syn immediately after receiving "large" udp
> packet.
>
Does tcpdump
Hi Brian,
Thanks for your response. I created common labels for each category
something like below and I see 3 groupings in the alertmanager now.
Since our targets has unique naming per cluster (For eg: router111, router
112, hypervisor111, hypervisor112, instance111, instance112), is there a
Thanks, Brian. It really helped me.
I want to find the Downtime of the instance in a similar way to how we will
find the up time of the instance.
Up time : time() - node_boot_time_seconds{instance=~"$instance"}
Is there any metric in node exporter so that we can find the downtime of
the
For many reasons, I've been deploying node local DNS caching for production
servers for a while now.
I can highly recommend CoreDNS for this. It should also provide good
metrics as to the behavior of your central resolvers.
On Thu, Aug 25, 2022, 12:37 PM terrible person
wrote:
> 1) [image:
1) [image: 2022-08-25_20-10-14.png]
2) I was checking with tcpdump. Don't know if I'm on pair with your theory
cause client (blackbox) sending syn immediately after receiving "large" udp
packet. As I said I don't see this behavior with dig, nor I see the
truncated flag. UDP response from
What is this "DNSLookupDuration3s" you talk about? Is it an alerting
rule? Can you show the expr?
To me, it sounds like the opposite problem. My guess is that
blackbox_exporter is first making a UDP DNS query, and either the query or
the response is being blocked. So after 3 seconds it
The blackbox_exporter uses the built-in Go resolver library[0]. The only
options here are which address family you want in return.
[0]: https://pkg.go.dev/net#Resolver.LookupIP
On Thu, Aug 25, 2022 at 7:35 AM terrible person
wrote:
> Thank you, actually I found out about this behaviour just
Hi All,
I want to find the Down time of the instance in the similar way how we will
find up time of the instance?
Up time : time() - node_boot_time_seconds{instance=~"$instance"}
Is there any metric in node exporter so that we can find the down time of
the instance?
Thanks & regards,
Bharath
17 matches
Mail list logo
