Skip to content
This repository has been archived by the owner on Dec 27, 2022. It is now read-only.

Validation on Graphite Datasource Can Fail on Composite Queries #78

Open
Mmmkayness opened this issue Jan 24, 2014 · 0 comments
Open

Validation on Graphite Datasource Can Fail on Composite Queries #78

Mmmkayness opened this issue Jan 24, 2014 · 0 comments

Comments

@Mmmkayness
Copy link

Hi, the commit 2 months ago (fdc6d17) to address the alignment problem when Graphite fails to find values for the requested metric has an undesirable side effect when composite functions are chained together in a query for a metric (like for example a sumSeries on 2 metrics):

Graphite does not necessarily return the parameters requested in the same order in the JSON returned and so the underscorejs find function can fail (I presume Graphite does some kind of sorting). Graphite also seems to like injecting space characters inconsistently too:

/render/?target=sumSeries(api.foo.rate,api.bar.rate)

JSON:
[
{
target: "sumSeries(api.bar.rate,api.foo.rate)"
.... etc
}
]

A temporary workaround I'm implementing at the moment is to adjust my dashboard config to use the ordering that's sent back from Graphite, but it's something worth considering, or flagging as a gotcha when working with Graphite.

Adam

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant