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
root@ip-[REDACTED]:/# agent status
Getting the status from the agent.
===============
Agent (v7.59.0)
===============
Status date: 2024-11-14 18:58:31.577 UTC (1731610711577)
Agent start: 2024-11-14 18:56:59.147 UTC (1731610619147)
Pid: 381
Go Version: go1.19.5
Python Version: 3.8.16
Build arch: amd64
Agent flavor: agent
Check Runners: 4
Log Level: info
Paths
=====
Config File: /etc/datadog-agent/datadog.yaml
conf.d: /etc/datadog-agent/conf.d
checks.d: /etc/datadog-agent/checks.d
Clocks
======
System time: 2024-11-14 18:58:31.577 UTC (1731610711577)
Host Info
=========
bootTime: 2024-11-13 21:02:17 UTC (1731531737000)
hostId: ec2a7065-c340-a4cf-ae2a-96b25e6a4722
kernelArch: x86_64
kernelVersion: 4.14.353-270.569.amzn2.x86_64
os: linux
platform: ubuntu
platformFamily: debian
platformVersion: 22.04
procs: 136
uptime: 21h54m45s
Hostnames
=========
ec2-hostname: ip-10-11-68-34.ec2.internal
host_aliases: [i-06f9d1c7fd31a3cd2]
instance-id: i-06f9d1c7fd31a3cd2
socket-fqdn: ip-[REDACTED].ec2.internal.
socket-hostname: ip-[REDACTED].ec2.internal
hostname provider:
unused hostname providers:
'hostname' configuration/environment: hostname is empty
'hostname_file' configuration/environment: 'hostname_file' configuration is not enabled
Metadata
========
agent_version: 7.59.0
cloud_provider: AWS
config_apm_dd_url:
config_dd_url:
config_logs_dd_url:
config_logs_socks5_proxy_address:
config_no_proxy: []
config_process_dd_url:
config_proxy_http:
config_proxy_https:
config_site:
feature_apm_enabled: true
feature_cspm_enabled: false
feature_cws_enabled: false
feature_logs_enabled: true
feature_networks_enabled: false
feature_networks_http_enabled: false
feature_networks_https_enabled: false
feature_otlp_enabled: false
feature_process_enabled: false
feature_processes_container_enabled: true
feature_usm_go_tls_enabled: false
feature_usm_java_tls_enabled: false
flavor: agent
install_method_installer_version: docker
install_method_tool: docker
install_method_tool_version: docker
logs_transport: HTTP
=========
Collector
=========
Running Checks
==============
container
---------
Instance ID: container [OK]
Configuration Source: file:/etc/datadog-agent/conf.d/container.d/conf.yaml.default
Total Runs: 6
Metric Samples: Last Run: 69, Total: 414
Events: Last Run: 0, Total: 0
Service Checks: Last Run: 0, Total: 0
Average Execution Time : 3ms
Last Execution Date : 2024-11-14 18:58:17 UTC (1731610697000)
Last Successful Execution Date : 2024-11-14 18:58:17 UTC (1731610697000)
docker
------
Instance ID: docker [OK]
Configuration Source: file:/etc/datadog-agent/conf.d/docker.d/conf.yaml.default
Total Runs: 6
Metric Samples: Last Run: 16, Total: 96
Events: Last Run: 1, Total: 4
Service Checks: Last Run: 1, Total: 6
Average Execution Time : 4ms
Last Execution Date : 2024-11-14 18:58:24 UTC (1731610704000)
Last Successful Execution Date : 2024-11-14 18:58:24 UTC (1731610704000)
ecs_fargate (3.3.0)
-------------------
Instance ID: ecs_fargate:fed08cd1baa0bef1 [OK]
Configuration Source: file:/etc/datadog-agent/conf.d/ecs_fargate.d/conf.yaml.default
Total Runs: 5
Metric Samples: Last Run: 61, Total: 305
Events: Last Run: 0, Total: 0
Service Checks: Last Run: 1, Total: 5
Average Execution Time : 10ms
Last Execution Date : 2024-11-14 18:58:22 UTC (1731610702000)
Last Successful Execution Date : 2024-11-14 18:58:22 UTC (1731610702000)
========
JMXFetch
========
Information
==================
Initialized checks
==================
no checks
Failed checks
=============
no checks
=========
Forwarder
=========
Transactions
============
Cluster: 0
ClusterRole: 0
ClusterRoleBinding: 0
CronJob: 0
CustomResource: 0
CustomResourceDefinition: 0
DaemonSet: 0
Deployment: 0
Dropped: 0
HighPriorityQueueFull: 0
Ingress: 0
Job: 0
Namespace: 0
Node: 0
PersistentVolume: 0
PersistentVolumeClaim: 0
Pod: 0
ReplicaSet: 0
Requeued: 0
Retried: 0
RetryQueueSize: 0
Role: 0
RoleBinding: 0
Service: 0
ServiceAccount: 0
StatefulSet: 0
VerticalPodAutoscaler: 0
Transaction Successes
=====================
Total number: 14
Successes By Endpoint:
check_run_v1: 5
intake: 4
series_v2: 5
On-disk storage
===============
On-disk storage is disabled. Configure `forwarder_storage_max_size_in_bytes` to enable it.
API Keys status
===============
API key ending with 4c456: API Key valid
==========
Endpoints
==========
https://app.datadoghq.com - API Key ending with:
- 4c456
==========
Logs Agent
==========
Reliable: Sending compressed logs in HTTPS to agent-http-intake.logs.datadoghq.com on port 443
BytesSent: 6575
EncodedBytesSent: 700
LogsProcessed: 5
LogsSent: 5
ecsfargate
----------
- Type: ecsfargate
Service: example-ecs
Source: example-source
Status: Pending
Bytes Read: 0
Pipeline Latency:
Average Latency (ms): 0
24h Average Latency (ms): 0
Peak Latency (ms): 0
24h Peak Latency (ms): 0
=============
Process Agent
=============
Version: 7.59.0
Status date: 2024-11-14 18:58:32.007 UTC (1731610712007)
Process Agent Start: 2024-11-14 18:56:59.449 UTC (1731610619449)
Pid: 384
Go Version: go1.19.5
Build arch: amd64
Log Level: info
Enabled Checks: [container rtcontainer]
Allocated Memory: 15,334,328 bytes
Hostname:
System Probe Process Module Status: Not running
=================
Process Endpoints
=================
https://process.datadoghq.com - API Key ending with:
- 4c456
=========
Collector
=========
Last collection time: 2024-11-14 18:58:29
Docker socket: /var/run/docker.sock
Number of processes: 0
Number of containers: 3
Process Queue length: 0
RTProcess Queue length: 0
Connections Queue length: 0
Event Queue length: 0
Pod Queue length: 0
Process Bytes enqueued: 0
RTProcess Bytes enqueued: 0
Connections Bytes enqueued: 0
Event Bytes enqueued: 0
Pod Bytes enqueued: 0
Drop Check Payloads: []
=========
APM Agent
=========
Status: Running
Pid: 382
Uptime: 92 seconds
Mem alloc: 10,193,920 bytes
Hostname:
Receiver: 0.0.0.0:8126
Endpoints:
https://trace.agent.datadoghq.com
Receiver (previous minute)
==========================
No traces received in the previous minute.
Writer (previous minute)
========================
Traces: 0 payloads, 0 traces, 0 events, 0 bytes
Stats: 0 payloads, 0 stats buckets, 0 bytes
==========
Aggregator
==========
Checks Metric Sample: 973
Dogstatsd Metric Sample: 903
Event: 4
Events Flushed: 4
Number Of Flushes: 5
Series Flushed: 1,140
Service Check: 28
Service Checks Flushed: 28
=========
DogStatsD
=========
Event Packets: 0
Event Parse Errors: 0
Metric Packets: 902
Metric Parse Errors: 0
Service Check Packets: 0
Service Check Parse Errors: 0
Udp Bytes: 140,994
Udp Packet Reading Errors: 0
Udp Packets: 531
Uds Bytes: 0
Uds Origin Detection Errors: 0
Uds Packet Reading Errors: 0
Uds Packets: 0
Unterminated Metric Errors: 0
=============
Autodiscovery
=============
Enabled Features
================
docker
ecsfargate
====
OTLP
====
Status: Not enabled
Collector status: Not running
Describe what happened:
A week back, we stood up a ECS EC2 for a service request my team had. We setup datadog-agent as a sidecar on the service, we found that ECS_FARGATE will utilize the ecsfargate endpoints to tail regardless of the value of environment variable; but when you completely remove the environment variable, the ecsfargate will not tail, and only tail the docker tailer.
Describe what you expected:
We expected, setting the variable to false, it wouldn't tail the ecsfargate endpoints, but it still does. We expected that setting the variable to false, it would only do docker tailing.
Go to the EC2 Instance, and do docker ps then docker logs <datadog_container> | grep -i tail
Look for tailer open then closed on docker logs. This should not be happening...
This happens, because the context switches back and forth from docker tailing and ecsfargate tailing. But remember, we set the ECS_FARGATE to false; so this technically should have never happened, to resolve this issue is we simply remove the environment variable.
Agent Environment
Describe what happened:
A week back, we stood up a ECS EC2 for a service request my team had. We setup datadog-agent as a sidecar on the service, we found that
ECS_FARGATE
will utilize theecsfargate
endpoints to tail regardless of the value of environment variable; but when you completely remove the environment variable, theecsfargate
will not tail, and only tail the docker tailer.Describe what you expected:
We expected, setting the variable to
false
, it wouldn't tail theecsfargate
endpoints, but it still does. We expected that setting the variable to false, it would only do docker tailing.Steps to reproduce the issue:
docker ps
thendocker logs <datadog_container> | grep -i tail
This happens, because the context switches back and forth from docker tailing and ecsfargate tailing. But remember, we set the
ECS_FARGATE
to false; so this technically should have never happened, to resolve this issue is we simply remove the environment variable.Additional environment details (Operating System, Cloud provider, etc):
Cloud: AWS ECS
Operating System: Linux
I feel as this is a bug. If not, then this should be documented more clearly.
Thanks.
The text was updated successfully, but these errors were encountered: