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
When deploying the Hono chart with a tracing backend, currently the Hono components send all traces to the tracing collector by default.
In order to limit the number of traces sent by the components, Hono has different sampler configuration options: https://www.eclipse.org/hono/docs/admin-guide/monitoring-tracing-config/#tracing
Setting these options for the Hono Helm chart deployment currently requires using the envConfigMap property along with a confg map containing corresponding environment variables. (Another option would be using an extra config file referenced via quarkusConfigLocations.)
It would be helpful to provide a more straightforward chart configuration option for configuring the sampler here.
The text was updated successfully, but these errors were encountered:
When deploying the Hono chart with a tracing backend, currently the Hono components send all traces to the tracing collector by default.
In order to limit the number of traces sent by the components, Hono has different sampler configuration options:
https://www.eclipse.org/hono/docs/admin-guide/monitoring-tracing-config/#tracing
Setting these options for the Hono Helm chart deployment currently requires using the
envConfigMap
property along with a confg map containing corresponding environment variables. (Another option would be using an extra config file referenced viaquarkusConfigLocations
.)It would be helpful to provide a more straightforward chart configuration option for configuring the sampler here.
The text was updated successfully, but these errors were encountered: