Repository navigation
Add Kubernetes noisy neighbor with ES|QL and SLOs notebook - #603
Merged
jarturomora merged 2 commits intoOct 5, 2026
Merged
jarturomora merged 2 commits into
jarturomora merged 2 commits into
Conversation
|
Found 1 changed notebook. Review the changes at https://app.gitnotebooks.com/elastic/elastic-labs/pull/603 |
jarturomora
approved these changes
Oct 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Companion notebook for the Observability Labs article "Finding and fixing a noisy-neighbor problem in a multi-tenant Kubernetes cluster" (elastic/elastic-labs-blogs#2211).
It checks that the tenant labels reach the kubelet metrics, confirms the storefront's latency symptom, ranks the tenants on the shared worker with ES|QL
TS, traces the top consumer to its Deployment, verifies the fix with the same queries, and creates a histogram-metric SLO through the Kibana API. The last cell deletes the SLO.The scenario runs on a two-node kind cluster from
k8s/: the EDOT kube-stack Helm override that copies the tenant labels onto the metrics, the storefront and batch tenants, a k6 probe, the ResourceQuota, andlab.shfor the baseline, contention and fix phases. Requires Elasticsearch and Kibana 9.4+ on Elastic Cloud Hosted, Docker, kind, kubectl, Helm and k6 1.0+. Includes.env.example,k8s/lab.env.exampleand the Kubernetes manifests undersupporting-blog-content/observability-labs/kubernetes-noisy-neighbor-esql-slo/.