diff --git a/examples/extras/datadog-agent/dd-agent.kubectl.log b/examples/extras/datadog-agent/dd-agent.kubectl.log deleted file mode 100644 index c35b554..0000000 --- a/examples/extras/datadog-agent/dd-agent.kubectl.log +++ /dev/null @@ -1,304 +0,0 @@ -# agent -% kubectl --kubeconfig setup/kube.config logs -n monitoring pod/datadog-agent-zfvlf -c agent -Error: unable to load Datadog config file: While parsing config: yaml: unmarshal errors: - -# trace-agent -% kubectl --kubeconfig setup/kube.config logs -n monitoring pod/datadog-agent-zfvlf -c trace-agent -WARNING: `-config` argument is deprecated and will be removed in a future version. Please use `--config` instead. -Usage: - trace-agent [command] [flags] - trace-agent [command] - -Available Commands: - completion Generate the autocompletion script for the specified shell - help Help about any command - info Gather Datadog trace-agent information. - run Start datadog trace-agent. - version Print the version info - -Flags: - -c, --config string path to directory containing datadog.yaml (default "/opt/datadog-agent/etc/datadog.yaml") - -l, --cpu-profile string enables CPU profiling and specifies profile path. - -h, --help help for trace-agent - -m, --mem-profile string enables memory profiling and specifies profile. - -p, --pidfile string path for the PID file to be created - -Use "trace-agent [command] --help" for more information about a command. - -Error: unable to load Datadog config file: While parsing config: yaml: unmarshal errors: - -# fips-proxy -% kubectl --kubeconfig setup/kube.config logs -n monitoring pod/datadog-agent-zfvlf -c fips-proxy -HMAC : (Module_Integrity) : Pass -SHA1 : (KAT_Digest) : Pass -SHA2 : (KAT_Digest) : Pass -SHA3 : (KAT_Digest) : Pass -TDES : (KAT_Cipher) : Pass -AES_GCM : (KAT_Cipher) : Pass -AES_ECB_Decrypt : (KAT_Cipher) : Pass -RSA : (KAT_Signature) : RNG : (Continuous_RNG_Test) : Pass -Pass -ECDSA : (PCT_Signature) : Pass -ECDSA : (PCT_Signature) : Pass -DSA : (PCT_Signature) : Pass -TLS13_KDF_EXTRACT : (KAT_KDF) : Pass -TLS13_KDF_EXPAND : (KAT_KDF) : Pass -TLS12_PRF : (KAT_KDF) : Pass -PBKDF2 : (KAT_KDF) : Pass -SSHKDF : (KAT_KDF) : Pass -KBKDF : (KAT_KDF) : Pass -HKDF : (KAT_KDF) : Pass -SSKDF : (KAT_KDF) : Pass -X963KDF : (KAT_KDF) : Pass -X942KDF : (KAT_KDF) : Pass -HASH : (DRBG) : Pass -CTR : (DRBG) : Pass -HMAC : (DRBG) : Pass -DH : (KAT_KA) : Pass -ECDH : (KAT_KA) : Pass -RSA_Encrypt : (KAT_AsymmetricCipher) : Pass -RSA_Decrypt : (KAT_AsymmetricCipher) : Pass -RSA_Decrypt : (KAT_AsymmetricCipher) : Pass -INSTALL PASSED -VERIFY PASSED -[WARNING] (2291086) : *** HAPROXY IS RUNNING IN FIPS MODE *** -[WARNING] (2291086) : datadog-api/mothership1 changed its IP from (none) to 3.32.209.35 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-api/mothership1 ('api.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-api/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-api/mothership2 changed its IP from (none) to 3.32.209.31 by DNS cache. -[WARNING] (2291086) : Server datadog-api/mothership2 ('api.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-api/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-api/mothership3 changed its IP from (none) to 3.32.209.32 by DNS cache. -[WARNING] (2291086) : Server datadog-api/mothership3 ('api.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-api/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-database-monitoring-metrics/mothership1 changed its IP from (none) to 15.205.116.78 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-database-monitoring-metrics/mothership1 ('dbm-metrics-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-database-monitoring-metrics/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-database-monitoring-metrics/mothership2 changed its IP from (none) to 3.30.33.52 by DNS cache. -[WARNING] (2291086) : Server datadog-database-monitoring-metrics/mothership2 ('dbm-metrics-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-database-monitoring-metrics/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-database-monitoring-metrics/mothership3 changed its IP from (none) to 15.200.117.57 by DNS cache. -[WARNING] (2291086) : Server datadog-database-monitoring-metrics/mothership3 ('dbm-metrics-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-database-monitoring-metrics/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-flare/mothership1 changed its IP from (none) to 3.32.209.59 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-flare/mothership1 ('flare.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-flare/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-flare/mothership2 changed its IP from (none) to 3.32.209.57 by DNS cache. -[WARNING] (2291086) : Server datadog-flare/mothership2 ('flare.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-flare/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-flare/mothership3 changed its IP from (none) to 3.32.209.58 by DNS cache. -[WARNING] (2291086) : Server datadog-flare/mothership3 ('flare.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-flare/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-metrics/mothership1 changed its IP from (none) to 3.30.62.176 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-metrics/mothership1 ('haproxy-app.agent.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-metrics/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-metrics/mothership2 changed its IP from (none) to 3.30.62.172 by DNS cache. -[WARNING] (2291086) : Server datadog-metrics/mothership2 ('haproxy-app.agent.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-metrics/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-metrics/mothership3 changed its IP from (none) to 3.30.62.171 by DNS cache. -[WARNING] (2291086) : Server datadog-metrics/mothership3 ('haproxy-app.agent.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-metrics/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-profiles/mothership1 changed its IP from (none) to 3.32.209.201 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-profiles/mothership1 ('intake.profile.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-profiles/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-profiles/mothership2 changed its IP from (none) to 3.32.209.202 by DNS cache. -[WARNING] (2291086) : Server datadog-profiles/mothership2 ('intake.profile.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-profiles/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-profiles/mothership3 changed its IP from (none) to 3.32.209.199 by DNS cache. -[WARNING] (2291086) : Server datadog-profiles/mothership3 ('intake.profile.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-profiles/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-traces/mothership1 changed its IP from (none) to 3.32.209.215 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-traces/mothership1 ('trace.agent.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-traces/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-traces/mothership2 changed its IP from (none) to 3.32.209.216 by DNS cache. -[WARNING] (2291086) : Server datadog-traces/mothership2 ('trace.agent.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-traces/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-traces/mothership3 changed its IP from (none) to 3.32.209.218 by DNS cache. -[WARNING] (2291086) : Server datadog-traces/mothership3 ('trace.agent.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-traces/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-network-devices-netflow/mothership1 changed its IP from (none) to 3.32.209.201 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-network-devices-netflow/mothership1 ('ndmflow-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-network-devices-netflow/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-network-devices-netflow/mothership2 changed its IP from (none) to 3.32.209.202 by DNS cache. -[WARNING] (2291086) : Server datadog-network-devices-netflow/mothership2 ('ndmflow-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-network-devices-netflow/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-network-devices-netflow/mothership3 changed its IP from (none) to 3.32.209.199 by DNS cache. -[WARNING] (2291086) : Server datadog-network-devices-netflow/mothership3 ('ndmflow-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-network-devices-netflow/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-database-monitoring-samples/mothership1 changed its IP from (none) to 15.200.117.57 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-database-monitoring-samples/mothership1 ('dbquery-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-database-monitoring-samples/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-database-monitoring-samples/mothership2 changed its IP from (none) to 3.30.33.52 by DNS cache. -[WARNING] (2291086) : Server datadog-database-monitoring-samples/mothership2 ('dbquery-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-database-monitoring-samples/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-database-monitoring-samples/mothership3 changed its IP from (none) to 15.205.116.78 by DNS cache. -[WARNING] (2291086) : Server datadog-database-monitoring-samples/mothership3 ('dbquery-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-database-monitoring-samples/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-processes/mothership1 changed its IP from (none) to 3.30.62.159 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-processes/mothership1 ('process.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-processes/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-processes/mothership2 changed its IP from (none) to 3.30.62.164 by DNS cache. -[WARNING] (2291086) : Server datadog-processes/mothership2 ('process.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-processes/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-processes/mothership3 changed its IP from (none) to 3.30.62.160 by DNS cache. -[WARNING] (2291086) : Server datadog-processes/mothership3 ('process.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-processes/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-synthetics/mothership1 changed its IP from (none) to 3.30.62.132 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-synthetics/mothership1 ('intake.synthetics.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-synthetics/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-synthetics/mothership2 changed its IP from (none) to 3.30.62.133 by DNS cache. -[WARNING] (2291086) : Server datadog-synthetics/mothership2 ('intake.synthetics.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-synthetics/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-synthetics/mothership3 changed its IP from (none) to 3.30.62.127 by DNS cache. -[WARNING] (2291086) : Server datadog-synthetics/mothership3 ('intake.synthetics.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-synthetics/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-instrumentations-telemetry/mothership1 changed its IP from (none) to 3.32.209.58 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-instrumentations-telemetry/mothership1 ('instrumentation-telemetry-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-instrumentations-telemetry/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-instrumentations-telemetry/mothership2 changed its IP from (none) to 3.32.209.57 by DNS cache. -[WARNING] (2291086) : Server datadog-instrumentations-telemetry/mothership2 ('instrumentation-telemetry-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-instrumentations-telemetry/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-instrumentations-telemetry/mothership3 changed its IP from (none) to 3.32.209.59 by DNS cache. -[WARNING] (2291086) : Server datadog-instrumentations-telemetry/mothership3 ('instrumentation-telemetry-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-instrumentations-telemetry/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-network-devices-metadata/mothership1 changed its IP from (none) to 3.32.209.199 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-network-devices-metadata/mothership1 ('ndm-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-network-devices-metadata/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-network-devices-metadata/mothership2 changed its IP from (none) to 3.32.209.201 by DNS cache. -[WARNING] (2291086) : Server datadog-network-devices-metadata/mothership2 ('ndm-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-network-devices-metadata/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-network-devices-metadata/mothership3 changed its IP from (none) to 3.32.209.202 by DNS cache. -[WARNING] (2291086) : Server datadog-network-devices-metadata/mothership3 ('ndm-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-network-devices-metadata/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-logs-http/mothership1 changed its IP from (none) to 3.32.209.243 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-logs-http/mothership1 ('agent-http-intake.logs.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-logs-http/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-logs-http/mothership2 changed its IP from (none) to 3.32.209.245 by DNS cache. -[WARNING] (2291086) : Server datadog-logs-http/mothership2 ('agent-http-intake.logs.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-logs-http/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-logs-http/mothership3 changed its IP from (none) to 3.32.209.244 by DNS cache. -[WARNING] (2291086) : Server datadog-logs-http/mothership3 ('agent-http-intake.logs.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-logs-http/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-runtime-security/mothership1 changed its IP from (none) to 3.32.209.245 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-runtime-security/mothership1 ('runtime-security-http-intake.logs.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-runtime-security/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-runtime-security/mothership2 changed its IP from (none) to 3.32.209.243 by DNS cache. -[WARNING] (2291086) : Server datadog-runtime-security/mothership2 ('runtime-security-http-intake.logs.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-runtime-security/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-runtime-security/mothership3 changed its IP from (none) to 3.32.209.244 by DNS cache. -[WARNING] (2291086) : Server datadog-runtime-security/mothership3 ('runtime-security-http-intake.logs.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-runtime-security/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-network-devices-snmp-traps/mothership1 changed its IP from (none) to 3.32.209.199 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-network-devices-snmp-traps/mothership1 ('snmp-traps-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-network-devices-snmp-traps/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-network-devices-snmp-traps/mothership2 changed its IP from (none) to 3.32.209.202 by DNS cache. -[WARNING] (2291086) : Server datadog-network-devices-snmp-traps/mothership2 ('snmp-traps-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-network-devices-snmp-traps/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-network-devices-snmp-traps/mothership3 changed its IP from (none) to 3.32.209.201 by DNS cache. -[WARNING] (2291086) : Server datadog-network-devices-snmp-traps/mothership3 ('snmp-traps-intake.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-network-devices-snmp-traps/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-orchestrator-explorer/mothership1 changed its IP from (none) to 3.30.62.148 by my-dns/172.20.0.10. -[WARNING] (2291086) : Server datadog-orchestrator-explorer/mothership1 ('orchestrator.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-orchestrator-explorer/mothership1 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-orchestrator-explorer/mothership2 changed its IP from (none) to 3.30.62.144 by DNS cache. -[WARNING] (2291086) : Server datadog-orchestrator-explorer/mothership2 ('orchestrator.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-orchestrator-explorer/mothership2 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : datadog-orchestrator-explorer/mothership3 changed its IP from (none) to 3.30.62.149 by DNS cache. -[WARNING] (2291086) : Server datadog-orchestrator-explorer/mothership3 ('orchestrator.ddog-gov.com') is UP/READY (resolves again). -[WARNING] (2291086) : Server datadog-orchestrator-explorer/mothership3 administratively READY thanks to valid DNS answer. -[WARNING] (2291086) : Server datadog-metrics/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-metrics/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-api/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-api/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-api/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[NOTICE] (2291086) : haproxy version is 2.4.25-6cfe787 -[NOTICE] (2291086) : path to executable is /opt/datadog-fips-proxy/embedded/sbin/haproxy -[ALERT] (2291086) : backend 'datadog-api' has no server available! -[WARNING] (2291086) : Server datadog-flare/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10003ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-flare/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-flare/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-flare' has no server available! -[WARNING] (2291086) : Server datadog-traces/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-traces/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-traces/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-traces' has no server available! -[WARNING] (2291086) : Server datadog-profiles/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-profiles/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-profiles/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-profiles' has no server available! -[WARNING] (2291086) : Server datadog-processes/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-processes/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-processes/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-processes' has no server available! -[WARNING] (2291086) : Server datadog-logs-http/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-logs-http/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-logs-http/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-logs-http' has no server available! -[WARNING] (2291086) : Server datadog-database-monitoring-metrics/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-database-monitoring-metrics/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-database-monitoring-metrics/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-database-monitoring-metrics' has no server available! -[WARNING] (2291086) : Server datadog-database-monitoring-samples/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10002ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-database-monitoring-samples/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-database-monitoring-samples/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-database-monitoring-samples' has no server available! -[WARNING] (2291086) : Server datadog-network-devices-metadata/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-network-devices-metadata/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-network-devices-metadata/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-network-devices-metadata' has no server available! -[WARNING] (2291086) : Server datadog-network-devices-snmp-traps/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-network-devices-snmp-traps/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-network-devices-snmp-traps/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-network-devices-snmp-traps' has no server available! -[WARNING] (2291086) : Server datadog-network-devices-netflow/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-network-devices-netflow/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-network-devices-netflow/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-network-devices-netflow' has no server available! -[WARNING] (2291086) : Server datadog-instrumentations-telemetry/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-instrumentations-telemetry/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-instrumentations-telemetry/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-instrumentations-telemetry' has no server available! -[WARNING] (2291086) : Server datadog-synthetics/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-synthetics/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-synthetics/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-synthetics' has no server available! -[WARNING] (2291086) : Server datadog-orchestrator-explorer/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-orchestrator-explorer/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-orchestrator-explorer/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-orchestrator-explorer' has no server available! -[WARNING] (2291086) : Server datadog-runtime-security/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-runtime-security/mothership2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[WARNING] (2291086) : Server datadog-runtime-security/mothership3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-runtime-security' has no server available! -[WARNING] (2291086) : Server datadog-metrics/mothership1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. -[ALERT] (2291086) : backend 'datadog-metrics' has no server available! - -# process-agent -% kubectl --kubeconfig setup/kube.config logs -n monitoring pod/datadog-agent-zfvlf -c process-agent -Failed to initialize the process agent: unable to load Datadog config file: While parsing config: yaml: unmarshal errors: - -# system-probe -% kubectl --kubeconfig setup/kube.config logs -n monitoring pod/datadog-agent-zfvlf -c system-probe -2024-03-08 21:16:49 UTC | SYS-PROBE | WARN | (pkg/util/log/log.go:693 in func1) | Unknown key in config file: runtime_security_config.syscall_monitor.enabled -2024-03-08 21:16:49 UTC | SYS-PROBE | WARN | (pkg/util/log/log.go:693 in func1) | Unknown key in config file: runtime_security_config.network.enabled -2024-03-08 21:16:49 UTC | SYS-PROBE | WARN | (pkg/util/log/log.go:693 in func1) | Unknown key in config file: runtime_security_config.activity_dump.cgroup_wait_list_size -2024-03-08 21:16:49 UTC | SYS-PROBE | WARN | (pkg/util/log/log.go:693 in func1) | Unknown key in config file: runtime_security_config.activity_dump.path_merge.enabled -2024-03-08 21:16:49 UTC | SYS-PROBE | WARN | (pkg/util/log/log.go:688 in func1) | configuration key `network_config.enable_http_monitoring` is deprecated, use `service_monitoring_config.enable_http_monitoring` instead -2024-03-08 21:16:49 UTC | SYS-PROBE | WARN | (pkg/util/log/log.go:688 in func1) | configuration key `network_config.enable_https_monitoring` is deprecated, use `service_monitoring_config.tls.native.enabled` instead -2024-03-08 21:16:49 UTC | SYS-PROBE | WARN | (pkg/util/log/log.go:688 in func1) | configuration key `runtime_security_config.activity_dump.cgroup_dump_timeout` is deprecated, use `runtime_security_config.activity_dump.dump_duration` instead -2024-03-08 21:16:49 UTC | SYS-PROBE | WARN | (pkg/config/model/viper.go:340 in GetStringSlice) | failed to get configuration value for key "flare_stripped_keys": unable to cast of type to []string -2024-03-08 21:16:49 UTC | SYS-PROBE | WARN | (pkg/config/setup/config.go:1549 in LoadDatadogCustom) | Error loading config: While parsing config: yaml: unmarshal errors: - line 1: cannot unmarshal !!bool `true` into map[string]interface {} -2024-03-08 21:16:49 UTC | SYS-PROBE | INFO | (pkg/config/env/environment_detection.go:124 in DetectFeatures) | 1 Features detected from environment: kubernetes -Error: unable to load Datadog config file: While parsing config: yaml: unmarshal errors: - -# init-volume -% kubectl --kubeconfig setup/kube.config logs -n monitoring pod/datadog-agent-zfvlf -c init-volume - -# init-config -% kubectl --kubeconfig setup/kube.config logs -n monitoring pod/datadog-agent-zfvlf -c init-config -Disabling the apiserver check as leader election is disabled - -# seccomp-setup -% kubectl --kubeconfig setup/kube.config logs -n monitoring pod/datadog-agent-zfvlf -c seccomp-setup -