Merge branch 'master' into palo-alto-cortex-xdr-v1.0.0

.github/CODEOWNERS

@@ -243,6 +243,11 @@ datadog_checks_base/datadog_checks/base/checks/windows/              @DataDog/wi
 /cisco_duo/*.md                                                      @DataDog/saas-integrations @DataDog/documentation
 /cisco_duo/manifest.json                                             @DataDog/saas-integrations @DataDog/documentation
 
+/cisco_secure_endpoint/                                              @DataDog/saas-integrations
+/cisco_secure_endpoint/*.md                                          @DataDog/saas-integrations @DataDog/documentation
+/cisco_secure_endpoint/manifest.json                                 @DataDog/saas-integrations @DataDog/documentation
+/cisco_secure_endpoint/assets/logs/                                  @DataDog/saas-integrations @DataDog/documentation @DataDog/logs-backend
+
 /mimecast/                                                          @DataDog/saas-integrations
 /mimecast/*.md                                                      @DataDog/saas-integrations @DataDog/documentation
 /mimecast/manifest.json                                             @DataDog/saas-integrations @DataDog/documentation
@@ -253,11 +258,17 @@ datadog_checks_base/datadog_checks/base/checks/windows/              @DataDog/wi
 /palo_alto_cortex_xdr/manifest.json                                  @DataDog/saas-integrations @DataDog/documentation
 /palo_alto_cortex_xdr/assets/logs/                                   @DataDog/saas-integrations @DataDog/documentation @DataDog/logs-backend
 
+/sophos_central_cloud/                                               @DataDog/saas-integrations
+/sophos_central_cloud/*.md                                           @DataDog/saas-integrations @DataDog/documentation
+/sophos_central_cloud/manifest.json                                  @DataDog/saas-integrations @DataDog/documentation
+/sophos_central_cloud/assets/logs/                                   @DataDog/saas-integrations @DataDog/documentation @DataDog/logs-backend
+
 /ping_one/                                                          @DataDog/saas-integrations
 /ping_one/*.md                                                      @DataDog/saas-integrations @DataDog/documentation
 /ping_one/manifest.json                                             @DataDog/saas-integrations @DataDog/documentation
 /ping_one/assets/logs/                                              @DataDog/saas-integrations @DataDog/documentation @DataDog/logs-backend
 
+
 # To keep Security up-to-date with changes to the signing tool.
 /datadog_checks_dev/datadog_checks/dev/tooling/signing.py             @DataDog/agent-integrations
 # As well as the secure downloader.

.github/workflows/config/labeler.yml

@@ -99,6 +99,8 @@ integration/cisco_duo:
 - cisco_duo/**/*
 integration/cisco_sdwan:
 - cisco_sdwan/**/*
+integration/cisco_secure_endpoint:
+- cisco_secure_endpoint/**/*
 integration/cisco_secure_firewall:
 - cisco_secure_firewall/**/*
 integration/cisco_umbrella_dns:
@@ -433,6 +435,8 @@ integration/solr:
 - solr/**/*
 integration/sonarqube:
 - sonarqube/**/*
+integration/sophos_central_cloud:
+- sophos_central_cloud/**/*
 integration/spark:
 - spark/**/*
 integration/sqlserver:

aerospike/README.md

@@ -63,15 +63,30 @@ To configure this check for an Agent running on a host:
 
 #### Containerized
 
-For containerized environments, see the [Autodiscovery Integration Templates][5] for guidance on applying the parameters below.
+For containerized environments, see [Configure integrations with Autodiscovery on Kubernetes][5] or [Configure integrations with Autodiscovery on Docker][14] for guidance on applying the parameters below. See the [sample aerospike.d/conf.yaml][3] for all available configuration options.
 
 ##### Metric collection
 
 | Parameter            | Value                                |
 | -------------------- | ------------------------------------ |
 | `<INTEGRATION_NAME>` | `aerospike`                          |
 | `<INIT_CONFIG>`      | blank or `{}`                        |
-| `<INSTANCE_CONFIG>`  | `{"openmetrics_endpoint": "http://%%host%%:9145/metrics"}` |
+| `<INSTANCES_CONFIG>`  | `{"openmetrics_endpoint": "http://%%host%%:9145/metrics"}` |
+
+**Example**
+
+Apply the following annotation to your pod, where `<CONTAINER_IDENTIFIER>` is the Aerospike container image name or a [custom identifier][15]:
+
+```
+ad.datadoghq.com/<CONTAINER_IDENTIFIER>.checks: |
+  {
+    "aerospike": {
+      "init_config": {},
+      "instances": [{"openmetrics_endpoint": "http://%%host%%:9145/metrics"}]
+    }
+  } 
+```
+
 
 ##### Log collection
 
@@ -83,6 +98,20 @@ Collecting logs is disabled by default in the Datadog Agent. To enable it, see [
 | -------------- | --------------------------------------------------- |
 | `<LOG_CONFIG>` | `{"source": "aerospike", "service": "<SERVICE_NAME>"}` |
 
+**Example**
+
+Apply the following annotation to your pod, where `<CONTAINER_IDENTIFIER>` is the Aerospike container image name or a [custom identifier][15]:
+
+```
+ad.datadoghq.com/<CONTAINER_IDENTIFIER>.logs: |
+  [
+    {
+      "type": "file",
+      "path": "/var/log/aerospike/aerospike.log",
+      "source": "aerospike"
+    } 
+  ]
+```
 <!-- xxz tab xxx -->
 <!-- xxz tabs xxx -->
 
@@ -113,7 +142,7 @@ Need help? Contact [Datadog support][9].
 [2]: https://app.datadoghq.com/account/settings/agent/latest
 [3]: https://github.com/DataDog/integrations-core/blob/master/aerospike/datadog_checks/aerospike/data/conf.yaml.example
 [4]: https://docs.datadoghq.com/agent/guide/agent-commands/#start-stop-and-restart-the-agent
-[5]: https://docs.datadoghq.com/agent/kubernetes/integrations/
+[5]: https://docs.datadoghq.com/containers/kubernetes/integrations/
 [6]: https://docs.datadoghq.com/agent/kubernetes/log/
 [7]: https://docs.datadoghq.com/agent/guide/agent-commands/#agent-status-and-information
 [8]: https://github.com/DataDog/integrations-core/blob/master/aerospike/metadata.csv
@@ -122,3 +151,5 @@ Need help? Contact [Datadog support][9].
 [11]: https://docs.aerospike.com/monitorstack/new/installing-components
 [12]: https://docs.datadoghq.com/integrations/openmetrics/
 [13]: https://github.com/DataDog/integrations-core/blob/7.36.x/aerospike/datadog_checks/aerospike/data/conf.yaml.example
+[14]: https://docs.datadoghq.com/containers/docker/integrations/
+[15]: https://docs.datadoghq.com/containers/guide/ad_identifiers/

argo_rollouts/README.md

@@ -12,13 +12,13 @@ Follow the instructions below to install and configure this check for an Agent r
 
 Starting from Agent release 7.53.0, the Argo Rollouts check is included in the [Datadog Agent][2] package. No additional installation is needed in your environment.
 
-This check uses [OpenMetrics][5] to collect metrics from the OpenMetrics endpoint that Karpenter exposes, which requires Python 3.
+This check uses [OpenMetrics][5] to collect metrics from the OpenMetrics endpoint that Argo Rollouts exposes, which requires Python 3.
 
 ### Configuration
 
 The Argo Rollouts controller has Prometheus-formatted metrics readily available at `/metrics` on port `8090`. For the Agent to start collecting metrics, the Argo Rollouts pods need to be annotated. For more information about annotations, refer to the [Autodiscovery Integration Templates][3] for guidance. You can find additional configuration options by reviewing the [sample argo_rollouts.d/conf.yaml][4].
 
-**Note**: The listed metrics can only be collected if they are available. Some metrics are generated only when certain actions are performed. For example, the `argo_rollout.info.replicas.updated` metric is exposed only after a replica is updated.
+**Note**: The listed metrics can only be collected if they are available. Some metrics are generated only when certain actions are performed. For example, the `argo_rollouts.info.replicas.updated` metric is exposed only after a replica is updated.
 
 The only parameter required for configuring the Argo Rollouts check is:
 - `openmetrics_endpoint`: This parameter should be set to the location where the Prometheus-formatted metrics are exposed. The default port is `8090`. In containerized environments, `%%host%%` should be used for [host autodetection][3]. 
@@ -82,6 +82,11 @@ See [service_checks.json][8] for a list of service checks provided by this integ
 
 Need help? Contact [Datadog support][9].
 
+## Further Reading
+
+Additional helpful documentation, links, and articles:
+
+- [Monitoring the health and performance of your container-native CI/CD pipelines][11]
 
 [1]: https://argoproj.github.io/rollouts/
 [2]: https://app.datadoghq.com/account/settings/agent/latest
@@ -93,3 +98,4 @@ Need help? Contact [Datadog support][9].
 [8]: https://github.com/DataDog/integrations-core/blob/master/argo_rollouts/assets/service_checks.json
 [9]: https://docs.datadoghq.com/help/
 [10]: https://docs.datadoghq.com/agent/kubernetes/log/
+[11]: https://www.datadoghq.com/blog/container-native-ci-cd-integrations/

argo_workflows/README.md

@@ -80,6 +80,11 @@ See [service_checks.json][8] for a list of service checks provided by this integ
 
 Need help? Contact [Datadog support][9].
 
+## Further Reading
+
+Additional helpful documentation, links, and articles:
+
+- [Monitoring the health and performance of your container-native CI/CD pipelines][12]
 
 [1]: https://argo-workflows.readthedocs.io/en/stable/
 [2]: https://app.datadoghq.com/account/settings/agent/latest
@@ -92,3 +97,4 @@ Need help? Contact [Datadog support][9].
 [9]: https://docs.datadoghq.com/help/
 [10]: https://docs.datadoghq.com/agent/kubernetes/log/
 [11]: https://argo-workflows.readthedocs.io/en/stable/metrics/
+[12]: https://www.datadoghq.com/blog/container-native-ci-cd-integrations/

argocd/README.md

@@ -181,6 +181,12 @@ See [service_checks.json][8] for a list of service checks provided by this integ
 
 Need help? Contact [Datadog support][9].
 
+## Further Reading
+
+Additional helpful documentation, links, and articles:
+
+- [Monitoring the health and performance of your container-native CI/CD pipelines][16]
+
 
 [1]: https://argo-cd.readthedocs.io/en/stable/
 [2]: https://app.datadoghq.com/account/settings/agent/latest
@@ -197,4 +203,5 @@ Need help? Contact [Datadog support][9].
 [13]: https://github.com/DataDog/integrations-core/blob/7.45.x/argocd/datadog_checks/argocd/data/conf.yaml.example#L164-L166
 [14]: https://argo-cd.readthedocs.io/en/stable/operator-manual/metrics/#exposing-application-labels-as-prometheus-metrics
 [15]: https://github.com/DataDog/integrations-core/blob/master/argocd/datadog_checks/argocd/data/conf.yaml.example#L45-L72
+[16]: https://www.datadoghq.com/blog/container-native-ci-cd-integrations/
 

cisco_secure_endpoint/CHANGELOG.md

@@ -0,0 +1,7 @@
+# CHANGELOG - cisco_secure_endpoint
+
+## 1.0.0 / 2024-06-17
+
+***Added***:
+
+* Initial Release

cisco_secure_endpoint/README.md

@@ -0,0 +1,42 @@
+# Agent Check: cisco_secure_endpoint
+
+## Overview
+
+This check monitors [Cisco Secure Endpoint][1].
+
+## Setup
+
+### Installation
+
+The Cisco Secure Endpoint check is included in the [Datadog Agent][2] package.
+No additional installation is needed on your server.
+
+### Configuration
+
+1. <List of steps to configure this integration>
+
+### Validation
+
+<Steps to validate integration is functioning as expected>
+
+## Data Collected
+
+### Metrics
+
+The Cisco Secure Endpoint integration does not include any metrics.
+
+### Service Checks
+
+The Cisco Secure Endpoint integration does not include any service checks.
+
+### Events
+
+The Cisco Secure Endpoint integration does not include any events.
+
+## Troubleshooting
+
+Need help? Contact [Datadog support][3].
+
+[1]: **LINK_TO_INTEGRATION_SITE**
+[2]: https://app.datadoghq.com/account/settings#agent
+[3]: https://docs.datadoghq.com/help/

cisco_secure_endpoint/assets/service_checks.json

@@ -0,0 +1 @@
+[]

cisco_secure_endpoint/manifest.json

@@ -0,0 +1,40 @@
+{
+    "manifest_version": "2.0.0",
+    "app_uuid": "9636c2eb-34f6-4aa4-a236-c39e47b21c79",
+    "app_id": "cisco-secure-endpoint",
+    "display_on_public_website": false,
+    "tile": {
+        "overview": "README.md#Overview",
+        "configuration": "README.md#Setup",
+        "support": "README.md#Support",
+        "changelog": "CHANGELOG.md",
+        "description": "Gain insights into Cisco Secure Endpoint logs",
+        "title": "cisco-secure-endpoint",
+        "media": [],
+        "classifier_tags": [
+            "Category::Log Collection",
+            "Category::Security",
+            "Submitted Data Type::Logs"
+        ]
+    },
+    "assets": {
+        "integration": {
+            "auto_install": false,
+            "source_type_id": 18601889,
+            "source_type_name": "Cisco Secure Endpoint",
+            "events": {
+                "creates_events": false
+            },
+            "service_checks": {
+                "metadata_path": "assets/service_checks.json"
+            }
+        }
+    },
+    "author": {
+        "support_email": "help@datadoghq.com",
+        "name": "Datadog",
+        "homepage": "https://www.datadoghq.com",
+        "sales_email": "info@datadoghq.com"
+    },
+    "oauth": {}
+}

ecs_fargate/README.md

@@ -297,7 +297,7 @@ CloudFormation example (YAML):
               Value: "{\"com.docker.compose.service\":\"service_name\"}"
 ```
 
-**Note**: You should not use `DD_HOSTNAME` since there is no concept of a host to the user in Fargate. `DD_TAGS` is traditionally used to assign host tags, but as of Datadog Agent version 6.13.0 you can also use the environment variable to set global tags on your integration metrics.
+**Note**: You should not use `DD_HOSTNAME` since there is no concept of a host to the user in Fargate. Using this tag can cause your tasks to appear as APM Hosts in the Infrastructure list, potentially impacting your billing. Instead, `DD_TAGS` is traditionally used to assign host tags. As of Datadog Agent version 6.13.0, you can also use the `DD_TAGS` environment variable to set global tags on your integration metrics.
 
 ### Crawler-based metrics
 

fluxcd/README.md

@@ -92,6 +92,7 @@ Need help? Contact [Datadog support][9].
 Additional helpful documentation, links, and articles:
 
 - [Monitoring your container-native technologies][11]
+- [Monitoring the health and performance of your container-native CI/CD pipelines][13]
 
 
 [1]: https://fluxcd.io/
@@ -106,3 +107,4 @@ Additional helpful documentation, links, and articles:
 [10]: https://docs.datadoghq.com/agent/guide/use-community-integrations/?tab=agentv721v621#installation
 [11]: https://www.datadoghq.com/blog/container-native-integrations/#cicd-with-flux
 [12]: https://docs.datadoghq.com/agent/kubernetes/log/
+[13]: https://www.datadoghq.com/blog/container-native-ci-cd-integrations/

ibm_db2/README.md

@@ -41,7 +41,7 @@ For Agent versions >= 6.12 and < 7.0:
 For Agent versions >= 7.0:
 
 ```text
-"C:\Program Files\Datadog\Datadog Agent\embedded3\python.exe" -m pip install ibm_db==3.1.0
+"C:\Program Files\Datadog\Datadog Agent\embedded3\python.exe" -m pip install ibm_db==3.1.4
 ```
 
 On Linux there may be need for XML functionality. If you encounter errors during