Skip to:

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

Introduce better parameter handling for graph definitions

Description

Currently, the snmp-graph.properties and the response-graph.properties contains a plain rrd-graph command. Introducing additional parameters allows to simplify the process of defining graphs and solves escaping problems.

For each graph definition (i.e. mib2.bits) allow a set of predefined additional parameters, like title, width, height, vertical-label, etc.
In addition, the parameters should be accessible through API,allowing to overwrite predefined values (i.e. KSC reports, Ops-Board / -Panel, including in 3rd-party).

If a property is not specified, a global default should be specify in a similar manner.

Example:

default.width=600 default.height=150 report.mib2.bits.name=Bits In/Out report.mib2.bits.title=Bits In/Out report.mib2.bits.width=800 # Overwrites default for single report #report.mib2.bits.height=... Inherited from default report.mib2.bits.vertical-label=Bits per second report.mib2.bits.command=DEF....

The graph author must not care about quoting and escaping and the properties can be overwritten by code without parsing the command string.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Ron Roskens November 27, 2014 at 6:52 PM

https://opennms.atlassian.net/browse/NMS-2165#icft=NMS-2165 suggested converting from properties formatted files to an xml format for graphs.

Ronny Trommer November 27, 2014 at 2:55 PM

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

PagerDuty

Created November 27, 2014 at 2:43 PM
Updated September 21, 2021 at 9:15 PM

Flag notifications