You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a deployed vector container, I can observe environments ECS_CONTAINER_METADATA_URI=http://169.254.170.2/v3/f4275bb6-2577-45f4-8500-49c6f5fa28ad ECS_CONTAINER_METADATA_URI_V4=http://169.254.170.2/v4/f4275bb6-2577-45f4-8500-49c6f5fa28ad
The versions:
EC2: AWS amz linux 2, amzn2-ami-ecs-hvm-2.0.20250102-x86_64-ebs
ECS agent: "Starting Amazon ECS Agent" version="1.89.2" commit="41d593c6"
Vector.dev: "timberio/vector:0.43.1-debian"
Questions:
If I have specify v4 in source - and vector can see env ECS_CONTAINER_METADATA_URI_V4 - why does it try to use v3 endpoint? In the doc it is specified that v4 in that case should be used
I can curl to http://169.254.170.2/v3/f4275bb6-2577-45f4-8500-49c6f5fa28ad/task/stats and get payload from ec2 instance itself and from any container in the ECS task. Unfortunately, I can't check if this endpoint is available from vector container. But if endpoint is available from other containers - I assume that it is available from vector container too. The question why it sees null instead of payload.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Good day.
Tried to configure vector to gather ECS task metrics but got an error:
ERROR source{component_kind="source" component_id=source_aws_ecs_metrics component_type=aws_ecs_metrics}: vector::internal_events::aws_ecs_metrics: Parsing error. endpoint=http://169.254.170.2/v3/f4275bb6-2577-45f4-8500-49c6f5fa28ad/task/stats error=Error("invalid type: null, expected struct ContainerStats", line: 1, column: 72) stage="processing" error_type="parser_failed" internal_log_rate_limit=true
Vector configuration:
sources: ... source_aws_ecs_metrics: type: aws_ecs_metrics scrape_interval_secs: 15 version: v4 ...
In a deployed vector container, I can observe environments
ECS_CONTAINER_METADATA_URI=http://169.254.170.2/v3/f4275bb6-2577-45f4-8500-49c6f5fa28ad ECS_CONTAINER_METADATA_URI_V4=http://169.254.170.2/v4/f4275bb6-2577-45f4-8500-49c6f5fa28ad
The versions:
EC2: AWS amz linux 2, amzn2-ami-ecs-hvm-2.0.20250102-x86_64-ebs
ECS agent: "Starting Amazon ECS Agent" version="1.89.2" commit="41d593c6"
Vector.dev: "timberio/vector:0.43.1-debian"
Questions:
Beta Was this translation helpful? Give feedback.
All reactions