Are you running either the Prometheus server or the web browser under Windows? STATUS_BREAKPOINT appears here: https://pkg.go.dev/golang.org/x/[email protected]/windows#pkg-constants
On Monday 12 February 2024 at 15:58:44 UTC Ben Kochie wrote: > On Mon, Feb 12, 2024, 16:39 Alexander Wilke <[email protected]> wrote: > >> Hello, > > thanks for the fast response. Unfortunately the linux environment I have >> is very restricted and I first have to check which snmpwalk tool I can use >> because downloads are very limited. >> Will take me some time but I think I will open the issue with the >> information I have. >> > > The output from the exporter is fine, no need for other tools. > > >> if I run ltmNodeAddresstype I can see a value of (1) for the IPs in the >> /Common partition which is the base partition and has no suffix like %xyz. >> Other partitions I have the suffix and the address Type value is (3). >> > > Yup, that's what I thought. > > >> So it is probably as you said: >> ipv4z(3) A non-global IPv4 address including a zone index as defined by >> the InetAddressIPv4z textual convention. >> >> >> PS: >> is it possible that this may cause instability of the prometheus webui? >> If I browse the "graph" page and searching for f5 metrics sometimes the >> rbwoser is showing a white error page "STATUS_BREAKPOINT". >> This is a test environment and maybe there something else wrong - however >> - it feels like it started with the monitoring of f5 devices via SNMP. >> > > No, this is just a failed string conversion. So you get the default hex > conversion instead. > > I don't know what your error is, but I am fairly sure this is unrelated to > Prometheus or SNMP data. > > >> Ben Kochie schrieb am Montag, 12. Februar 2024 um 15:20:05 UTC+1: >> >>> Looking at the MIB (F5-BIGIP-LOCAL-MIB), I see this MIB definition: >>> >>> ltmPoolMemberAddr OBJECT-TYPE >>> SYNTAX InetAddress >>> MAX-ACCESS read-only >>> STATUS current >>> DESCRIPTION >>> "The IP address of a pool member in the specified pool. >>> It is interpreted within the context of an ltmPoolMemberAddrType >>> value." >>> ::= { ltmPoolMemberEntry 3 } >>> >>> InetAddress syntax comes from INET-ADDRESS-MIB, which has several >>> conversion types. Without knowing what the device is exposing >>> for ltmPoolMemberAddrType it's hard to say, but I'm guessing it's type >>> 3, InetAddressIPv4z. >>> >>> I don't think we have this textual convention implemented in the >>> exporter. >>> >>> Would you mind filing this as an issue on GitHub? >>> * It would also be helpful to have the sample data as text, rather than >>> a screenshot. This makes it easier to work with for creating test cases. >>> * Please also include walks of `ltmPoolMemberAddrType` as well as >>> `ltmPoolMemberAddr` >>> >>> https://github.com/prometheus/snmp_exporter/issues >>> >>> It would also be helpful to have the sample data as text, rather than a >>> screenshot. This makes it easier to work with for creating test cases. >>> >>> On Mon, Feb 12, 2024 at 2:54 PM Alexander Wilke <[email protected]> >>> wrote: >>> >>>> Hello, >>>> >>>> I am using the snmp_exporter 0.25.0 and prometheus 2.49.1. >>>> >>>> I am collecting metrics from F5 LTM Loadbalancers. I want to collect >>>> the IP-Address. >>>> >>>> >>>> >>>> in general it is working however some IP-address formats are looking >>>> like that: >>>> >>>> >>>> >>>> 10.10.10.10 which I can import in the correct fromat >>>> >>>> >>>> >>>> Others a displayed by the F5 system like this: >>>> >>>> >>>> >>>> 10.10.10.10%0 >>>> >>>> or >>>> >>>> 10.10.10.10%1 >>>> >>>> >>>> >>>> The trailing %0 or %1 ... represents a logical separation on the >>>> system. >>>> >>>> >>>> >>>> The ingestion into prometheus works however the format is then >>>> different and looks like hex. Any chance to get the "raw" information or >>>> at >>>> least replace the trailing %0? >>>> >>>> >>>> [image: ip_address_format_includes_percent.jpg] >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Prometheus Users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/prometheus-users/dd89ed7e-a276-43ff-8bb1-5631ba98cfb7n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/prometheus-users/dd89ed7e-a276-43ff-8bb1-5631ba98cfb7n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Prometheus Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/prometheus-users/a5658075-d685-487e-9cac-5d16d3cb0e15n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/prometheus-users/a5658075-d685-487e-9cac-5d16d3cb0e15n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/ab1993d2-ba59-40d5-8fe7-179832f5e7a4n%40googlegroups.com.
