Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

POW Arithmetic Operator Does not work with Backshift Graphing Engine

Description

When using the default graphing engine to backshift "org.opennms.web.graphs.engine=backshift" the Arithmetic POW Operator does not work.
The same works when we set the grahing engine to "png"

RRD Docs on Arithmetic Operator

https://oss.oetiker.ch/rrdtool/doc/rrdgraph_rpn.en.html

RPN-Eval Code in ONMS

https://github.com/OpenNMS/backshift/blob/925662f6cbcf5a23a699942edd10fd1204d1609f/src/Backshift.Utilities.RpnEvaluator.js

 

Graph Definitions

With PNG

With +Backshift

+

Acceptance / Success Criteria

None

Attachments

4

Lucidchart Diagrams

Activity

Show:

Dmitri Herdt May 3, 2023 at 1:30 PM

PR:

Sriraag Sridhar April 13, 2023 at 4:00 PM

I see POW Added in below file

But no POW in this file below, not sure if that could be the issue ??

Sergio Garcia April 13, 2023 at 3:18 PM

I saw that this was reopened. Let me know if I can help with testing in any way.

Sergio Garcia April 12, 2023 at 9:12 PM

Hello team,

I have updated to Horizon 31.0.6 and still have the issue with Backshift not properly displaying graphs that are using the POW function in the SNMP graph definition. Here is what I have defined:

However, I’m not seeing any graphs being created:

If I set the graphing engine to PNG, it works fine:

I believe this is the same issue that Sriraag had. I’m not sure if this is an issue with Backshift per se, but I wanted to post in here first before opening a new issue or re-opening this one.

Benjamin Reed March 14, 2023 at 8:17 PM

I tagged a new Backshift version with the POW fixes (and some other changes that never got released). PR for applying the updated version in foundation-2020 is awaiting review.

Fixed

Details

Assignee

Reporter

Labels

HB Grooming Date

HB Backlog Status

FD#

Components

Sprint

Fix versions

Affects versions

Priority

Parent

PagerDuty

Created September 26, 2022 at 5:50 AM
Updated May 9, 2023 at 1:40 PM
Resolved May 9, 2023 at 1:40 PM