Ad Widget

Collapse

graph outside the quadrant

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • just2blue4u
    Senior Member
    • Apr 2006
    • 347

    #1

    graph outside the quadrant

    Hi there!

    I added a new item (CPU interrupts (system.cpu.intr)).
    As also described here, my graph was outside the quadrant, when i watched the graph.

    After waiting about 2h, i watched that graph again and it was generated correctly.
    When i switched the range to 2h (so that the first value was displayed again), the graph was drawn outside the range again.

    The y-axis scaling is dynamic. If i define static values for the y-axis, everything is fine.

    is this a bug?

    greets,
    J2B4U
    Big ZABBIX is watching you!
    (... and my 48 hosts, 4513 items, 1280 triggers via zabbix v1.6 on CentOS 5.0)
  • just2blue4u
    Senior Member
    • Apr 2006
    • 347

    #2
    I still have those Problems of values shown outside the graph. here is a screenshot of that problem.

    When i switch y-scaling to fixed, everything looks great; after turning back to "calculated", zabbix draws crap again. It doesn't matter if i watch the graph in "latest values" or in a screen, together with other graphs. Its simply messed up...
    Big ZABBIX is watching you!
    (... and my 48 hosts, 4513 items, 1280 triggers via zabbix v1.6 on CentOS 5.0)

    Comment

    • teferi
      Member
      • Jul 2008
      • 93

      #3
      Originally posted by just2blue4u
      I still have those Problems of values shown outside the graph. here is a screenshot of that problem.

      When i switch y-scaling to fixed, everything looks great; after turning back to "calculated", zabbix draws crap again. It doesn't matter if i watch the graph in "latest values" or in a screen, together with other graphs. Its simply messed up...
      Sorry for bringing it up from the dead but the problem is quite similar. I may post a screenshot if needed. this happens on 1.5.3 and only if graph uses items from several different hosts. When Yaxis type is set to calculated the top value of Yaxis is always 0.3 on all the graphs. Setting Yaxis type to fixed is a somewhat like workaround for the problem in my case.

      Comment

      • teferi
        Member
        • Jul 2008
        • 93

        #4
        Sorry again. On a closer look it appeared to be a bug in my graph-creating script =) Seems like it didn't set graphs_item's type to a correct value =)

        Comment

        Working...