This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
What is your recommendation for monitoring memory usage for kubernetes pods/containers?
So far we are using this in Instana: Kubernetes -> Container -> Memory Usage. (Prefer this as compared to pods because sidecars can get in the way)
The problem is, because Instana is also using cache memory in it’s calculations, in some cases it makes the monitoring useless, basically any caching deployment would reach 90+ % in a matter of weeks, and this normal Kubernetes/Linux behaviour. Here’s a fun description: Help! Linux ate my RAM!
I think Instana should monitor the same metrics that are followed by the oom kill mechanism in K8S/Linux.
Idea priority | Urgent |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Hi @Guest ! Following up here, if you're available for a call to discuss K8s monitoring in more detail.
Hi @Guest ! I'd like to get on a call to talk more about the first thing - around K8s monitoring needing to be more comprehensive. If you're open to a brief call, could you provide some availabilities? Also, let me know what timezone you're in.
My answers:
Yes, it's still relevant. AFAIK I'm not alone on this matter, many colleagues told me the Instana's K8s monitoring needs to be more comprehensive on the infrastructure side.
Yes, we want to get info of the cache usage always. Additionally, include one or more default rules for cache utilization.
Hi @Guest ! Nice to e-meet you. I'm Jayanth, the PM for Kubernetes at Instana and I'm looking into your idea here.
I wanted to follow-up here with a couple questions:
Given this was filed almost 2 years ago, is this still relevant for your use case?
In an ideal scenario, would you never want to see memory usage which includes cache? Or would you prefer that there's a toggle of some sort? If you would like an option, what would be your use case around being able to switch between both views?