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
Is your feature request related to a problem? Please describe.
Make it possible to add fire count a global item. Essentially allow a fire count of 1 mean that 1 trace point will fire even if there are more than 1 client connected.
Describe the solution you'd like
This would need Deep to track fire counts of the tracepoints as the snapshots arrive, then disable the tracepoints in the service once they have exceeded the count.
Considerations:
Scale of the control - how would a deep cluster of 10-20-1000 nodes handle this?
How could we track the fire count (as a metric)? - maybe look at the global rate limit control for ingest.
How would we re arm these disabled tracepoints?
How would a local deep-agent/collector handle these?
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Make it possible to add fire count a global item. Essentially allow a fire count of 1 mean that 1 trace point will fire even if there are more than 1 client connected.
Describe the solution you'd like
This would need Deep to track fire counts of the tracepoints as the snapshots arrive, then disable the tracepoints in the service once they have exceeded the count.
Considerations:
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: