Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ECS Fargate service name not working #7154

Open
arunodhayamsam opened this issue Feb 19, 2025 · 1 comment
Open

ECS Fargate service name not working #7154

arunodhayamsam opened this issue Feb 19, 2025 · 1 comment

Comments

@arunodhayamsam
Copy link

Is your feature request related to a problem?

Hi Signoz team, first I would like to appreciate your good product, which Signoz uses for monitoring CNCF products.

I'm having some issues while monitoring my ecs service.

I have hosted the signoz on ec2 using docker-compose, and I configured the ECS monitoring setup with help of this blog post[0], I can see my task definition metrics using sidecar container mechanism, but I couldn't separate the details of the service, for example, I have deployed two aws ecs services with 1 CPU 4 GB memory, but it shows the metrics of two services combined as single like 2 CPU 8 GB , Also I couldn't drop down the ecs service name, the dropdown doesn't show the available ecs services names.

Could you please help on this?

[0] https://signoz.io/docs/userguide/collecting-ecs-sidecar-infra/

Image

``extensions:
health_check:

receivers:
awsecscontainermetrics:
collection_interval: 30s
otlp:
protocols:
grpc:
endpoint: 0.0.0.0:4317
http:
endpoint: 0.0.0.0:4318
fluentforward:
endpoint: 0.0.0.0:8006

processors:
batch:
timeout: 10s
filter:
metrics:
include:
match_type: strict
metric_names:

  • ecs.task.memory.reserved
  • ecs.task.memory.utilized
  • ecs.task.cpu.reserved
  • ecs.task.cpu.utilized
  • ecs.task.network.rate.rx
  • ecs.task.network.rate.tx
  • ecs.task.storage.read_bytes
  • ecs.task.storage.write_bytes
  • container.duration

exporters:
otlp:
endpoint: "http://peek-a-booo:4317/"
tls:
insecure: true
logging:
verbosity: normal

service:
extensions: [health_check]
pipelines:
traces:
receivers: [otlp]
processors: [batch]
exporters: [otlp, logging]
metrics:
receivers: [otlp]
processors: [batch]
exporters: [otlp, logging]
metrics/aws:
receivers: [awsecscontainermetrics]
processors: [filter]
exporters: [otlp, logging]
logs:
receivers: [otlp, fluentforward]
processors: [batch]
exporters: [otlp, logging]
``

Copy link

welcome bot commented Feb 19, 2025

Thanks for opening this issue. A team member should give feedback soon. In the meantime, feel free to check out the contributing guidelines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant