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
Comments
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 |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
3 similar comments
+1 |
+1 |
+1 |
Is anyone working on this feature? |
@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. |
+1 |
+1 |
+1 |
+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. |
+1 |
1 similar comment
+1 |
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. :-/ |
+++1 |
This is most useful in elasticsearch, but sadly, after 4 years, still no way to do this. |
+1 |
1 similar comment
+1 |
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 !!!
The text was updated successfully, but these errors were encountered: