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

Regex support in elasticsearch metrics alias pattern #5212

Closed
soltiz opened this issue May 30, 2016 · 24 comments · Fixed by #29281
Closed

Regex support in elasticsearch metrics alias pattern #5212

soltiz opened this issue May 30, 2016 · 24 comments · Fixed by #29281

Comments

@soltiz
Copy link

soltiz commented May 30, 2016

Metrics field are often longer than wished in a legend.
Example: topbeat ==> "cpu.idle", "cpu.system", "cpu.user", "cpu.nice"

a regex in alias pattern (like {{regex /cpu.(.*)/}} ) would allow more readible series names (here, only "idle", "user", "system"). This is especially powerful if we can chain it with {{term fieldname}} so as to transform terms values !!!

@bergquist bergquist added type/feature-request prio/low It's a good idea, but not scheduled for any release labels May 30, 2016
@charlescva
Copy link

Same. I have lookup values in my index. e.g. 1, 2 ,3. While I could create a new index, I think I would like to be able to Regex them. 1/httpd, 2/jboss, 3/auditd

@boernd
Copy link

boernd commented Jul 27, 2016

+1

4 similar comments
@dachenbach
Copy link

+1

@lukanus
Copy link

lukanus commented Mar 23, 2017

+1

@tijlk
Copy link

tijlk commented Apr 11, 2017

+1

@amper43
Copy link

amper43 commented Jun 7, 2017

+1

@GedPL
Copy link

GedPL commented Feb 8, 2018

+1
and maybe also allow to set Alias manually for each metric

@gekr
Copy link

gekr commented Feb 22, 2018

+1

3 similar comments
@MrSantamaria
Copy link

+1

@Dr-kyle
Copy link

Dr-kyle commented Aug 16, 2018

+1

@zhiyp
Copy link

zhiyp commented Aug 27, 2018

+1

@holiiveira
Copy link
Contributor

Is anyone working on this feature?
I'm interested in helping where needed.

@marefr marefr changed the title [Feature Request] Regex support in elasticsearch metrics alias pattern Regex support in elasticsearch metrics alias pattern Dec 11, 2018
@marefr
Copy link
Member

marefr commented Dec 11, 2018

@holiiveira you're welcome to contribute. No one else in working on this as far as I know. Please note that it's no guarantee that we'll accept your PR and/or it may take some time depending on how we see this feature fit. Right now there are no other core datasource having this feature so maybe this feature would be better to solve in a more generic way. However, how this generic way looks we don't know right now.

If you want to open a PR you'll need to solve it both client and server side to support alerting.

@pathikmehta
Copy link

+1

@Colear
Copy link

Colear commented Jan 28, 2019

+1
It's a feature that I miss a lot. For exemple, with the module jolokia from metricbeat, when using generic terms, I could have fields like "kafka.server:name=MessagesInPerSec,topic=gap,type=BrokerTopicMetricskafka.". In this case, the only discriminating thing I would like to see in legend is the name of the topic ("gap" here).

@RubenDiaz
Copy link

+1

@davtex
Copy link

davtex commented Mar 13, 2019

+1

I have two ES queries, both are simple "Count" metrics, unfortunately both of their names is "Count". I believe this prevents Grafana from displaying these next to each other (they are grouped by the same "group by") - this is not an issue with InfluxDB at all since aliasBy is available. This also prevents me from using Meta Queries plugin.

@alessandro-lac
Copy link

+1

1 similar comment
@magaton
Copy link

magaton commented Jun 5, 2019

+1

@smurfix
Copy link

smurfix commented Sep 23, 2019

Same here. Use case: My host names are stored as-is as tags in the time series databases, and I need to have a generic way to drop the domain part. :-/

@vmitris
Copy link

vmitris commented Jan 20, 2020

+++1

@danielmotaleite
Copy link

This is most useful in elasticsearch, but sadly, after 4 years, still no way to do this.
While a generic way to do this in all data sources is awesome, trying to aim just for that may be harder and block this features for several years. It is better to add this just to elasticsearch and then expand or rewrite if it is found a better way

@sujay1109
Copy link

+1

1 similar comment
@Daphneitec
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging a pull request may close this issue.