You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 18, 2023. It is now read-only.
I'm considering to contribute filtering capability backed into the configuration flow.
The idea behind it is to enable better control over the metrics you sending over the wire at runtime.
You may want limited amount of metrics that will give general health indication,
but when you got indication that something may went wrong,
you may want to illuminate specific spot by open other metrics.
In terms of Api I'm considering something similar to Serilog's filtering.
My suggestion is:
Thanks for the heads-up, Bnaya. This isn't a feature I've personally been looking for, but I can't speak for everyone else - will keep this here so we can collect feedback. Cheers!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm considering to contribute filtering capability backed into the configuration flow.
The idea behind it is to enable better control over the metrics you sending over the wire at runtime.
You may want limited amount of metrics that will give general health indication,
but when you got indication that something may went wrong,
you may want to illuminate specific spot by open other metrics.
In terms of Api I'm considering something similar to Serilog's filtering.
My suggestion is:
Metrics.Collector = new CollectorConfiguration()
.Filter.Tags.Match(tags => tags.ContainsKey("host") && tags["host"] == "BnayaMac")
.Tags.Exists.All(() => new[] { "Dev", "Staging" })
.Tags.Exists.Any(() => new[] { "OperationA", "OperationB" })
.Fields.Match(fileds => fileds.ContainsKey("cpu") && fileds["cpu"] > 80)
What do you think about the Api?
The text was updated successfully, but these errors were encountered: