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

chore(deps): update datadog/agent docker tag to v6.53.0 #153

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 14, 2022

This PR contains the following updates:

Package Type Update Change
datadog/agent final minor 6.3.3 -> 6.53.0

Release Notes

DataDog/datadog-agent (datadog/agent)

v6.53.0

Compare Source

================

.. _Release Notes_7.53.0_Prelude:

Prelude

Release on: 2024-04-30

  • Please refer to the 7.53.0 tag on integrations-core <https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7530>_ for the list of changes on the Core Checks

.. _Release Notes_7.53.0_New Features:

New Features

  • Support database-monitoring autodiscovery for Aurora cluster instances. Adds a new configuration listener to poll
    for a specific set of Aurora cluster IDs and then create a new database-monitoring supported check
    configuration for each endpoint. This allows for monitoring of endpoints that scale dynamically.

  • Add new core check orchestrator_ecs to collect running ECS tasks

  • APM stats now include an is_trace_root field to indicate if the stats are from the root span of a trace.

  • The cluster-agent now collects network policies from the cluster.

  • Enable 'host_benchmarks' by default when running the security-agent compliance module.

  • OTLP ingest now has a feature flag to identify top-level spans by span kind. This new logic can be enabled by adding enable_otlp_compute_top_level_by_span_kind in DD_APM_FEATURES.

    • With this new logic, root spans and spans with a server or consumer span.kind will be marked as top-level. Additionally, spans with a client or producer span.kind will have stats computed.
    • Enabling this feature flag may increase the number of spans that generate trace metrics, and may change which spans appear as top-level in Datadog.
  • Experimental: The process-agent checks (process, container, and process-discovery) can be run from the Core Agent in
    Linux. This feature can be toggled on by setting the process_config.run_in_core_agent.enabled flag to true in
    the datadog.yaml file. This feature is disabled by default.

.. _Release Notes_7.53.0_Enhancement Notes:

Enhancement Notes

  • Add the container image and container lifecycle checks to the output of the Agent status command.

  • Add kubelet_core_check_enabled flag to Agent config to control
    whether the kubelet core check should be loaded.

  • Added LastSuccessfulTime to cronjob status payload.

  • Add a retry mechanism to Software Bill of Materials (SBOM) collection for container images.
    This will help to avoid intermittent failures during the collection process.

  • Add startup timestamp to the Agent metadata payload.

  • Agents are now built with Go 1.21.9.

  • Adds image repo digest string to the container payload when present

  • CWS: Add selftests report on Windows and platforms with no eBPF support.

  • CWS: Add visibility for cross container program executions on platforms with no eBPF support.

  • APM: Enable credit card obfuscation by default. There is a small chance that numbers that are similar to valid credit cards may be redacted, this feature can be disabled by using apm_config.obfuscation.credit_cards.enabled. Alternatively, it can be made more accurate through luhn checksum verification by using apm_config.obfuscation.credit_cards.luhn, however, this increases the performance penalty of this check.

  • logs_config.expected_tags_duration now works for journald logs.

  • [oracle] Adds oracle.can_query service check.

  • [oracle] Automatically fall back to deprecated Oracle integration mode if privileges are missing.

  • [oracle] Add service configuration parameter.

  • The connections check no longer relies on the process/container check as it can now
    fetch container data independently.

  • The performance of Remote Config has been significantly improved when large amounts of configurations are received.

  • Send ECS task lifecycle events in the container lifecycle check.

  • dbm: add new SQL obfuscation mode normalize_only to support normalizing SQL without obfuscating it.
    This mode is useful for customers who want to view unobfuscated SQL statements.
    By default, ObfuscationMode is set to obfuscate_and_normalize and every SQL statement is obfuscated and normalized.

  • USM: Handle the HTTP TRACE method.

.. _Release Notes_7.53.0_Deprecation Notes:

Deprecation Notes

  • [oracle] Deprecating Oracle integration code. The functionality is fully implemented in the oracle-dbm check which is now renamed to oracle.

.. _Release Notes_7.53.0_Bug Fixes:

Bug Fixes

  • The windows_registry check can be run with the check sub-command.

  • CWS: Fix very rare event corruption.

  • Fixes issue where processes for ECS Fargate containers would sometimes not be associated
    with the correct container.

  • Fixed a bug in the Dual Shipping feature where events were not being
    emitted on endpoint recovery.

  • Fix issue with display_container_name being tagged as N/A
    when container_name information is available.

  • Fix a Windows process handle leak in the Process Agent, which was introduced in 7.52.0 when process_collection is enabled.

  • Fixes a bug where the tagger server did not properly handle a closed channel.

  • [oracle] Set the default for metric_prefix in custom_queries to oracle.

  • [oracle] Fix global_custom_queries bug.

  • [oracle] Adds the oracle.process.pga_maximum_memory metric for backward compatibility.

  • Stop sending systemd metrics when they are not set

.. _Release Notes_7.52.1:

v6.52.1

Compare Source

================

.. _Release Notes_7.52.1_Prelude:

Prelude

Release on: 2024-04-04

.. _Release Notes_7.52.1_Enhancement Notes:

Enhancement Notes

  • Add a check to the Windows installer to verify that the caller has the correct membership to install the Agent.
  • Ensure the metadata requests are delayed at Agent startup to reduce host tag delays.

.. _Release Notes_7.52.0:

v6.52.0

Compare Source

================

.. _Release Notes_7.52.0_Prelude:

Prelude

Release on: 2024-03-21

  • Please refer to the 7.52.0 tag on integrations-core <https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7520>_ for the list of changes on the Core Checks

.. _Release Notes_7.52.0_Upgrade Notes:

Upgrade Notes

  • To prevent misconfigurations, the Windows Datadog Agent installer now raises an error if
    the user account running the installer MSI is provided as the ddagentuser (DDAGENTUSER_NAME) account.
    If the account is a service account, such as LocalSystem or a gMSA account, no action is needed.
    If the account is a regular account, configure a different Datadog Agent service account.

.. _Release Notes_7.52.0_New Features:

New Features

  • Add device_type to the device metadata.

  • Attach host tags to metrics for expected_tags_duration amount of time.

  • APM stats will now include, if present, the Git commit SHA from traces (or container tags) and the image tag from container tags.

  • Creation of a new packageSigning component to collect Linux package signature information and improve signature rotation process. More information can be found in DataDog documentation at 2024 linux key rotation <https://docs.datadoghq.com/agent/guide/linux-key-rotation-2024>_.

  • Adds support for span links <https://docs.datadoghq.com/tracing/trace_collection/span_links/>_ in the trace agent. This field
    contains a list of casual relationships between spans and is only
    populated when v0.4 of the Trace API is used.

  • The Windows Agent now supports CWS for process and network threats.

  • CWS: Add chdir event to allow recent container escape detection.

  • CWS: [BETA] Add File Integrity Monitoring support on Windows, supporting both files and registry.

  • CWS: The Agent now automatically suppresses benign security events if they have already been reported for a particular container image.

  • Updating process agent discovery configuration to include a Data Scrubber for obfuscating sensitive information such as passwords, API keys, or tokens.

  • Add support for pinging network devices in the SNMP integration.

  • [oracle] Add oracle.locks.transaction_duration metric.

  • APM: Add support for Single Step Instrumentation remote configuration

  • Headless agent installation support on macOS 14 and later

.. _Release Notes_7.52.0_Enhancement Notes:

Enhancement Notes

  • [DBM] Increase the DBM dbm-metrics-intake endpoint's defaultInputChanSize value to 500.

  • Add debug level logs when files are evicted from registry.json
    after their TTL expires.

  • Add the instance ID returned by the IMDSv2 metadata endpoint to the list of EC2 host aliases.

  • This change adds journald permissions to the flare in the
    logs_file_permissions.log file, in the form of either the
    journald directory or a specific file (if specified by the
    Agent journald configuration).

  • The Logs Agent now creates a file in the flare, called
    logs_file_permissions.log, which lists every file and
    that file's permissions that the Logs Agent can detect.

  • Add the SBOM check to the output of the Agent status command and the Agent flare.

  • Add the Software Bill of Materials (SBOM) for container images to the output of the flare command.

  • Add repo_digest to containerd ContainerImage to remove duplicate images in container images UI.

  • Agents are now built with Go 1.21.7.

  • Agents are now built with Go 1.21.8.

  • CWS: Improved coverage on platforms with no eBPF support.

  • CWS: Send context of variables in events.

  • Add DD_APM_DEBUGGER_DIAGNOSTICS_DD_URL, DD_APM_DEBUGGER_DIAGNOSTICS_API_KEY,
    and DD_APM_DEBUGGER_DIAGNOSTICS_ADDITIONAL_ENDPOINTS to allow sending Live
    Debugger / Dynamic Instrumentation diagnostic data to multiple intakes.

  • Added config that allows user to toggle on and off the collection of zombie processes in the Process Agent.

  • [oracle] Add ddagenthostname tag.

  • [oracle]: Add oracle.tablespace.maxsize metric.

  • OTLP ingest supports stable Java runtime metrics introduced in opentelemetry-java-instrumentation v2.0.0.
    OTLP ingest supports Kafka metrics mapping. This allows users of the JMX Receiver/JMX Metrics Gatherer and Kafka metrics receiver to have access to the OOTB Kafka Dashboard.

  • Modified the process check to populate process with the newly created field "ProcessContext"

  • Rename the kubelet_core check to kubelet and change the metrics
    prefix from kubernetes_core to kubernetes so that it can replace
    the Python kubelet check.

  • APM: Adds msgp_short_bytes reason for trace payloads dropped to distinguish them from EOF errors.

  • When getting resource tags from an ECS task with zero containers, print a warn log instead of error log.

.. _Release Notes_7.52.0_Deprecation Notes:

Deprecation Notes

  • Removal of the pod check from the process agent. The current check will run from the core agent.

  • This release drops support for Red Hat Enterprise Linux 6 and its derivatives.

  • [oracle] Deprecate the configuration parameter instant_client. Replacing it with oracle_client.

  • Removed the system-probe configuration value data_streams_config.enabled and replaced it with service_monitoring_config.enable_kafka_monitoring.
    This also implies that the DsmEnabled field in the AgentConfiguration proto will consistently be set to false.

.. _Release Notes_7.52.0_Bug Fixes:

Bug Fixes

  • Upgrade dependencies for systemd core check. This silences excessive warning logs on systemd v252.

  • oracle: Fix wrong tablespace metrics.

  • APM: Stop dropping incoming OTel payloads when the processing channel is full
    and eliminate OOM issues in the trace agent and collector component in high
    load scenarios, making the OTel pipeline more reliable.

  • Fix dogstatsd-capture. Message PID was not set after the 7.50 release.

  • Fix a memory exception where the flare controller tries to
    stat a file that doesn't exist.

  • Fleet Automation filters in the Datadog UI now accurately reflect which products are enabled when deployed with the official DataDog Helm chart on Kubernetes.

  • Corrected a problem where the ignore_autodiscovery_tags parameter was not functioning correctly with pod
    annotations or autodiscovery version 2 (adv2) annotations. This fix ensures that when this parameter is set
    to true, autodiscovery tags are ignored as intended.
    Example:

    ad.datadoghq.com/redis.checks: |
      {
        "redisdb": {
          "ignore_autodiscovery_tags": true,
          "instances": [
            {
              "host": "%%host%%",
              "port": "6379"
            }
          ]
        }
      }

    Moving forward, configurations that attempt to use hybrid setups—combining adv2 for check specification
    while also employing adv1 for ignore_autodiscovery_tags—are no longer supported by default.
    Users should set the configuration parameter cluster_checks.support_hybrid_ignore_ad_tags to true
    to enable this behavior.

  • [oracle]: Add support for more Asian character sets.

  • Prevention of OOMs when collecting a large number of zombie processes.

  • Fixed race conditions caused by concurrent execution of etw.StartEtw()
    and etw.StopEtw() functions which may concurrently access and modify a
    global map.

  • Fix recent PR #​22664 which in turn fixes a race condition in the ETW package.
    The previous PR introduced a minor error addressed in this PR.

  • [oracle] Add resource_manager configuration to conf.yaml.example.

  • [oracle] Fix multi-tagging bug.

  • Fixes a bug in OTLP ingest where empty histograms were not being sent to the backend in the distributions mode. Empty histograms are now mapped as if they had a single (min, max) bucket.

  • Scrub authentication bearer token of any size, even invalid, from integration configuration (when being printed
    through the checksconfig CLI command or other).

  • Empty UDS payloads no longer cause the DogStatsD server to close the socket.

.. _Release Notes_7.52.0_Other Notes:

Other Notes

  • The version of Python required for tooling in README matches that which the CI uses.

.. _Release Notes_7.51.1:

v6.51.1

Compare Source

================

.. _Release Notes_7.51.1_Prelude:

Prelude

Release on: 2024-02-29

  • Please refer to the 7.51.1 tag on integrations-core <https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7511>_ for the list of changes on the Core Checks

.. _Release Notes_7.51.1_New Features:

New Features

  • Add the chdir event type to CWS.

.. _Release Notes_7.51.1_Security Notes:

Security Notes

  • Bump embedded Python version to 3.11.8 to address CVE-2023-5678 on Windows.

.. _Release Notes_7.51.1_Bug Fixes:

Bug Fixes

  • Fix a crash in the win32_event_log check that occurs when processing an event that has
    a missing publisher and no EventData.

.. _Release Notes_7.51.0:

v6.51.0

================

.. _Release Notes_7.51.0_Prelude:

Prelude

Release on: 2024-02-19

  • Please refer to the 7.51.0 tag on integrations-core <https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7510>_ for the list of changes on the Core Checks

.. _Release Notes_7.51.0_Upgrade Notes:

Upgrade Notes

  • The orchestrator check is moving from the Process Agent to the Core Agent. Any orchestrator configuration set on the Process Agent will need to be moved to the Core Agent. No other changes are required. If you need to go back to the old check, you can do so temporarily by manually setting the environment variable DD_ORCHESTRATOR_EXPLORER_RUN_ON_NODE_AGENT to false. The Process Agent pod check will be deprecated in the following release.

  • Upgrade the Python version from 3.9 to 3.11.

.. _Release Notes_7.51.0_New Features:

New Features

  • Add support for ARM64 SLES flavor of datadog-agent

  • Add support for multiple users when listening for SNMP traps.

  • Add check_delay metric in Agent telemetry

  • Add an ETW component for ETW tracing.

  • Add an ETW APM tracer component to forward .Net ETW events to the Tracer Agent.

  • DBM: Add configuration options to SQL obfuscator to customize the normalization of SQL statements:

    • KeepTrailingSemicolon - disable removing trailing semicolon. This option is only valid when ObfuscationMode is obfuscate_and_normalize.
    • KeepIdentifierQuotation - disable removing quotation marks around identifiers. This option is only valid when ObfuscationMode is obfuscate_and_normalize.
  • CWS: [BETA] early support based on ptrace for platforms with no eBPF support.
    Only processes and files are currently supported.

  • Add msodbcsql18 linux dependency needed for SQL Server to run in Docker Agent.

  • Add timestamps to the logs HTTP client

  • Add support for Oracle Active Data Guard.

  • Re-enable Aerospike in SUSE packages.

.. _Release Notes_7.51.0_Enhancement Notes:

Enhancement Notes

  • Updated the ntp check to support the default location of chrony.conf
    on Ubuntu (/etc/chrony/chrony.conf).

  • Agents are now built with Go 1.21.5.

  • CWS: Reloading the datadog-agent-sysprobe systemd service now reloads the runtime security policies.

  • CWS: Added ssdeep file hashing algorithm support.

  • USM will report the actual status code of the HTTP traffic, instead of reporting
    only the status code family (2xx, 3xx, etc.).

  • Improved performance of the activity sampling query on RDS and Oracle Cloud databases.

  • OTLP ingest log timestamps (i.e. '@​timestamp') now include milliseconds.

  • Always report the following telemetry metrics about the retry queue capacity:

    • datadog.agent.retry_queue_duration.capacity_secs
    • datadog.agent.retry_queue_duration.bytes_per_sec
    • datadog.agent.retry_queue_duration.capacity_bytes
  • Support container metrics for kata containers using containerd.

  • System Probe can now expose its healthcheck on a dedicated HTTP port.
    The Kubernetes daemonset uses this by default on port 5558.

.. _Release Notes_7.51.0_Deprecation Notes:

Deprecation Notes

  • The config value ipc_address is deprecated in favor of cmd_host.

  • service_monitoring_config.process_service_inference.enabled is deprecated and replaced by system_probe_config.process_service_inference.enabled
    service_monitoring_config.process_service_inference.use_windows_service_name is deprecated and replaced by system_probe_config.process_service_inference.use_windows_service_name

  • Removes freetds and msodbcsql18 dependencies for py2.

  • Removes postgresql dependency after upgrading psycopg2 to v2.9 in integrations-core.
    psycopg2 now comes with pre-built wheel for arm architecture.

  • An error will now be logged if replace tags are used to change the Agent
    "env", since this could have negative side effects. At this time, an error
    is logged, but future versions may explicitly disallow this to avoid bugs.
    See https://docs.datadoghq.com/getting_started/tracing/#environment-name
    for instructions on settihttps://github.com/DataDog/datadog-agent/issues/21253g-agent/issues/21253 for more details
    about this issue.

.. _Release Notes_7.51.0_Bug Fixes:

Bug Fixes

  • CWS/CSPM: Fixes the hostname value attached to CWS and CSPM events, which in rare cases
    the security agent computed incorrectly.

  • Fix file_handle core check on Darwin by using sysctl system call.

  • Fix spikes for bandwidth usage metric when interface speed is auto-adjusted.

  • Fixes Agent startup script when enabling OOM Kill and TCP Queue Length checks to prevent crashes when restarting the container.

  • Fix a spewing error message ("DCA Client not initialized by main provider, cannot post heartbeat") in the cluster check runner log during CLC initialization.

  • Fixed Logs Agent additional endpoints to respect their
    logs_no_ssl setting.

  • [DBM] Add Oracle broken connection handling on Windows

  • Fix indentation in conf.yaml.example.

  • Bug fix for empty database names in query samples.

  • Bug fix for the Korean character set for Windows.

  • Fixing the issue with a Korean character set for Windows.

  • Fix missing sysmetrics, such as shared pool and library cache.

  • Bug fix for missing tags.

  • Fixed obfuscation error false positive when the access or filter predicates are empty.

  • Fix resource manager metrics collection bugs.

  • Pause containers from the Rancher image-mirror repository (rancher/mirrored-pause.*) are now excluded by default for containers and metrics collection.

  • Error messages from Go checks are now shown on the Agent GUI status page
    instead of UNKNOWN ERROR.

.. _Release Notes_7.51.0_Other Notes:

Other Notes

  • Update s6-overlay version used in Datadog Agent container images to v2.2.0.3

  • Added a warning when logs_no_ssl is set and dd_url
    contains an https prefix. logs_no_ssl will take precedence
    over the prefix in a future version.

.. _Release Notes_7.50.3:

v6.50.3

================

.. _Release Notes_7.50.3_Prelude:

Prelude

Release on: 2024-01-11

.. _Release Notes_7.50.3_Bug Fixes:

Bug Fixes

  • Fix incorrect metadata about system-probe being sent to Inventory and Fleet Automation products.

.. _Release Notes_7.50.2:

v6.50.2

================

.. _Release Notes_7.50.2_Prelude:

Prelude

Release on: 2024-01-04

  • Please refer to the 7.50.2 tag on integrations-core <https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7502>_ for the list of changes on the Core Checks

.. _Release Notes_7.50.2_Enhancement Notes:

Enhancement Notes

  • Agents are now built with Go 1.20.12.

.. _Release Notes_7.50.2_Bug Fixes:

Bug Fixes

  • The CWS configuration parameter to enable anomaly detection is now working and taken
    into account by the Agent.

  • Fix issue introduced in 7.47 that allowed all users to start/stop the
    Windows Datadog Agent services. The Windows installer now, as in versions
    before 7.47, grants this permission explicitly to ddagentuser.

.. _Release Notes_7.50.1:

v6.50.1

================

.. _Release Notes_7.50.1_Prelude:

Prelude

Release on: 2023-12-21

Bug Fixes

  • Fixes a bug introduced in 7.50.0 preventing DD_TAGS to be added to kubernetes_state.* metrics.

.. _Release Notes_7.50.0:

v6.50.0

================

.. _Release Notes_7.50.0_Prelude:

Prelude

Release on: 2023-12-18

  • Please refer to the 7.50.0 tag on integrations-core <https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7500>_ for the list of changes on the Core Checks

.. _Release Notes_7.50.0_Upgrade Notes:

Upgrade Notes

  • The win32_event_log check <https://docs.datadoghq.com/integrations/win32_event_log/?tab=events>_
    has moved from Python (integrations-core#16108) <https://github.com/DataDog/integrations-core/pull/16108>_
    to Go (#&#8203;20701 <https://github.com/DataDog/datadog-agent/pull/20701>).
    All legacy_mode: false configuration options are backwards compatible except for some regular expressions
    used in the included_messages and excluded_messages options.
    For example, Go regular expressions do not support lookahead or lookbehind assertions. If you do not
    use these options, then no configuration changes are necessary.
    See the Python regular expression docs <https://docs.python.org/3/library/re.html>
    and the
    Go regular expression docs <https://github.com/google/re2/wiki/Syntax>_ for more information on
    the supported regular expression syntax.
    Set legacy_mode_v2: true to revert to the Python implementation of the check. The Python implementation
    may be removed in a future version of the Agent.

.. _Release Notes_7.50.0_New Features:

New Features

  • The orchestrator check is moving from the Process Agent to the Node Agent. In the next release, this new check will replace the current pod check in the Process Agent. You can start using this new check now by manually setting the environment variable DD_ORCHESTRATOR_EXPLORER_RUN_ON_NODE_AGENT to true.

  • Adds the following CPU manager metrics to the kubelet core check: kubernetes_core.kubelet.cpu_manager.pinning_errors_total, kubernetes_core.kubelet.cpu_manager.pinning_requests_total.

  • Add a diagnosis for connecting to the agent logs endpoints. This is accessible through the agent diagnose command.

  • Add FIPS mode support for Network Device Monitoring products

  • Added support for collecting Cloud Foundry container names without the Cluster Agent.

  • The Kubernetes State Metrics Core check now collects kubernetes_state.ingress.tls.

  • APM: Added a new endpoint tracer_flare/v1/. This endpoint acts as a
    proxy to forward HTTP POST request from tracers to the serverless_flare
    endpoint, allowing tracer flares to be triggered via remote config, improving
    the support experience by automating the collection of logs.

  • CWS: Ability to send a signal to a process when a rule was triggered.
    CWS: Add Kubernetes user session context to events, in particular the username, UID and groups of the user that ran the commands remotely.

  • Enable container image collection by default.

  • Enable container lifecycle events collection by default.
    This feature helps stopped containers to be cleaned from Datadog faster.

  • [netflow] Allow collecting configurable fields for Netflow V9/IPFIX

  • Add support for Oracle 12.1 and Oracle 11.

  • Add monitoring of Oracle ASM disk groups.

  • Add metrics for monitoring Oracle resource manager.

  • [corechecks/snmp] Load downloaded profiles

  • DBM: Add configuration option to SQL obfuscator to use go-sqllexer package to run SQL obfuscation and normalization

  • Support filtering metrics from endpoint and service checks based
    on namespace when the DD_CONTAINER_EXCLUDE_METRICS environment
    variable is set.

  • The Windows Event Log tailer saves its current position in an event log and
    resumes reading from that location when the Agent restarts. This allows
    the Agent to collect events created before the Agent starts.

.. _Release Notes_7.50.0_Enhancement Notes:

Enhancement Notes

  • [corechecks/snmp] Support symbol modifiers for global metric tags and metadata tags.

  • Update the go-systemd package to the latest version (22.5.0).

  • Added default peer tags for APM stats aggregation which can be enabled through a new flag (peer_tags_aggregation).

  • Add a stop timeout to the Windows Agent services. If an Agent service
    does not cleanly stop within 15 seconds after receiving a stop command
    from the Service Control Manager, the service will hard stop.
    The timeout can be configured by setting the DD_WINDOWS_SERVICE_STOP_TIMEOUT_SECONDS
    environment variable.
    Agent stop timeouts are logged to the Windows Event Log and can be monitored and alerted on.

  • APM: OTLP: Add support for custom container tags via resource attributes prefixed by datadog.container.tag.*.

  • Agents are now built with Go 1.20.11.

  • CWS: Support for Ubuntu 23.10.
    CWS: Reduce memory usage of ring buffer on machines with more than 64 CPU cores.
    CSPM: Move away from libapt to run Debian packages compliance checks.

  • DBM: Bump the minimum version of the go-sqllexer library to 0.0.7 to support collecting stored procedure names.

  • Add subcommand diagnose show-metadata gohai for gohai data

  • Upgraded JMXFetch to 0.49.0 which adds some more telemetry
    and contains some small fixes.

  • Netflow now supports the datadog-agent status command, providing
    configuration information. Any configuration errors encountered will be
    listed.

  • Emit database_instance tag with the value host/cdb. The goal is to show each database separately in the DBM entry page. Currently, the backend initializes database_instance to host.
    Also, the Agent will emit the new db_server tag because we have to initialize the host tag to host/cdb.

  • Improve obfuscator formatting. Prevent spaces after parentheses.
    Prevent spaces before # when # is a part of an identifier.

  • Emit query metrics with zero executions to capture long runners spanning over several sampling periods.

  • Impose a time limit on query metrics processing. After exceeding the default limit of 20s, the Agent stops emitting execution plans and fqt events.

  • Add oracle.inactive_seconds metric. Add tags with session attributes to oracle.process_pga* metrics.

  • Stop override peer.service with other attributes in OTel spans.

  • Process-Agent: Improved parsing performance of the '/proc/pid/stat' file (Linux only)

  • [snmp_listener] Enable collect_topology by default.

  • dbm: add SQL obfuscation options to give customer more control over how SQL is obfuscated and normalized.

    • RemoveSpaceBetweenParentheses - remove spaces between parentheses. This option is only valid when ObfuscationMode is obfuscate_and_normalize.
    • KeepNull` - disable obfuscating null values with ?. This option is only valid when ObfuscationModeis "obfuscate_only" orobfuscate_and_normalize``.
    • KeepBoolean - disable obfuscating boolean values with ?. This option is only valid when ObfuscationMode is obfuscate_only or obfuscate_and_normalize.
    • KeepPositionalParameter - disable obfuscating positional parameters with ?. This option is only valid when ObfuscationMode is obfuscate_only or obfuscate_and_normalize.
  • Add logic to support multiple tags created by a single label/annotaion.
    For example, add the following config to extract tags for chart_name and app_chart_name.
    podLabelsAsTags:
    chart_name: chart_name, app_chart_name
    Note: the format must be a comma-separated list of tags.

  • The logs collection pipeline has been through a refactor to support
    processing only the message content (instead of the whole raw message)
    in the journald and Windows events tailers.
    This feature is experimental and off by default since it changes how
    existing log_processing_rules behaves with journald and Windows events
    tailer.
    Note that it will be switched on by default in a future release of the Agent.
    A warning notifying about this is shown when the journald and Windows events
    tailers are used with some log_processing_rules.

  • The Datadog agent container image is now using Ubuntu 23.10 mantic
    as the base image.

  • The win32_event_log check now continuously collects and reports events instead of waiting for
    min_collection_interval to collect.
    min_collection_interval now controls how frequently the check attempts to reconnect
    when the event subscription is in an error state.

.. _Release Notes_7.50.0_Deprecation Notes:

Deprecation Notes

  • Installing the Agent on Windows Server versions lower than 2016 and client versions lower than 10 is now deprecated.

  • The timeout option for the win32_event_log check is no longer applicable and can be removed. If the option
    is set, the check logs a deprecation warning and ignores the option.

.. _Release Notes_7.50.0_Security Notes:

Security Notes

  • Fix CVE-2023-45283 and CVE-2023-45284

  • Update OpenSSL from 3.0.11 to 3.0.12.
    This addresses CVE-2023-5363.

.. _Release Notes_7.50.0_Bug Fixes:

Bug Fixes

  • On Windows, uninstalling the Agent should not fail if the Datadog Agent registry key is missing.

  • APM: OTLP: Only extract DD container tags from resource attributes. Previously, container tags were also extracted from span attributes.

  • APM: OTLP: Only add container tags in tag _dd.tags.container. Previously, container tags were also added as span tags.

  • Resolved an issue in the containerd collector where the SBOM collection did not correctly attach RepoTags and RepoDigests to the SBOM payload.

  • Add a workaround for a bug in a Windows API that can cause the Agent to
    crash when collecting forwarded events from the Windows Event Log.

  • Resolve the issue with hostname resolution in the kube_apiserver provider when the useHostNetwork setting is enabled.

  • Fix an issue that prevented process ID (PID) from being associated with containers in Live Container View when the Agent is deployed in AWS Fargate.

  • APM: Fixed trace-agent not forwarding errors from remote configuration and reporting them all as 500s

  • On Windows, the SE_DACL_AUTO_INHERITED flag is reset on %PROJECTLOCATION% during upgrades and uninstalls.

  • Fixes a bug in the Windows NPM driver where NPM displays byte overcounts.

  • For USM on Windows, fixes the problem where paths were being erroneously
    reported as truncated

  • Fixes journald log's Seek function to be set at the beginning or end upon initialization.

  • Fixed the cause of some crashes related to CPU instruction
    incompatibility happening under certain CPUs when making calls to
    the included libgmp library.

  • [kubelet] The Kubelet client no longer fails to initialize when the parameter kubelet_tls_verify is set to false with a misconfigured root certificate authority.

  • Fixes a bug where the process-agent process check command would fail to run
    when language detection was enabled.

  • Document query metrics metric_prefix parameter.

  • Set the tag dd.internal.resource:database_instance to host instead of host/cdb.

  • Switch to the new obfuscator where bugs such as getting an error when obfuscating @! and where comments on DMLs weren't being removed are fixed.

  • Fixes wrong values in Oracle query metrics data. Extreme cases had inflated statistics and missing statements. The affected were pure DML and PL/SQL statements.

  • Fix the bug that prevented Oracle DBM working properly on AWS RDS non-multitenant instances.

  • Fix an issue that caused the win32_event_log check to not stop running when the rate of incoming event
    records was higher than the timeout option. The timeout option is now deprecated.

  • The Windows Event Log tailer automatically recovers and is able to resume collecting
    events when a log provider is reinstalled, which sometimes happens during Windows updates.

.. _Release Notes_7.49.1:

v6.49.1

================

.. _Release Notes_7.49.1_Prelude:

Prelude

Release on: 2023-11-15

  • Please refer to the 7.49.1 tag on integrations-core <https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7491>_ for the list of changes on the Core Checks

.. _Release Notes_7.49.1_Bug Fixes:

Bug Fixes

  • CWS: add arch field into agent context included in CWS events.

  • APM: Fix a deadlock issue which can prevent the trace-agent from shutting down.

  • CWS: Fix the broken lineage check for process activity in CWS.

  • APM: fix a regression in the Trace Agent that caused container tagging
    with UDS and cgroup v2 to fail.

.. _Release Notes_7.49.0:

v6.49.0

================

.. _Release Notes_7.49.0_Prelude:

Prelude

Release on: 2023-11-02

  • Refer to the 7.49.0 tag on integrations-core <https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7490>_ for the list of changes on the core checks

.. _Release Notes_7.49.0_New Features:

New Features

  • Add --use-unconnected-udp-socket flag to agent snmp walk command.

  • Add support for image pull metrics in the containerd check.

  • Add kubelet stats.summary check (kubernetes_core.kubelet.*) to the Agent's core checks to replace the old kubernetes.kubelet check generated from Python.

  • APM: [BETA] Adds peer_tags configuration to allow for more tags in APM stats that
    can add granularity and clarity to a peer.service. To set this config, use
    DD_APM_PEER_TAGs='["aws.s3.bucket", "db.instance", ...] or
    apm_config.peer_tags: ["aws.s3.bucket", "db.instance", ...] in datadog.yaml.
    Please note that DD_APM_PEER_SERVICE_AGGREGATION or apm_config.peer_service_aggregation must also be set to true.

  • Introduces new Windows crash detection check. Upon initial check
    run, sends a DataDog event if it is determined that the machine has
    rebooted due to a system crash.

  • Install the Aerospike integration on ARM platforms for Python 3

  • CWS: Detect patterns in processes and files paths to improve
    accuracy of anomaly detections.

  • Add Dynamic Instrumentation diagnostics proxy endpoint to the trace-agent http server.

    At present, diagnostics are forwarded through the debugger endpoint on the trace-agent server to logs.
    Since Dynamic Instrumentation also allows adding dynamic metrics and dynamic spans, we want to remove the
    dependency on logs for diagnostics - the new endpoint uploads diagnostic messages on a dedicated track.

  • Adds a configurable jmxfetch telemetry check that collects additional data on the
    running jmxfetch JVM in addition to data about the JVMs jmxfetch is monitoring.
    The check can be configured by enabling the jmx_telemetry_enabled option in the Agent.

  • [NDM] Collect diagnoses from SNMP devices.

  • Adding support for Oracle 12.2.

  • Add support for Oracle 18c.

  • CWS now computes hashes for all the files involved in the generation of a Security Profile and an Anomaly Detection Event

  • [Beta] Cluster agent supports APM Single Step Instrumentation for Kubernetes.
    Can be enabled in Kubernetes cluster by setting ``DD_APM_INSTRUMENTATION_ENABLED=true`.
    Single Step Instrumentation can be turned on in specific namespaces using
    environment variable DD_APM_INSTRUMENTATION_ENABLED_NAMESPACES.
    Single Step Instrumentation can be turned off in specific namespaces using
    environment variable DD_APM_INSTRUMENTATION_DISABLED_NAMESPACES.

.. _Release Notes_7.49.0_Enhancement Notes:

Enhancement Notes

  • Moving the Orchestrator Explorer pod check from the process agent to the core agent. In the following release we will be removing the process agent check and defaulting to the core agent check. If you want to migrate ahead of time you can set orchestrator_explorer.run_on_node_agent = true in your configuration.

  • Add new GPU metrics in the KSM Core check:

    • kubernetes_state.node.gpu_capacity tagged by node, resource, unit and mig_profile.
    • kubernetes_state.node.gpu_allocatable tagged by node, resource, unit and mig_profile.
    • kubernetes_state.container.gpu_limit tagged by kube_namespace, pod_name, kube_container_name, node, resource, unit and mig_profile.
  • Tag container entity with image_id tag.

  • max_message_size_bytes can now be configured in logs_config. This allows the default message
    content limit of 256,000 bytes to be increased up to 1MB. If a log line is larger than this byte limit,
    the overflow bytes will be truncated.

  • APM: Add regex support for filtering tags by apm_config.filter_tags_regex or environment
    variables DD_APM_FILTER_TAGS_REGEX_REQUIRE and DD_APM_FILTER_TAGS_REGEX_REJECT.

  • Agents are now built with Go 1.20.10.

  • CWS: Support fentry/fexit eBPF probes which provide lower overhead than
    kprobe/kretprobes (currently disabled by default and supported only
    on Linux kernel 5.10 and later).

  • CWS: Improved username resolution in containers and handle their creation
    and deletion at runtime.

  • CWS: Apply policy rules on processes already present at startup.

  • CWS: Reduce memory usage of BTF symbols.

  • Remote Configuration for Cloud Workload Security detection rules is enabled if Remote Configuration is globally enabled for the Datadog Agent.
    Remote Configuration for Cloud Workload Security can be disabled while Remote Configuration is globally enabled by setting the runtime_security_config.remote_configuration.enabled value to false.
    Remote Configuration for Cloud Workload Security cannot be enabled if Remote Configuration is not globally enabled.

  • Add gce-container-declaration to default GCE excluded host tags. See exclude_gce_tags configuration settings for more.

  • Add metrics for the workloadmeta extractor to process-agent status output

  • Add a heartbeat mechanism for SBOM collection to avoid having to
    send the whole SBOM if it has not changed since the last computation.
    The default interval for the host SBOM has changed from 24 hours to 1 hour.

  • Prefix every entry in the log file with details about the database server and port to distinguish log entries originating from different databases.

  • JMXFetch internal telemetry is now included in the agent status output when
    the verbose flag is included in the request.

  • Sensitive information is now scrubbed from pod annotations.

  • The image_id tag no longer includes the docker-pullable:// prefix when using Kubernetes with Docker as runtime.

  • Improve SQL text collection for self-managed installations. The Agent selects text from V$SQL instead of V$SQLSTATS. If it isn't possible to query the text, the Agent tries to identify the context, such as parsing or closing cursor, and put it in the SQL text.

  • Improve the Oracle check example configuration file.

  • Collect Oracle execution plans by default.

  • Add global custom queries to Oracle checks.

  • Add connection refused handling.

  • Add the hosting-type tag, which can have one of the following values: self-managed, RDS, or OCI.

  • Add a hidden parameter to log unobfuscated execution plan information.

  • Adding real_hostname tag.

  • Add sql_id and plan_hash_value to obfuscation error message.

  • Add Oracle pga_over_allocation_count_metric.

  • Add information about missing privileges with the link to the grant commands.

  • Add TCPS configuration to conf.yaml.example.

  • The container check reports two new metrics:

    • container.memory.page_faults
    • container.memory.major_page_faults

    to report the page fault counters per container.

  • prometheus_scrape: Adds support for multiple OpenMetrics V2 features in the prometheus_scrape.checks[].configurations[] items:

  • Improved the SBOM check function to now communicate the status of scans and any potential errors directly
    to DataDog for more streamlined error management and resolution.

  • Separate init-containers from containers in the KubernetesPod structure of workloadmeta.

  • Improve marshalling performance in the system-probe -> process-agent path. This improves memory footprint when NPM and/or USM are enabled.

  • Raise the default logs_config.open_files_limit to 500 on
    Windows.

.. _Release Notes_7.49.0_Deprecation Notes:

Deprecation Notes

  • service_monitoring_config.enable_go_tls_support is deprecated and replaced by service_monitoring_config.tls.go.enabled.
    network_config.enable_https_monitoring is deprecated and replaced by service_monitoring_config.tls.native.enabled.

.. _Release Notes_7.49.0_Security Notes:

Security Notes

  • APM: The Agent now obfuscates the entire Memcached command by
    default. You can revert to the previous behavior where only the values
    were obfuscated by setting DD_APM_OBFUSCATION_MEMCACHED_KEEP_COMMAND=true
    or apm_config.obfuscation.memcached.keep_command: true in datadog.yaml.

  • Fix CVE-2023-39325

  • Bump golang.org/x/net to v0.17.0 to fix CVE-2023-44487.

.. _Release Notes_7.49.0_Bug Fixes:

Bug Fixes

  • Fix Agent Flare not including Trace Agent's expvar output.

  • Fixes a panic that occurs when the Trace Agent receives an OTLP payload during shutdown

  • Fixes a crash upon receiving an OTLP Exponential Histogram with no buckets.

  • CWS: Scope network context to DNS events only as it may not be available
    to all events.

  • CWS: Fix a bug that caused security profiles of already running workloads
    to be empty.

  • The docker.cpu.shares metric emitted by the Docker check now reports the correct number of CPU shares when running on cgroups v2.

  • Fixes a critical data race in workloadmeta that was causing issues when a subscriber attempted to unsubscribe while events were being handled in another goroutine.

  • Fix misnamed metric in the trace-agent.

  • Fixed a problem that caused the Agent to miss some image labels when using
    containerd as the container runtime.

  • Fix config conflict preventing logs_config.use_podman_logs from working

  • The scubbing logic for configurations now scrubs YAML lists. This fixes flare_stripped_keys not working on YAML
    list.

  • Fixed an issue in the SBOM check when using Kubernetes with Docker as runtime. Some images used by containers were incorrectly marked as unused.

  • Fix Oracle SQL text truncation in query samples.

  • Make the custom queries feature available for non-DBM users.

  • Fix wrong tags generated by custom queries.

  • Eliminate duplicate upper case cdb and pdb tags.

  • Fix panic: runtime error: invalid memory address or nil pointer dereference in StatementMetrics by improving cache handling.

  • Fix truncation of SQL text for large statements.

  • Fix the failed to query v$pdbs, which was appearing for RDS databases.

  • Bug fix for ORA-06502: PL/SQL: numeric or value error: character string buffer too small. This error would occasionally appear during activity sampling.

  • Adjust doc links to grant privilege commands for multitenant and non-CDB architecture.

  • Workaround for the PGA memory leak.

  • Improve recovering from lost connections in custom queries.

  • Emit zero value for oracle.pga_over_allocation metric.

  • APM: Parse SQL Server query with single dollar identifier $action.

.. _Release Notes_7.49.0_Other Notes:

Other Notes

  • JMXFetch upgraded to 0.48.0 <https://github.com/DataDog/jmxfetch/releases/tag/0.48.0>_

.. _Release Notes_7.48.1:

v6.48.1

================

.. _Release Notes_7.48.1_Prelude:

Prelude

Release on: 2023-10-17

  • Please refer to the 7.48.1 tag on integrations-core <https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7481>_ for the list of changes on the Core Checks

.. _Release Notes_7.48.1_Upgrade Notes:

Upgrade Notes

  • Upgraded Python 3.9 to Python 3.9.18

.. _Release Notes_7.48.1_Security Notes:

Security Notes

.. _Release Notes_7.48.1_Bug Fixes:

Bug Fixes

  • On some slow drives, when the Agent shuts down suddenly the Logs Agent registry file can become corrupt.
    This means that when the Agent starts again the registry file can't be read and therefore the Logs Agent reads logs from the beginning again.
    With this update, the Agent now attempts to update the registry file atomically to reduce the chances of a corrupted file.

.. _Release Notes_7.48.0:

v6.48.0

================

.. _Release Notes_7.48.0_Prelude:

Prelude

Release on: 2023-10-10

  • Please refer to the 7.48.0 tag on integrations-core <https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7480>_ for the list of changes on the Core Checks

.. _Release Notes_7.48.0_Upgrade Notes:

Upgrade Notes

  • The EventIDs logged to the Windows Application Event Log by the Agent services
    have been normalized and now have the same meaning across Agent services.
    Some EventIDs have changed and the rendered message may be incorrect
    if you view an Event Log from a host that uses a different version of the Agent
    than the host that created the Event Log. To ensure you see the correct message,
    choose "Display information for these languages" when exporting the Event
    Log from the host. This does not affect Event Logs collected by the Datadog Agent's
    Windows Event Log integration, which renders the event messages on the originating host.
    The EventIDs and messages used by the Agent services can be viewed in
    pkg/util/winutil/messagestrings/messagestrings.mc.

  • datadog-connectivity and metadata-availability subcommands
    do not exist anymore and their diagnoses are reported in a more
    general and structured way.

    Diagnostics previously reported via datadog-connectivity
    subcommand will be reported now as part of
    connectivity-datadog-core-endpointssuite. Correspondingly,
    diagnostics previously reported via metadata-availability
    subcommand will be reported now as part of
    connectivity-datadog-autodiscovery suite.

  • Streamlined settings by renaming workloadmeta.remote_process_collector.enabled and process_config.language_detection.enabled to language_detection.enabled.

  • The command line arguments to the Datadog Agent Trace Agent trace-agent
    have changed from single-dash arguments to double-dash arguments.
    For example, -config must now be provided as --config.
    Additionally, subcommands have been added, these may be listed with the
    --help switch. For backward-compatibility reasons the old CLI arguments
    will still work in the foreseeable future but may be removed in future versions.

.. _Release Notes_7.48.0_New Features:

New Features

  • Added the kubernetes_state.pod.tolerations metric to the KSM core check

  • Grab, base64 decode, and attach trace context from message attributes passed through SNS->SQS->Lambda

  • Add kubelet healthz check (check_run.kubernetes_core.kubelet.check) to the Agent's core checks to replace the old kubernetes.kubelet.check generated from Python.

  • Tag the aws.lambda span generated by the datadog-extension with a language tag based on runtime information in dotnet and java cases

  • Extended the "agent diagnose" CLI command to allow the easy addition of new
    diagnostics for diverse and dispersed Agent code.

  • Add support for the otlp_config.metrics.sums.initial_cumulative_monotonic_value setting.

  • [BETA] Adds Golang language and version detection through the system probe. This beta feature can be enabled by setting
    system_probe_config.language_detection.enabled to true in your system-probe.yaml.

  • Add new kubelet corecheck, which will eventually replace the existing kubelet check.

  • Add custom queries to Oracle monitoring.

  • Adding new configuration setting otlp_config.logs.enabled to enable/disable logs support in the OTLP ingest endpoint.

  • Add logsagentexporter, which is used in OTLP agent to translate ingested logs and forward them to logs-agent

  • Flush in-flight requests and pending retries to disk at shutdown when disk-based buffering of metrics is enabled
    (for example, when forwarder_storage_max_size_in_bytes is set).

  • Added a new collector in the process agent in workloadmeta.
    This collector allows for collecting processes when the process_config.process_collection.enabled is false
    and language_detection.enabled is true.
    The interval at which this collector collects processes can be adjusted with the setting
    workloadmeta.local_process_collector.collection_interval.

  • Tag lambda cold starts and proactive initializations on the root aws.lambda span

  • APM - This change improves the acceptance and queueing strategy for trace
    payloads sent to the Trace Agent. These changes create a system of
    backpressure in the Trace Agent, causing it to reject payloads when it
    cannot keep up with the rate of traffic, rather than buffering and causing
    OOM issues.

    This change has been shown to increase overall throughput in the Trace Agent
    while decreasing peak resource usage. Existing configurations for CPU and
    memory work at least as well, and often better, with these changes compared to previous Agent versions. This means users do not have to adjust
    their configuration to take advantage of these changes, and they do not
    experience performance degredation as a result of upgrading.

.. _Release Notes_7.48.0_Enhancement Notes:

Enhancement Notes

  • When jmx_use_container_support is enabled you can use jmx_max_ram_percentage to set a maximum JVM heap size based off a percentage of the total container memory.

  • SNMP profile detection now updates the SNMP profile for a given IP if the device at that IP changes.

  • Add Process Language Detection Enabled in the output of the Agent Status command under the Process Agent section.

  • Improve agent diagnose command to be executed in context of
    running Agent process.

  • Agents are now built with Go 1.20.7. This version of Golang fixes CVE-2023-29409.

  • Added the container.memory.usage.peak metric to the container check. It shows the maximum memory usage recorded since the container started.

  • Unified agent diagnose CLI command by removing all,
    datadog-connectivity, and metadata-availability subcommands.
    These separate subcommands became one of the diagnose suites. The
    all subcommand became unnecessary.

  • APM: Improved performance and memory consumption in obfuscation, both halved on average.

  • Agents are now built with Go 1.20.8.

  • The processor frequency sent in metadata is now a decimal value on Darwin and Windows,
    as it already is on Linux. The precision of the value is increased on Darwin.

  • CPU metadata which failed to be collected is no longer sent as empty values on Windows.

  • Platform metadata which failed to be collected is no longer sent as empty values on Windows.

  • Filesystem metadata is now collected without running the df binary on Unix.

  • Adds language detection support for JRuby, which is detected as Ruby.

  • Add the oracle.can_connect metric.

  • Add duration to the plan payload.

  • Increasing the collection interval for all the checks except for activity samples from 10s to 60s.

  • Collect the number of CPUs and physical memory.

  • Improve Oracle query metrics algorithm and the fetching time for execution plans.

  • OTLP ingest pipeline panics no longer stop the Datadog Agent and instead
    only shutdown this pipeline. The panic is now available in the OTLP status section.

  • During the process check, collect the command name from /proc/[pid]/comm. This
    allows more accurate language detection of processes.

  • Change how SNMP trap variables with bit enumerations are resolved to hexadecimal strings prefixed with "0x" (previously base64 encoded strings).

  • The Datadog agent container image is now using Ubuntu 23.04 lunar
    as the base image.

  • Upgraded JMXFetch to 0.47.10 <https://github.com/DataDog/jmxfetch/releases/0.47.10>.
    This version improves how JMXFetch communicates with the Agent, and fixes a race condition
    where an exception is thrown if the Agent hasn't finished initializing before JMXFetch starts to shut down.

  • Added collector.worker_utilization to the telemetry. This metric represents the amount of time that a runner worker has been running checks.

.. _Release Notes_7.48.0_Deprecation Notes:

Deprecation Notes

  • The command line arguments to the Datadog Agent Trace Agent trace-agent
    have changed from single-dash arguments to double-dash arguments.
    For example, -config must now be provided as --config. For backward-
    compatibility reasons the old CLI arguments will still work in the foreseeable
    future but may be removed in future versions.

.. _Release Notes_7.48.0_Security Notes:

Security Notes

  • APM: In order to improve the default customer experience regarding
    sensitive data, the Agent now obfuscates database statements within
    span metadata by default. This includes MongoDB queries,
    ElasticSearch request bodies, and raw commands from Redis and
    MemCached. Previously, this setting was off by default.
    This update could have performance implications, or obfuscate data that
    is not sensitive, and can be disabled o

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.41.0 Update datadog/agent Docker tag to v6.41.0 Dec 17, 2022
@renovate renovate bot changed the title Update datadog/agent Docker tag to v6.41.0 chore(deps): update datadog/agent docker tag to v6.41.0 Dec 17, 2022
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from ad4875a to a7311dd Compare December 21, 2022 17:30
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.41.0 chore(deps): update datadog/agent docker tag to v6.41.1 Dec 21, 2022
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.41.1 chore(deps): update datadog/agent docker tag to v6.41.1 - autoclosed Jan 20, 2023
@renovate renovate bot closed this Jan 20, 2023
@renovate renovate bot deleted the renovate/datadog-agent-6.x branch January 20, 2023 14:51
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.41.1 - autoclosed chore(deps): update datadog/agent docker tag to v6.41.1 Jan 20, 2023
@renovate renovate bot reopened this Jan 20, 2023
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.41.1 chore(deps): update datadog/agent docker tag to v6.42.0 Jan 23, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from a7311dd to b02f29d Compare January 23, 2023 16:29
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from b02f29d to fe3d889 Compare February 3, 2023 01:46
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.42.0 chore(deps): update datadog/agent docker tag to v6.42.1 Feb 3, 2023
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.42.1 chore(deps): update datadog/agent docker tag to v6.42.2 Feb 17, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from fe3d889 to 0c857cb Compare February 17, 2023 00:22
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.42.2 chore(deps): update datadog/agent docker tag to v6.43.0 Feb 23, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from 0c857cb to 6bbfec0 Compare February 23, 2023 12:36
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.43.0 chore(deps): update datadog/agent docker tag to v6.43.1 Mar 7, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from 6bbfec0 to aac92ad Compare March 7, 2023 20:39
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.43.1 chore(deps): update datadog/agent docker tag to v6.43.2 Apr 21, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from aac92ad to 1f065d7 Compare April 21, 2023 06:26
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.43.2 chore(deps): update datadog/agent docker tag to v6.44.0 Apr 27, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from 1f065d7 to dbd8d5d Compare April 27, 2023 16:05
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.44.0 chore(deps): update datadog/agent docker tag to v6.44.1 May 31, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from dbd8d5d to 8830f71 Compare May 31, 2023 01:59
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from 8830f71 to 9656444 Compare June 7, 2023 05:45
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.44.1 chore(deps): update datadog/agent docker tag to v6.45.0 Jun 7, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from 9656444 to 9607097 Compare June 28, 2023 23:59
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.45.0 chore(deps): update datadog/agent docker tag to v6.45.1 Jun 29, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from 9607097 to 538014d Compare July 11, 2023 23:39
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.46.0 chore(deps): update datadog/agent docker tag to v6.47.0 Sep 1, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from 2d637d1 to 205f4d2 Compare September 22, 2023 05:59
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.47.0 chore(deps): update datadog/agent docker tag to v6.47.1 Sep 22, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from 205f4d2 to eaad8e6 Compare October 11, 2023 02:41
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.47.1 chore(deps): update datadog/agent docker tag to v6.48.0 Oct 11, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from eaad8e6 to 370be05 Compare October 18, 2023 05:49
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.48.0 chore(deps): update datadog/agent docker tag to v6.48.1 Oct 18, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from 370be05 to f0fb94b Compare November 3, 2023 02:40
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.48.1 chore(deps): update datadog/agent docker tag to v6.49.0 Nov 3, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from f0fb94b to 50e827e Compare November 17, 2023 05:59
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.49.0 chore(deps): update datadog/agent docker tag to v6.49.1 Nov 17, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from 50e827e to b5aa7c0 Compare December 20, 2023 08:14
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.49.1 chore(deps): update datadog/agent docker tag to v6.50.0 Dec 20, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from b5aa7c0 to 2660d50 Compare December 22, 2023 08:11
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.50.0 chore(deps): update datadog/agent docker tag to v6.50.1 Dec 22, 2023
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from 2660d50 to a6053ea Compare January 5, 2024 05:47
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.50.1 chore(deps): update datadog/agent docker tag to v6.50.2 Jan 5, 2024
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from a6053ea to abd1a64 Compare January 12, 2024 14:55
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.50.2 chore(deps): update datadog/agent docker tag to v6.50.3 Jan 12, 2024
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from abd1a64 to 76f8cee Compare February 21, 2024 05:42
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.50.3 chore(deps): update datadog/agent docker tag to v6.51.0 Feb 21, 2024
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from 76f8cee to 81d72be Compare February 29, 2024 20:59
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.51.0 chore(deps): update datadog/agent docker tag to v6.51.1 Feb 29, 2024
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from 81d72be to e15d495 Compare March 23, 2024 02:51
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.51.1 chore(deps): update datadog/agent docker tag to v6.52.0 Mar 23, 2024
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from e15d495 to e801dc6 Compare April 5, 2024 23:56
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.52.0 chore(deps): update datadog/agent docker tag to v6.52.1 Apr 5, 2024
@renovate renovate bot force-pushed the renovate/datadog-agent-6.x branch from e801dc6 to aa37cda Compare May 1, 2024 11:20
@renovate renovate bot changed the title chore(deps): update datadog/agent docker tag to v6.52.1 chore(deps): update datadog/agent docker tag to v6.53.0 May 1, 2024
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

Successfully merging this pull request may close these issues.

0 participants