[Observium] Sensor limit nominal and delta OIDs need different scaling

Hi, We are trying to set appropriate limits for a frequency sensor. There are OIDs for the nominal frequency and the acceptable deviation from it. The problem is the nominal OID needs 0.1 scaling while the deviation OID needs 1 scaling (the measured value needs 0.1 scaling). Is there a way to hand

[Observium] Re: Incorrect sensor limits caused by duplicate unit conversion

mit_unit" is not set. On Tue, Sep 3, 2024 at 4:53 AM Mike Stupalov wrote: > Should be fixed since r13633 (trunk, rolling updates). > > Corwin Ziegler Hunts via observium wrote on 31.08.2024 03:43: > > The definition for the temperature sensor on a CyberPower PDU (or UPS) >

[Observium] Incorrect sensor limits caused by duplicate unit conversion

The definition for the temperature sensor on a CyberPower PDU (or UPS) environmental sensor accessory defines both "unit" and "limit_unit" as "F". This seems to cause the limit values to get converted (to Celsius) twice: first in "entity_limits_definition" using "limit_unit" and then in "discover_s

[Observium] Re: Bug report: Broken scaling on some SFP receive power graphs

We updated to r13611. The graphs are much better now. On Tue, Aug 6, 2024 at 9:58 AM Adam Armstrong via observium < observium@lists.observium.org> wrote: > Try r13609! > > adam. > > Corwin Ziegler Hunts via observium wrote on 2024-08-05 20:13: > > These sensors show

[Observium] Re: Bug report: Broken scaling on some SFP receive power graphs

need an explicit toggle to turn the > autoscale off, though the logic for the autoscale decision code is already > pretty messy and confusing. > > adam. > > > Corwin Ziegler Hunts via observium wrote on 2024-07-27 00:54: > > Is there any guidance towards resolving these i

[Observium] Re: Missing rebuild buttons for groups and alert checkers

gt; to cause some confusion, so I probably won't put the button back. > > Thanks, > adam. > > Corwin Ziegler Hunts via observium wrote on 2024-07-29 20:54: > > Hi, > > We use Observium groups extensively, often nested several times. Our alert > checkers then refer

[Observium] Missing rebuild buttons for groups and alert checkers

Hi, We use Observium groups extensively, often nested several times. Our alert checkers then reference these groups. After making changes to a group, including by adding a device, we used to force rebuilds of the groups (possibly several times) and checkers so the changes would propagate all the w

[Observium] Re: Bug report: Broken scaling on some SFP receive power graphs

m Armstrong via observium < > observium@lists.observium.org> wrote: > >> so many words, but no pictures. >> >> Corwin Ziegler Hunts via observium wrote on 2024-06-25 19:13: >> >> Hi Observium team, >> >> We're having issues with some of the gener

[Observium] Re: Bug report: Broken scaling on some SFP receive power graphs

dBm, set option: > Global Settings -> Entities -> (Ports) Convert Port DOM power sensors to > dBm. > > Corwin Ziegler Hunts via observium wrote on 25.06.2024 21:13: > > Hi Observium team, > > We're having issues with some of the generated graphs. Some of our devic

[Observium] Re: Bug report: Broken scaling on some SFP receive power graphs

Pictures attached. On Tue, Jun 25, 2024 at 11:47 AM Adam Armstrong via observium < observium@lists.observium.org> wrote: > so many words, but no pictures. > > Corwin Ziegler Hunts via observium wrote on 2024-06-25 19:13: > > Hi Observium team, > > We're having i

[Observium] Bug report: Broken scaling on some SFP receive power graphs

Hi Observium team, We're having issues with some of the generated graphs. Some of our devices report the light level received by SFPs using mW (rather than dBm). We are on the latest stable revision (13582). Issue 1: The graphs generated by Observium for these sensors usually show an excessive sc

[Observium] Obtaining good thresholds for monitoring SFP light levels

We would like to alert if an SFP's received light level is too low. The light level sensor data is present and linked with a specific port so we can adjust the alert checkers based on attributes of the linked port. What we haven't figured out how to do is get appropriate thresholds for alerting for

[Observium] device_rebooted metric is now NULL instead of 1

We have an alert checker using the device_rebooted metric to monitor for reboots. The metric used to read as 1 when a reboot was detected as is documented . After updating to the latest stable revision (r13020) from r12520 the metric now reads as NULL im

[Observium] Bug report: multiple devices API call breaks when filtering fields

The multiple devices API call combined with field filtering fails for us in the latest stable release, revision 12520 from 2023-02-08. The API call responds with an HTTP 200 but the data contained in the response is incomplete. It worked when we were on revision 12342 from 2022-10-24. It still work