By using AWS re:Post, you agree to the Terms of Use
/Monitoring & Logging/

Questions tagged with Monitoring & Logging

Sort by most recent
  • 1
  • 90 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Health check at NLB level for a Fargate Service

I have a service using ECS Fargate behind an NLB, which runs my application at port 8443. The NLB target group health check shows the following settings (default for TCP health check). ``` Protocol TCP Port. Traffic port Healthy threshold 3 consecutive health check successes Unhealthy threshold 3 consecutive health check failures Timeout. 10 seconds Interval 30 seconds ``` The NLB target group also has the default target deregistration time of 60 seconds. With this, I wanted to understand the difference between the active health check and the passive health check done by the NLB for its targets. My understanding is that the above health check configuration is for the active health check. Would there also be a default passive health check in an NLB which responds to failed responses from the target? Further, i can see that the moment i stop my Fargate task, even in the absence of any traffic, the target(ECS IP) begins deregistration. There seems to be no 30 second time gap (active health check interval as above). The metric (healthy host as 1) stops getting published. Is this thus somehow configured in the NLB to get notified about terminating Fargate tasks? Finally, I wanted to understand how good is the NLB healthy task count metric to monitor my Fargate application. I was thinking that it is the best metric since it does a TCP ping at the port level (8443 port in my case) thus ensuring that the monitoring is done at the port (application) level as well as the task level.
1
answers
0
votes
29
views
asked 19 days ago

CloudWatch Cutome metrics does not created

Hi, Based on [this](https://aws.amazon.com/blogs/containers/autoscaling-amazon-ecs-services-based-on-custom-cloudwatch-and-prometheus-metrics/) session I tried to report new metrics using cloudwatch-agent (docker image) and Prometheus in order to set up autoscaling. Well, things seem to work fine but no new matrics are added to cloud watch. Prometheus cloudwatch logs present logs my custom metric: Log Group: /.../ecs/containerinsights/../prometheus Example Log: { "ClusterName": "XXXX-Cluster-uM8Ibru82elP", "LaunchType": "FARGATE", "StartedBy": "ecs-svc/XXXX", "TaskDefinitionFamily": "XXXX", "TaskGroup": "service:XXXX", "TaskRevision": "87", "Timestamp": "1642512851574", "Version": "0", "container_name": "XXXX", "exported_job": "LBL1", "instance": "10.0.1.225:3005", "job": "labrain-ecs-mri", "labrain_mri_counter_total": 0, "prom_metric_type": "counter" } I notice that other insights logs, within different Log Group, has Metric section: {...... "CloudWatchMetrics": [ { "Namespace": "ECS/ContainerInsights", "Metrics": [ { "Name": "DesiredTaskCount", "Unit": "Count" }, { "Name": "RunningTaskCount", "Unit": "Count" }, { "Name": "PendingTaskCount", "Unit": "Count" }, { "Name": "DeploymentCount", "Unit": "Count" }, { "Name": "TaskSetCount", "Unit": "Count" } ], "Dimensions": [ [ "ServiceName", "ClusterName" ] ] } ] } I wonder if that is what is missing from my log and if so what did I miss? Thanks in advance.
0
answers
0
votes
14
views
asked 5 months ago
  • 1
  • 90 / page