Graphs saved with areamode=stacked will load without "stacked" applied

Bug #1026333 reported by Josh Behrends
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Graphite
New
Medium
Nicholas Leskiw

Bug Description

This applies to Graphite v0.9.10
This has also been reproduced on CentOS 6.2 and Ubuntu 10.04

Any graph I create and apply an area mode of "stacked" and then save will load without a mode of "stacked". I have also tried enabling "stacked" and then added a graph title and saved. Then went to load the saved graph and stacked was no longer applied and there was no title applied.

Here are example URL's:

Graph URL Before saving:
http://graph01/render/?_salt=1342646294.419&target=myserver.AA.servers.serverxy01.cpu.0.cpu.wait&target=myserver.AA.servers.serverxy01.cpu.1.cpu.wait&width=586&height=308&areaMode=stacked

Graph URL after loading saved graph:
http://graph01/render/?_salt=1342646310.167&target=myserver.AA.servers.serverxy01.cpu.0.cpu.wait&target=myserver.AA.servers.serverxy01.cpu.1.cpu.wait&width=586&height=308

I also opened graphite.db in a sqlite viewer and found that the graph URL was in fact saved with &areaMode=stacked saved to the end.

description: updated
Revision history for this message
Joey Imbasciano (joey-imbasciano) wrote :

I have confirmed this bug on Ubuntu 12.04 with Graphite v0.9.10

Reproduce:

1. Create graph with stacked option.
2. Save graph.
3. Load graph, stacked is not applied to the graph.

Revision history for this message
Daniel Goulder (daniel-goulder) wrote :

Confirmed this bug exists also on Solaris 10/Graphite 0.9.10 built against the following:
Python 2.6.4
Django 1.4.1
django-tagging-0.3.1
Cairo 1.12.2/libpng 1.5.12
zope-interface 4.0.1

Same steps to reproduce as Joey above

Revision history for this message
Nicholas Leskiw (nleskiw) wrote :

I'll bet that saving a graph only saves the target= parameter, not all the parameters.

Changed in graphite:
assignee: nobody → Nicholas Leskiw (nleskiw)
importance: Undecided → Medium
Revision history for this message
Jason Antman (jason-jasonantman) wrote :

This affects me as well, graphite 0.9.10.

It seems that the params are saved correctly. From graphite.db:
http://graphite/render/?_salt=1350568723.93&width=1032&height=711&title=Prod%20Celery%20and%20Solr%20Messages&target=alias(sumSeries(*_celery_nv-d.42)%2C%22Celery%22)&target=alias(secondYAxis(sumSeries(*_solr_nv-d.42))%2C%22Solr%22)&vtitle=Messages&vtitleRight=Messages

However if I load this graph in a new browser tab, in the Composer, neither the title nor the right title/label show.

I don't know if this is the same for everyone, but this only seems to affect loading the graph in the Composer. If I add it to a dashboard, it displays fine, title/label and all. Seems like something in the code that's loading saved graphs in Composer.

Revision history for this message
Carl (cmercier) wrote :

+1

Revision history for this message
Jeff Fishbaugh (email-fish) wrote :

I am hitting this bug as well. I confirmed any custom setting saved to a graph (title, transform, etc.) does not display when you load your saved graph up in composer. It does however display saved values properly if you call a saved graph to display on a dashboard.

I agree with some of the previous comments, it looks like this issue has something to do with how composer is pulling the values of titles, transforms, and the like when added and saved to a saved graph. It's evidently getting into the db properly if the dashboard is able to pull up the same saved graph and display the title and other things like transforms. Just composer seems not to be able to do the same.

I am on the following:

Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise

- carbon-0.9.10.tar.gz
- graphite-web-0.9.10.tar.gz
- whisper-0.9.10.tar.gz

Thanks for the great code! Hoping there is a fix soon.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.