-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Add ability to map string fields to numeric fields #2791
Comments
Just for references: And just for clarification, I'm not saying this request should be closed, just throwing out some related stuff. |
Thanks. That info will be really handy as a "stop gap". 👍 |
I think it is best to implement this with some enhancements to the #2667 proposal. I'll write a follow up over there. |
Changing my mind on this, I guess it doesn't make sense to have a general purpose transform plugin so we would want a "enum" or "case" processor for this. Here is my first idea for how to configure the processor. I don't love it, so hopefully we can improve on the idea. [[processors.enum]]
namepass = ["elasticsearch"]
[[processors.enum.fields]]
key = "health"
[processors.enum.table]
green = 0
yellow = 1
red = 2 |
Kind of a crazy ass idea, but what about embedding kapacitor in telegraf? We wouldn't put the whole thing in, just the stream processing engine. Or, to go batshit insane, what if telegraf were gone, and the input plugins were kapacitor input plugins. Yes kapacitor would need to be modified to make the management easier. But just throwing at the wall to see what sticks. There's quite a bit of overlap between kapacitor and telegraf. |
I'd love to do it but I guess it's a fair amount of work. |
This is also fixed! :) |
Closed in #3772 |
Feature Request
Proposal:
Introduce a numeric "cluster_health" or "cluster_status" value
Current behavior:
Current implementation has a status field which is a text object, having values "green", "yellow" or "red".
Desired behavior:
Add a numeric representation of this field, called cluster_health, cluster_status or just health. I suggest a simple mapping of 0, 1 and 2 for green,yellow and red.
Use case: [Why is this important (helps with prioritizing requests)]
The "SignalFX" plugin for CollectD already has this behaviour. Having a numeric field permits Grafana presentation of state with time, so showing when a cluster went into a degraded or failed state. This can be very useful in tracking down root cause. Current text-based representation has to be converted to a number in order to do this, which is cumbersome.
Alerting rules are also simplified, since != 0 means intervention is needed
The text was updated successfully, but these errors were encountered: