URL for a complete Graphite Composer experience

replace /render with /composer in the url.

On Wed, Jun 27, 2012 at 6:26 PM, Steve Keller <
<email address hidden>> wrote:

> New question #201667 on Graphite:
> https://answers.launchpad.net/graphite/+question/201667
>
> We use the URL API a lot, for some custom dashboards and occasionally
> ad-hoc, but we have a request to link a rendered image to the Graphite UI
> in case an executive wants to drill down and do other things. Basically,
> we want to be able to go from a rendered image to the same graph in the
> Composer interface.
>
> Is this possible? Even after poring over the API and tailing the access
> log, I can't figure out how...
>
> --
> You received this question notification because you are a member of
> graphite-dev, which is an answer contact for Graphite.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~graphite-dev
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~graphite-dev
> More help : https://help.launchpad.net/ListHelp
>

Also:

http://obfuscurity.com/2012/04/Unhelpful-Graphite-Tip-2

Thanks David.

This works - kind of... If I use a single metric target or multiple targets, it will work. If I use a target with a wildcard (which we do a lot) ... I get the No Data screen.

I THINK this might be related to the composer not being able to digest wildcards anymore. In 0.9.6, I can go into the data window, and change one of the areas of a single metric to a '*' to pick up a bunch of hosts with similar names. Since 0.9.9, this doesn't work.

Jason, I just spent 20 minutes browsing your Unhelpful Graphite Tips. Actually, they are really helpful :) And a couple of them I already knew, specifically Nos. 7 and 10.

Thanks, I'm not sure how I would deal with this tip in this context, but I'll play around with it. I'm not a Javascript person, so I'm not sure how I could get that stuff into a link in a totally different page. But I know people who are .... :)

Thanks to you both, I'm sure we'll get there. Maybe I should file a bug about the composer wildcard issue.

I think this is related to a problem treating the query string in JS - I've opened an issue with what I think is the problem.
https://github.com/graphite-project/graphite-web/issues/362
Fixing the composer.js to not replace one % character should make it work with any kinds of targets

I'm sorry I've just seen that this bug has alreayd been fixed in https://github.com/graphite-project/graphite-web/commit/0c2b2670ec41c85d63b275e47e221894c3aca8b6, so this should already be working.