Health Checks and Validation
This section provides step-by-step instructions to assess and monitor the health and proper function of ESET Static Scanning Engine deployments on EKS and ECS.
EKS Health Check
1.Pod and Service Status
# Check pod status (must show "Running") kubectl get pods -n $K8S_NAMESPACE
# Verify service endpoints are available kubectl get svc -n $K8S_NAMESPACE |
2.Application Logs
# Monitor scanner logs for license validation, metering, and scanning activity kubectl logs deployment/scanner -n $K8S_NAMESPACE --follow
# Check specific pod if multiple replicas kubectl logs -l app=scanner -n $K8S_NAMESPACE --follow |
3.Resource Utilization
# Monitor CPU/memory usage kubectl top pods -n $K8S_NAMESPACE
# Detailed resource metrics kubectl describe pod <scanner-pod-name> -n $K8S_NAMESPACE |
ECS Health Check
1.Service and Task Status
# Verify service is stable with desired tasks running aws ecs describe-services --cluster $EKS_CLUSTER_NAME --services scanner
# Check individual task health aws ecs describe-tasks --cluster $EKS_CLUSTER_NAME --tasks <task-id> |
3.Application Logs
# Tail scanner logs in real-time aws logs tail /ecs/scanner --region $AWS_REGION --follow |
3.CloudWatch Metrics
# CPU/Memory utilization for service aws cloudwatch get-metric-statistics \ --namespace AWS/ECS \ --metric-name CPUUtilization \ --dimensions Name=ClusterName,Value=ecs-demo Name=ServiceName,Value=scanner \ --start-time $(date -u -d '1 hour ago' +%FT%TZ) \ --end-time $(date -u +%FT%TZ) \ --period 300 \ --statistics Average |
Health Indicators Checklist
Component |
Healthy Status |
Command |
|---|---|---|
EKS Pods |
Running / Ready |
kubectl get pods -n $K8S_NAMESPACE |
ECS Tasks |
RUNNNING |
aws ecs describe-tasks |
Services |
1/1 replicas |
kubectl get deploy / aws ecs describe-services |
gRPC |
Responds to health check |
grpcurl scanner:50051 |
Logs |
License validated, no metering errors |
kubectl logs / aws logs tail |
Resources |
<80% CPU/Memory |
kubectl top / CloudWatch |