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
The networking overview dashboards renders the number of inflight request for the mimir gateway
mimir/operations/mimir-mixin/dashboards/overview-networking.libsonnet
Line 9 in 1e903e4
cortex_inflight_requests
cortex_tcp_connections
cortex_tcp_connections_limit
Should those panels be removed for the gateway in the case that it uses nginx?
On that note, the rollout dashboard should probably be removable from the mixins as it's main use case it for the enterprise gateway
Steps to reproduce the behavior:
A clear and concise description of what you expected to happen.
The text was updated successfully, but these errors were encountered:
yeah i think it makes sense to remove those panels by default in the rendered dashboards. They are removed via $._config.gateway_enabled. I believe this is the config that's used for the config default dashboards https://github.com/grafana/mimir/blob/9090af52a8e104c37bb4da975bbefbf5185458cc/operations/mimir-mixin/mixin-compiled.libsonnet setting gateway_enabled: false in that file should do the job.
$._config.gateway_enabled
gateway_enabled: false
Sorry, something went wrong.
Hi @dimitarvdimitrov , I would like to work on this.
parambath92
No branches or pull requests
Describe the bug
The networking overview dashboards renders the number of inflight request for the mimir gateway
mimir/operations/mimir-mixin/dashboards/overview-networking.libsonnet
Line 9 in 1e903e4
cortex_inflight_requests
cortex_tcp_connections
andcortex_tcp_connections_limit
Should those panels be removed for the gateway in the case that it uses nginx?
On that note, the rollout dashboard should probably be removable from the mixins as it's main use case it for the enterprise gateway
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Environment
Additional Context
The text was updated successfully, but these errors were encountered: