Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gmetad: Add wildcard support to gmetad http query interface. #64

Merged
merged 1 commit into from Oct 26, 2012
Merged

gmetad: Add wildcard support to gmetad http query interface. #64

merged 1 commit into from Oct 26, 2012

Conversation

miherran
Copy link
Contributor

The word "any" is treated as a wildcard. A query for "/any/any/metric_name" would include all metrics named "metric_name" from all hosts. This change does not affect the non-http query interface.

@jbuchbinder
Copy link
Member

It would probably make more sense to use something like '' to denote a wildcard, since "any" could easily exist as a substring in a host or cluster name. Could you amend the patch to use a '' wildcard before we merge it?

@miherran
Copy link
Contributor Author

Sure, I'll do that.

The character '*' is treated as a wildcard. A query for "/*/*/metric_name"
would include all metrics named "metric_name" from all hosts. This change
does not affect the non-http query interface.
@miherran
Copy link
Contributor Author

Updated.

jbuchbinder added a commit that referenced this pull request Oct 26, 2012
gmetad: Add wildcard support to gmetad http query interface.
@jbuchbinder jbuchbinder merged commit f982643 into ganglia:master Oct 26, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants