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
However, using the tag format for dimensions would be more appropriate in many applications:
my_event:123.45|ms#foo:bar
Unfortunately, there's not a standard syntax for tags (see statsd/statsd#619), but I think this could be addressed by having an optional init parameter to specify the format:
enumDimensionFormat{case datadog
case influxdb
case inline
// ..}classStatsdClient:MetricsFactory{publicinit(eventLoopGroupProvider:EventLoopGroupProvider=.createNew, host:String, port:Int, format:DimensionFormat=.inline)throws{// ...}// ...}// User initialization codeletstatsdClient=tryStatsdClient(host: statsdHost, port: statsdPort, format:.datadog)MetricsSystem.bootstrap(statsdClient)
It may be preferable to avoid specific vendor names in the enum cases to avoid any sort of endorsement, but I'm confident that could be addressed.
Thoughts?
The text was updated successfully, but these errors were encountered:
At present, the use of metrics dimensions results in some metrics being emitted in an unexpected way:
will emit a packet roughly like
However, using the tag format for dimensions would be more appropriate in many applications:
Unfortunately, there's not a standard syntax for tags (see statsd/statsd#619), but I think this could be addressed by having an optional init parameter to specify the format:
It may be preferable to avoid specific vendor names in the enum cases to avoid any sort of endorsement, but I'm confident that could be addressed.
Thoughts?
The text was updated successfully, but these errors were encountered: