Uploaded image for project: 'Runtime'
  1. Runtime
  2. RUNTIME-881

Monitoring rrd images are not always rendered

XMLWordPrintable

      The scaling of the y-axis values is disabled for some sample manager. (See classes that inherits from org.ametys.runtime.plugins.core.administrator.jvmstatus.monitoring.sample.AbstractSampleManager)

      In case of a very high y-axis max-value, the generation of the graph will fails :

      Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
	at org.rrd4j.graph.ValueAxis.draw(ValueAxis.java:98)
	at org.rrd4j.graph.RrdGraph.drawGrid(RrdGraph.java:193)
	at org.rrd4j.graph.RrdGraph.createGraph(RrdGraph.java:75)
	at org.rrd4j.graph.RrdGraph.<init>(RrdGraph.java:40)
	at org.ametys.runtime.plugins.core.monitoring.RRDGraphReader.generate(RRDGraphReader.java:102)
	at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processReader(AbstractCachingProcessingPipeline.java:901)
	... 47 more

      This is dues to the configuration of the graph definition graphDef.setUnitsExponent(0);. This line is present in the method _populateGraphDefinition of some sample manager (for example, the disk IO sample manager, or the http request sample manager)

          [RUNTIME-881] Monitoring rrd images are not always rendered

          Nicolas Gavalda (Inactive) added a comment -

          Should be resolved now that we have upgraded to rrd4j 2.2 and fixed the wrong http request count.

          Nicolas Gavalda (Inactive) added a comment - Should be resolved now that we have upgraded to rrd4j 2.2 and fixed the wrong http request count.

          Raphaël Franchet added a comment -

          The httprequestsamplemanager has been modified: currently, by mistake, it was summing all connections => this used to lead to huge numbers. Now that is has been fixes the numbers are low and this does not happen anymore.

          In runtime 3.X this has been fixes by upgrading rrd4j

          Raphaël Franchet added a comment - The httprequestsamplemanager has been modified: currently, by mistake, it was summing all connections => this used to lead to huge numbers. Now that is has been fixes the numbers are low and this does not happen anymore. In runtime 3.X this has been fixes by upgrading rrd4j

            ngavalda Nicolas Gavalda (Inactive)
            trizzi Thibaut Rizzi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: