Justin Garrison

Google is going all in on progressive web apps and currently working on native container support on ChromeOS. I wouldn’t be surprised if by the end of the year it’d be dumb to NOT have a Chromebook. Especially if Apple can’t stabilize macOS and keeps adding unwanted features to their laptops.

Thanks for the write up and information. Do you plan on pushing these code changes upstream to the prometheus node_exporter project or will you carry the patches yourself?

Thanks for pointing that out. I updated the title so it only applies to k8s < 1.6

I would much rather my systems be down than up and unhealthy. Being down is clear and easier to fix. Unhealthy requires a lot more knowledge about the system and what “healthy” means.

Sorry about that. Traefik re-organized their repo. I updated the link to their new example file.

You can get all child processes with ppid option. Something like this should work

ps h -o pid --ppid 1 | xargs strace

This would obviously require xargs in your support container but that shouldn’t be an issue.

You have to do it manually right now buy finding the node the container is running on an then ssh to the host and follow the same steps. I’m not sure if kubernetes will add similar features but you still have access to the containers on the nodes.

Just thought I’d pass this along that maybe it’ll be helpful working with ingress. https://medium.com/@rothgar/exposing-services-using-ingress-with-on-prem-kubernetes-clusters-f413d87b6d34#.mlacwjm45

You’ve probably already found a solution but I thought I’d share.

I have used sysdig since ~2013. It’s a great tool but it only allows for passive monitoring (can’t send command to running process) and if you want to use tracers you have to have the source code of the application running in a container.

A great option for monitoring and finding root cause for outages but not an option for…

Correct but I didn’t want to make assumptions about someone’s cluster and I wanted to show how you can find the node a pod is running on.