So, trying to mimic some really expressive behavior that grafana uses. They allow you to track metrics with keys like: a.b.c.d.e and you can do analytics/querying based on searches of a.b.*.d.e. Note, using dots instead of slashes wouldn't change how this is implemented.
A real world scenario around this:
myapp.*.logins
where the convention used is myapp.version.logins.
That query (services.com/myapp.*.logins?all=true) allows you to get all login event metrics across all versions/deploys and can compare. A/B testing and a lot of things would be enabled by this.
I'd imagine we would just pass the raw string to the db adaptor and let them figure out how to parse/support it. For the file-db adaptor, should be a simple change of the filter to use a regex. Something along the lines of key.match(new RegExp('^' + options.pathname.replace('*','.*')))
So, trying to mimic some really expressive behavior that grafana uses. They allow you to track metrics with keys like:
a.b.c.d.eand you can do analytics/querying based on searches ofa.b.*.d.e. Note, using dots instead of slashes wouldn't change how this is implemented.A real world scenario around this:
myapp.*.loginswhere the convention used is
myapp.version.logins.That query (
services.com/myapp.*.logins?all=true) allows you to get all login event metrics across all versions/deploys and can compare. A/B testing and a lot of things would be enabled by this.I'd imagine we would just pass the raw string to the db adaptor and let them figure out how to parse/support it. For the file-db adaptor, should be a simple change of the filter to use a regex. Something along the lines of
key.match(new RegExp('^' + options.pathname.replace('*','.*')))