We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
per-rule tracing and metrics data could be quite useful for tracking down slow pipelines on a per request basis
As the title says, instrument the pipeline mechanisms to allow related insights and analysis
Indirect analysis is possible in a limited way by substracting the time measured for outbound connections opened by a particular mechanism.
v0.11.1-alpha
Discussed in Discord: https://discord.com/channels/1100447190796742698/1146494243985166376/1146494243985166376
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Preflight checklist
Describe the background of your feature request
per-rule tracing and metrics data could be quite useful for tracking down slow pipelines on a per request basis
Describe your idea
As the title says, instrument the pipeline mechanisms to allow related insights and analysis
Are there any workarounds or alternatives?
Indirect analysis is possible in a limited way by substracting the time measured for outbound connections opened by a particular mechanism.
Version
v0.11.1-alpha
Additional Context
Discussed in Discord: https://discord.com/channels/1100447190796742698/1146494243985166376/1146494243985166376
The text was updated successfully, but these errors were encountered: