graphite-dev team mailing list archive

Thread
Date

[Question #179136]: Completer should be able to search "better"

To: graphite-dev@xxxxxxxxxxxxxxxxxxx
From: Pierre Baillet <question179136@xxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 17 Nov 2011 18:05:46 -0000
Reply-to: question179136@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

New question #179136 on Graphite:
https://answers.launchpad.net/graphite/+question/179136

Hi,

While I perfectly understand the .\*. syntax we generally use to generate aggregated graphs (and .*. for searches), I'd like to know if you plan to implement something that's more agile in term of search:

- Typing "*memory*" would bring up all the metrics matching memory ( such as servers.net.ftnz.virtual.infrabox.system.memory.*  for example)
- Typing *.*_hits.* would bring up servers.net.ftnz.virtual.infrabox.Picor.picor_hits.*

This would definitely prove useful for systems where there are lots of metrics and nested paths for them.

Thanks for Graphite !
-- 
Pierre.

You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.