This is a pretty standard lookup. But the MIB entry for
lgpEnvTemperatureDescrDegC is a bit strange. You can override the type
easily to make it a DisplayString. But, based on your output, I'm guessing
the device doesn't return a useful description. Can you provide an SNMP
walk comparison?
Here's
generating snmp.yaml from mibs and I'm receiving some unexpected results:
*# HELP lgpEnvTemperatureMeasurementTenthsDegC The measured temperature
value. - 1.3.6.1.4.1.476.1.42.3.4.1.3.3.1.50# TYPE
lgpEnvTemperatureMeasurementTenthsDegC
Using vendor supplied mibs, added a module, generated my snmp.yml, and
snmp_exporter is giving me some unexpected results such as:
# HELP lgpEnvTemperatureMeasurementDegC The measured temperature value. -
1.3.6.1.4.1.476.1.42.3.4.1.3.3.1.3
# TYPE lgpEnvTemperatureMeasurementDegC gauge
Thanks Alexander,
I’m not aware you can setup a timeout in the snmp.yml, or at least I’m not
familiar with it?
The name of the interface is a regex string to match only interface names
with a ‘/‘ in them. So on Cisco will only match physical interfaces like
Gig1/0/1 and not stuff like Loopback0
Thanks for the hint. I checked the Go DNS feature and found these hints:
1. export GODEBUG=netdns=go # force pure Go resolver
2. export GODEBUG=netdns=cgo # force cgo resolver
I tried to set the cgo env variable and restarted services. however
systemd-resolved and nscd seem not to
Hello,
1.) is the timeout of 50s the same on prometheus scrape_config and snmp.yml
file?
2.) is this really the name of the interface? ifHCInOctetsIntfName
3) the =~".*.\\/.*." maybo shows many interfaces, maybe som internal
loppback which may count traffic twice? Further it may show
To clarify, my scrapes for this data run every 1m and have a timeout of 50s
On Friday 15 March 2024 at 22:41:52 UTC Nick Carlton wrote:
> Hello Everyone,
>
> I have just seen something weird in my environment where I saw interface
> bandwidth on a gigabit switch reach about 1tbps on some of the
All of the Prometheus components you're talking about are
statically compiled Go binaries. These use Go's native DNS resolution. It
does not use glibc. So maybe looking for solutions related to Golang and
nscd would help. I've not looked into this myself.
But on the subject of node local DNS
Hello,
I am running blackbox_exporter and smokeping_prober on a RHEL8 environment.
Unfortunately with our configu wie have around 4-5 million DNS queries per
24hrs.
The reason for that is that we do very frequent tcp queries to various
destinations which results in many DNS requests.
To
> What would you recommend in a situation with several hundredes or
thousands of servers or systems within a kubernetes cluster which should
have the node_exporter installed.
I would just scrape them normally, using service discovery to identify the
nodes to be scraped. Implicitly you're
10 matches
Mail list logo
