Monitor Linux machines with node-exporter on Kubernetes

Subscribe to show your support! goo.gl/1Ty1Q2 .
Patreon 👉🏽 / marceldempers
Today we're going to explore the Prometheus node-exporter.
Node Exporter is one of my most favorite observability tools on Linux used in Prometheus monitoring. It surfaces up hundreds of valuable upstream Linux metrics which are available in /proc
This will help you find bottlenecks in your server's ability to perform.
Remember to like, subscribe and checkout the source code below:
Source Code
github.com/marcel-dempers/doc...
Also if you want to support the channel further, become a member 😎
marceldempers.dev/join
Checkout "That DevOps Community" too
marceldempers.dev/community
If you need to know more about managing Prometheus instances, checkout my operator video:
• Introduction to the Pr...
Also, if you're new to Kubernetes, checkout my guides below:
Check out part 1 for how to install Kubernetes on Windows:
• Kubernetes Getting Sta...
Check out part 2 of how to use KUBECTL:
• Kubectl basics for beg...
Check out part 3 of how to do deployments
• Kubernetes Deployments...
Check out part 4 of how to manage application configurations
• Configuration manageme...
Check out part 5 of secret management explained
• Kubernetes Secret Mana...
Like and Subscribe for more :)
Follow me on socials!
Patreon | / marceldempers
Twitter | / marceldempers
GitHub | github.com/marcel-dempers
Facebook | thatdevopsguy
LinkedIn | / marceldempers
Instagram | / thatdevopsguy
Music:
Track: MESIØ - Clario Bubblegum
Listen: / clario-bubblegum-mesio...
Track: MNDBD - "TYPE BEAT" TYPE BEAT (FT. TGWOG & FEEP) | is licensed under a Creative Commons Attribution licence (creativecommons.org/licenses/...)
Listen: / type-beat-type-beat-ft...
Track: HERTHA - ROLLING
Listen: / g59
Track: souKo - souKo - Parallel | is licensed under a Creative Commons Attribution licence (creativecommons.org/licenses/...)
Listen: / parallel

[@leo5946]

you are really chnging the learniing experience for us with your blog type tutorials, great job, big fan

[@romannikolaevich5281]

Your vlog is excellent! Thank you so much!

[@salborough2]

Such a great video - thanks Marcel :)

[@RayanSlim087]

Fantastic Demo!

[@AlexStuffss]

For someone like me who's just getting started with Docker and Kubernetes, this is fantastic. Really appreciate your videos!

[@kellenlincoln2052]

You prolly dont care but does any of you know of a trick to get back into an Instagram account? I somehow lost the account password. I would love any tips you can offer me

[@justinjesse6417]

@Kellen Lincoln instablaster ;)

[@whyismychannelhandletaken]

Another excellent video! Keep up the good work!

[@whyismychannelhandletaken]

Alermanager 101 would be useful as well :)

[@MarcelDempers]

@@whyismychannelhandletaken Great idea 👍

[@m19mesoto]

Thank you for your nice work, can you showcase how to monitor redis or rabbit that are running in side the kube cluster?

[@jairams]

HI, your videos are excellent. The only thing to change I think is that your codebase has changed. For example, you dont have the prometheus-monitoring folder under the root structure.

[@user-rq4bu3jz8x]

Thanks, could you give some ideas how to monitor socket queue in k8s with help of prometheus?

[@rajeshn8681]

Nice and clear explanation. Keep doing the good work. How about monitoring mongodb in kubernetes using these tools. Do you have in your git resources already or planning any time in future ??

[@MarcelDempers]

Thank you! Nothing in the pipeline for mongoDB specifically. However, all service monitor concepts in my kubernetes monitoring series will work for mongoDB. You will want to add an exporter to it and use service monitors to scrape and pull metrics github.com/percona/mongodb_exporter

[@georgelza]

just curious, if we deploy onto a multi node K8S environment... thinking we want a persistent volume on the cluster where Prometheus stores it's configuration and metric data, so that if the pod moves around to another node or we have a restart it can still get to it's data folder ? did you by any chance do a follow up of this video covering that ? which files/values needs to be modified to accommodate this ?

[@ka11ki]

I love your videos. I an a newbie in DevOps and have a basic question. Lets say the infrastructure is very simple and as an example have 2 Ec2 instance son AWS. Is it possible to NOT have Prometheus installed on another remote machine outside of the infrastructure which it needs to monitor. Only node_exporter will be installed on the 2 instances in the infrastructure. is this possible?

[@MarcelDempers]

Thanks for the kind words :) You will need prometheus somewhere (local on machine or same network or remote network) to scrape the metrics from node exporter. Prometheus is the time series database that stores and aggregates metrics for consumption by UI tools like Grafana

[@zukerberg007]

Hi I am stuck up in this scenario please help . Scenario - with EKS created a master cluster and 2 slave machines . deployed a basic application. Now I want to expose the port of the application to external . could you please let me know how to use node exporter in this scenario. Also , please note , my local machine is Win10 and I create ec2 machine from aws console and proceeded with above scenario.

[@RavindraRaivlogs]

Where you configured node_expoter in promtheus.yml file with port 9100..... without configured how can you received metrics... please reply

[@rajualapati8742]

Can you please help me with how to do it on multiple AWS accounts without VPC peering? I need to get metrics from private IP subnets using any exporter and IAM role ... Please help

[@ctrlz4439]

I am puzzled that you are attempting to monitor linux machine , by running node_exporter in isolated container where it does not have full access to machines resources due cgroups, does not have access to physical machine filesystems and network as well. What kind of data it is monitoring ?

[@MarcelDempers]

Node exporter mounts host proc which gives access to every metric on the kernel for every process on the system regardless of container or not. From cpu, memory, file system to tcp and everything else tldp.org/LDP/Linux-Filesystem-Hierarchy/html/proc.html

[@lamle5183]

To add to Marcel's answer: Have a look at timestamp 8:40 as well. Indeed, containers are isolated. If we attempt to run node exporters in containers, we surely monitor the container. But what happens is we mount the metrics from the worker nodes to the node exporter containers via volume mounts. These are not really isolated now. Metrics are shared and node exporters will pick up the metrics from the same folders, but now, they are from the machines hosting them!