Search This Blog

Kubernetes health monitoring

Health Monitoring





  • Instance of application is working or not, if not working other services should not access. Route request to other instance
  • try bring system back in the healthy state (feedback loop)
    • Readiness prob   
      • when application is ready t0 accept request
    • Liveness prob   
      • Application is serving request or not
    • Startup Prob   
      • Application started or not
  • Monitor different resources like AKS, Web app etc. and drill down tline of code. It works by means of data collection of Metrics & Logs (raw telemetry ) from Application | OS | Azure Resources | Custom Resources
  • HTTP Prob       
  • Command Prob       
  • TCP Prob       
  • Monitor           
    • Web App       
    • AKS       
    • Redis Cache       
    • Logic App       
    • Event hub       
  • Workflow:           
    • Collect Data from on-prim resources, azure Resources, third party resources, Insight, Logs.io, Application, Container, VM
  • Metrics Explorer
    • Log Analysis   
    • Respond       
    • Alerts   
    • Auto-scale   
    • Integrate       
      • Event Hubs   
    • Ingest & Expos APIs
  • Health Condition Definition
    • Critical
    • Warning
    • Healthy
    • Unknown       
  • Health Criteria           
    • Resource Availability (It depends on type of resource)      
    • Storage Space
    • CPU   
    • Queue capacity
    • Composite   
    • Concurrent Request
    • Response time
    • Counters       
      • CPU Time
      • Memory Utilization
      • Restart   
      • MicrCore
      • Number of concurrent request
      • Request execution time
      • Log Analytics
      • Map       
      • How many VM
      • Open ports
      • Processes
  • CD Integration       
  • Scaling Integration