Merge branch 'master' into shopify-v1.0.0

DataDog · Oct 7, 2024 · 9fb273e · 9fb273e
2 parents 50d1921 + a9e8077
commit 9fb273e
Show file tree

Hide file tree

Showing 37 changed files with 124 additions and 101 deletions.
diff --git a/appgate_sdp/CHANGELOG.md b/appgate_sdp/CHANGELOG.md
@@ -2,3 +2,8 @@
 
 <!-- towncrier release notes start -->
 
+## 1.0.0 / 2024-10-04
+
+***Added***:
+
+* Initial Release ([#18465](https://github.com/DataDog/integrations-core/pull/18465))
diff --git a/appgate_sdp/changelog.d/18465.added b/appgate_sdp/changelog.d/18465.added
diff --git a/appgate_sdp/datadog_checks/appgate_sdp/__about__.py b/appgate_sdp/datadog_checks/appgate_sdp/__about__.py
@@ -1,4 +1,4 @@
 # (C) Datadog, Inc. 2024-present
 # All rights reserved
 # Licensed under a 3-clause BSD style license (see LICENSE)
-__version__ = '0.0.1'
+__version__ = '1.0.0'
diff --git a/cisco_secure_endpoint/README.md b/cisco_secure_endpoint/README.md
@@ -38,10 +38,10 @@ Configure the Datadog endpoint to forward Cisco Secure Endpoint logs to Datadog.
 
 | Cisco Secure Endpoint Parameters | Description  |
 | -------------------- | ------------ |
-| API Host URL                | The API Host URL for Cisco Secure Endpoint Cloud is "https://api.\<region\>.apm.cisco.com". Adjust the "region" part based on the region of the Cisco Secure Endpoint server. If Cisco Secure Endpoint is hosted on VPC (Virtual Private Cloud), directly provide the API Host URL. |
+| API Domain Name                | The API Domain Name for Cisco Secure Endpoint Cloud is "api.\<region\>.amp.cisco.com". Adjust the "region" part based on the region of the Cisco Secure Endpoint server. If Cisco Secure Endpoint is hosted on VPC (Virtual Private Cloud), directly provide the API Domain Name. |
 | Client ID      | Client ID from Cisco Secure Endpoint.    |
 | API Key           | API Key from Cisco Secure Endpoint.         |
-| Get Endpoint Details    | Keep it "true" to collect endpoint metadata for Cisco Secure Endpoint event logs, otherwise "false". |
+| Get Endpoint Details    | Keep it "true" to collect endpoint metadata for Cisco Secure Endpoint event logs, otherwise "false". Default value is "true". |
 
 
 ## Data Collected

diff --git a/kubeflow/CHANGELOG.md b/kubeflow/CHANGELOG.md
@@ -2,3 +2,8 @@
 
 <!-- towncrier release notes start -->
 
+## 1.0.0 / 2024-10-04
+
+***Fixed***:
+
+* Bump the version of datadog-checks-base to 37.0.0 ([#18617](https://github.com/DataDog/integrations-core/pull/18617))
diff --git a/kubeflow/changelog.d/18617.fixed b/kubeflow/changelog.d/18617.fixed
diff --git a/kubeflow/datadog_checks/kubeflow/__about__.py b/kubeflow/datadog_checks/kubeflow/__about__.py
@@ -1,4 +1,4 @@
 # (C) Datadog, Inc. 2024-present
 # All rights reserved
 # Licensed under a 3-clause BSD style license (see LICENSE)
-__version__ = '0.0.1'
+__version__ = '1.0.0'
diff --git a/kubeflow/manifest.json b/kubeflow/manifest.json
@@ -2,7 +2,7 @@
   "manifest_version": "2.0.0",
   "app_uuid": "0db7b333-38a1-4e09-af1b-317da2f9f413",
   "app_id": "kubeflow",
-  "display_on_public_website": false,
+  "display_on_public_website": true,
   "tile": {
     "overview": "README.md#Overview",
     "configuration": "README.md#Setup",

diff --git a/kubevirt_api/CHANGELOG.md b/kubevirt_api/CHANGELOG.md
@@ -1,3 +1,13 @@
 # CHANGELOG - KubeVirt API
 
 <!-- towncrier release notes start -->
+
+## 1.0.0 / 2024-10-04
+
+***Added***:
+
+* Initial Release ([#18179](https://github.com/DataDog/integrations-core/pull/18179))
+
+***Fixed***:
+
+* Bump the version of datadog-checks-base to 37.0.0 ([#18617](https://github.com/DataDog/integrations-core/pull/18617))
diff --git a/kubevirt_api/changelog.d/18179.added b/kubevirt_api/changelog.d/18179.added
diff --git a/kubevirt_api/changelog.d/18617.fixed b/kubevirt_api/changelog.d/18617.fixed
diff --git a/kubevirt_api/datadog_checks/kubevirt_api/__about__.py b/kubevirt_api/datadog_checks/kubevirt_api/__about__.py
@@ -1,4 +1,4 @@
 # (C) Datadog, Inc. 2024-present
 # All rights reserved
 # Licensed under a 3-clause BSD style license (see LICENSE)
-__version__ = '0.0.1'
+__version__ = '1.0.0'
diff --git a/kubevirt_api/manifest.json b/kubevirt_api/manifest.json
@@ -42,7 +42,8 @@
       },
       "service_checks": {
         "metadata_path": "assets/service_checks.json"
-      }
+      },
+      "process_signatures": ["virt-api"]
     },
     "dashboards": {
       "KubeVirt Overview": "assets/dashboards/kubevirt_overview.json"

diff --git a/kubevirt_api/metadata.csv b/kubevirt_api/metadata.csv
@@ -1,5 +1,5 @@
 metric_name,metric_type,interval,unit_name,per_unit_name,description,orientation,integration,short_name,curated_metric,sample_tags
-kubevirt_api.can_connect,gauge,,,,Whether the check can connect to the KubeVirt API or not.,0,kubevirt_api,api connect,,
+kubevirt_api.can_connect,gauge,,,,"Value of 1 if the agent can connect to the KubeVirt Handler, and 0 otherwise.",0,kubevirt_api,api connect,,
 kubevirt_api.process.cpu_seconds.count,count,,second,,Total user and system CPU time spent in seconds.,0,kubevirt_api,cpu time total,,
 kubevirt_api.process.max_fds,gauge,,file,,Maximum number of open file descriptors.,0,kubevirt_api,max fds,,
 kubevirt_api.process.open_fds,gauge,,file,,Number of open file descriptors.,0,kubevirt_api,open fds,,

diff --git a/kubevirt_controller/CHANGELOG.md b/kubevirt_controller/CHANGELOG.md
@@ -2,3 +2,12 @@
 
 <!-- towncrier release notes start -->
 
+## 1.0.0 / 2024-10-04
+
+***Added***:
+
+* Initial Release ([#18186](https://github.com/DataDog/integrations-core/pull/18186))
+
+***Fixed***:
+
+* Bump the version of datadog-checks-base to 37.0.0 ([#18617](https://github.com/DataDog/integrations-core/pull/18617))
diff --git a/kubevirt_controller/changelog.d/18186.added b/kubevirt_controller/changelog.d/18186.added
diff --git a/kubevirt_controller/changelog.d/18617.fixed b/kubevirt_controller/changelog.d/18617.fixed
diff --git a/kubevirt_controller/datadog_checks/kubevirt_controller/__about__.py b/kubevirt_controller/datadog_checks/kubevirt_controller/__about__.py
@@ -1,4 +1,4 @@
 # (C) Datadog, Inc. 2024-present
 # All rights reserved
 # Licensed under a 3-clause BSD style license (see LICENSE)
-__version__ = '0.0.1'
+__version__ = '1.0.0'
diff --git a/kubevirt_controller/datadog_checks/kubevirt_controller/check.py b/kubevirt_controller/datadog_checks/kubevirt_controller/check.py
@@ -63,6 +63,10 @@ def _parse_config(self):
             "namespace": self.__NAMESPACE__,
             "enable_health_service_check": False,
             "tls_verify": self.tls_verify,
+            "rename_labels": {
+                "namespace": "vm_namespace",
+                # both kubevirt_vm_* and kubevirt_vmi_* metrics share the same name and namespace labels
+            },
         }
 
         self.scraper_configs.append(instance)

diff --git a/kubevirt_controller/manifest.json b/kubevirt_controller/manifest.json
@@ -42,7 +42,8 @@
       },
       "service_checks": {
         "metadata_path": "assets/service_checks.json"
-      }
+      },
+      "process_signatures": ["virt-controller"]
     }
   },
   "author": {

diff --git a/kubevirt_controller/metadata.csv b/kubevirt_controller/metadata.csv
@@ -1,35 +1,35 @@
 metric_name,metric_type,interval,unit_name,per_unit_name,description,orientation,integration,short_name,curated_metric,sample_tags
-kubevirt_controller.can_connect,gauge,,,,Whether the check can connect to the KubeVirt Controller or not.,0,kubevirt_controller,api connect,,
+kubevirt_controller.can_connect,gauge,,,,"Value of 1 if the agent can connect to the KubeVirt Controller, and 0 otherwise.",0,kubevirt_controller,api connect,,
 kubevirt_controller.virt_controller.leading_status,gauge,,,,Indication for an operating virt-controller.,0,kubevirt_controller,leading_status,,
 kubevirt_controller.virt_controller.ready_status,gauge,,,,Indication for a virt-controller that is ready to take the lead.,0,kubevirt_controller,ready_status,,
-kubevirt_controller.vm.error_status_last_transition_timestamp_seconds.count,count,,,,Virtual Machine last transition timestamp to error status.,0,kubevirt_controller,,,
-kubevirt_controller.vm.migrating_status_last_transition_timestamp_seconds.count,count,,,,Virtual Machine last transition timestamp to migrating status.,0,kubevirt_controller,,,
-kubevirt_controller.vm.non_running_status_last_transition_timestamp_seconds.count,count,,,,Virtual Machine last transition timestamp to paused/stopped status.,0,kubevirt_controller,,,
-kubevirt_controller.vm.running_status_last_transition_timestamp_seconds.count,count,,,,Virtual Machine last transition timestamp to running status.,0,kubevirt_controller,,,
-kubevirt_controller.vm.starting_status_last_transition_timestamp_seconds.count,count,,,,Virtual Machine last transition timestamp to starting status.,0,kubevirt_controller,,,
+kubevirt_controller.vm.error_status_last_transition_timestamp_seconds.count,count,,second,,Virtual Machine last transition timestamp to error status.,0,kubevirt_controller,,,
+kubevirt_controller.vm.migrating_status_last_transition_timestamp_seconds.count,count,,second,,Virtual Machine last transition timestamp to migrating status.,0,kubevirt_controller,,,
+kubevirt_controller.vm.non_running_status_last_transition_timestamp_seconds.count,count,,second,,Virtual Machine last transition timestamp to paused/stopped status.,0,kubevirt_controller,,,
+kubevirt_controller.vm.running_status_last_transition_timestamp_seconds.count,count,,second,,Virtual Machine last transition timestamp to running status.,0,kubevirt_controller,,,
+kubevirt_controller.vm.starting_status_last_transition_timestamp_seconds.count,count,,second,,Virtual Machine last transition timestamp to starting status.,0,kubevirt_controller,,,
 kubevirt_controller.vmi.migrations_in_pending_phase,gauge,,,,Number of current pending migrations.,0,kubevirt_controller,,,
 kubevirt_controller.vmi.migrations_in_running_phase,gauge,,,,Number of current running migrations.,0,kubevirt_controller,,,
 kubevirt_controller.vmi.migrations_in_scheduling_phase,gauge,,,,Number of current scheduling migrations.,0,kubevirt_controller,,,
 kubevirt_controller.vmi.non_evictable,gauge,,,,Indication for a VirtualMachine that its eviction strategy is set to Live Migration but is not migratable.,0,kubevirt_controller,,,
 kubevirt_controller.vmi.number_of_outdated,gauge,,,,Indication for the total number of VirtualMachineInstance workloads that are not running within the most up-to-date version of the virt-launcher environment.,0,kubevirt_controller,,,
 kubevirt_controller.vmi.phase_count,gauge,,,,"Sum of VMIs per phase and node. phase can be one of the following: [Pending, Scheduling, Scheduled, Running, Succeeded, Failed, Unknown].",0,kubevirt_controller,,,
-kubevirt_controller.vmi.phase_transition_time_from_creation_seconds.bucket,count,,,,Histogram of VM phase transitions duration from creation time in seconds.,0,kubevirt_controller,,,
-kubevirt_controller.vmi.phase_transition_time_from_creation_seconds.count,count,,,,Histogram of VM phase transitions duration from creation time in seconds.,0,kubevirt_controller,,,
-kubevirt_controller.vmi.phase_transition_time_from_creation_seconds.sum,count,,,,Histogram of VM phase transitions duration from creation time in seconds.,0,kubevirt_controller,,,
-kubevirt_controller.vmi.phase_transition_time_from_deletion_seconds.bucket,count,,,,Histogram of VM phase transitions duration from deletion time in seconds.,0,kubevirt_controller,,,
-kubevirt_controller.vmi.phase_transition_time_from_deletion_seconds.count,count,,,,Histogram of VM phase transitions duration from deletion time in seconds.,0,kubevirt_controller,,,
-kubevirt_controller.vmi.phase_transition_time_from_deletion_seconds.sum,count,,,,Histogram of VM phase transitions duration from deletion time in seconds.,0,kubevirt_controller,,,
-kubevirt_controller.vmi.phase_transition_time_seconds.bucket,count,,,,Histogram of VM phase transitions duration between different phases in seconds.,0,kubevirt_controller,,,
-kubevirt_controller.vmi.phase_transition_time_seconds.count,count,,,,Histogram of VM phase transitions duration between different phases in seconds.,0,kubevirt_controller,,,
-kubevirt_controller.vmi.phase_transition_time_seconds.sum,count,,,,Histogram of VM phase transitions duration between different phases in seconds.,0,kubevirt_controller,,,
-kubevirt_controller.workqueue.adds.count,count,,,,Total number of adds handled by workqueue,0,kubevirt_controller,,,
-kubevirt_controller.workqueue.depth,gauge,,,,Current depth of workqueue,0,kubevirt_controller,,,
-kubevirt_controller.workqueue.longest_running_processor_seconds,gauge,,,,How many seconds has the longest running processor for workqueue been running.,0,kubevirt_controller,,,
-kubevirt_controller.workqueue.queue_duration_seconds.bucket,count,,,,How long an item stays in workqueue before being requested.,0,kubevirt_controller,,,
-kubevirt_controller.workqueue.queue_duration_seconds.count,count,,,,How long an item stays in workqueue before being requested.,0,kubevirt_controller,,,
-kubevirt_controller.workqueue.queue_duration_seconds.sum,count,,,,How long an item stays in workqueue before being requested.,0,kubevirt_controller,,,
+kubevirt_controller.vmi.phase_transition_time_from_creation_seconds.bucket,count,,second,,Histogram of VM phase transitions duration from creation time in seconds.,0,kubevirt_controller,,,
+kubevirt_controller.vmi.phase_transition_time_from_creation_seconds.count,count,,second,,Histogram of VM phase transitions duration from creation time in seconds.,0,kubevirt_controller,,,
+kubevirt_controller.vmi.phase_transition_time_from_creation_seconds.sum,count,,second,,Histogram of VM phase transitions duration from creation time in seconds.,0,kubevirt_controller,,,
+kubevirt_controller.vmi.phase_transition_time_from_deletion_seconds.bucket,count,,second,,Histogram of VM phase transitions duration from deletion time in seconds.,0,kubevirt_controller,,,
+kubevirt_controller.vmi.phase_transition_time_from_deletion_seconds.count,count,,second,,Histogram of VM phase transitions duration from deletion time in seconds.,0,kubevirt_controller,,,
+kubevirt_controller.vmi.phase_transition_time_from_deletion_seconds.sum,count,,second,,Histogram of VM phase transitions duration from deletion time in seconds.,0,kubevirt_controller,,,
+kubevirt_controller.vmi.phase_transition_time_seconds.bucket,count,,second,,Histogram of VM phase transitions duration between different phases in seconds.,0,kubevirt_controller,,,
+kubevirt_controller.vmi.phase_transition_time_seconds.count,count,,second,,Histogram of VM phase transitions duration between different phases in seconds.,0,kubevirt_controller,,,
+kubevirt_controller.vmi.phase_transition_time_seconds.sum,count,,second,,Histogram of VM phase transitions duration between different phases in seconds.,0,kubevirt_controller,,,
+kubevirt_controller.workqueue.adds.count,count,,item,,Total number of adds handled by workqueue,0,kubevirt_controller,,,
+kubevirt_controller.workqueue.depth,gauge,,item,,Current depth of workqueue,0,kubevirt_controller,,,
+kubevirt_controller.workqueue.longest_running_processor_seconds,gauge,,second,,How many seconds has the longest running processor for workqueue been running.,0,kubevirt_controller,,,
+kubevirt_controller.workqueue.queue_duration_seconds.bucket,count,,second,,How long an item stays in workqueue before being requested.,0,kubevirt_controller,,,
+kubevirt_controller.workqueue.queue_duration_seconds.count,count,,second,,How long an item stays in workqueue before being requested.,0,kubevirt_controller,,,
+kubevirt_controller.workqueue.queue_duration_seconds.sum,count,,second,,How long an item stays in workqueue before being requested.,0,kubevirt_controller,,,
 kubevirt_controller.workqueue.retries.count,count,,,,Total number of retries handled by workqueue.,0,kubevirt_controller,,,
-kubevirt_controller.workqueue.unfinished_work_seconds,gauge,,,,How many seconds of work has done that is in progress and hasn't been observed by work_duration. Large values indicate stuck threads. One can deduce the number of stuck threads by observing the rate at which this increases.,0,kubevirt_controller,,,
-kubevirt_controller.workqueue.work_duration_seconds.bucket,count,,,,How long in seconds processing an item from workqueue takes.,0,kubevirt_controller,,,
-kubevirt_controller.workqueue.work_duration_seconds.count,count,,,,How long in seconds processing an item from workqueue takes.,0,kubevirt_controller,,,
-kubevirt_controller.workqueue.work_duration_seconds.sum,count,,,,How long in seconds processing an item from workqueue takes.,0,kubevirt_controller,,,
+kubevirt_controller.workqueue.unfinished_work_seconds,gauge,,second,,How many seconds of work has done that is in progress and hasn't been observed by work_duration. Large values indicate stuck threads. One can deduce the number of stuck threads by observing the rate at which this increases.,0,kubevirt_controller,,,
+kubevirt_controller.workqueue.work_duration_seconds.bucket,count,,second,,How long in seconds processing an item from workqueue takes.,0,kubevirt_controller,,,
+kubevirt_controller.workqueue.work_duration_seconds.count,count,,second,,How long in seconds processing an item from workqueue takes.,0,kubevirt_controller,,,
+kubevirt_controller.workqueue.work_duration_seconds.sum,count,,second,,How long in seconds processing an item from workqueue takes.,0,kubevirt_controller,,,
diff --git a/kubevirt_handler/CHANGELOG.md b/kubevirt_handler/CHANGELOG.md
@@ -1,3 +1,9 @@
 # CHANGELOG - KubeVirt Handler
 
 <!-- towncrier release notes start -->
+
+## 1.0.0 / 2024-10-04
+
+***Added***:
+
+* Initial Release ([#18283](https://github.com/DataDog/integrations-core/pull/18283))
diff --git a/kubevirt_handler/changelog.d/18283.added b/kubevirt_handler/changelog.d/18283.added
diff --git a/kubevirt_handler/datadog_checks/kubevirt_handler/__about__.py b/kubevirt_handler/datadog_checks/kubevirt_handler/__about__.py
@@ -1,4 +1,4 @@
 # (C) Datadog, Inc. 2024-present
 # All rights reserved
 # Licensed under a 3-clause BSD style license (see LICENSE)
-__version__ = '0.0.1'
+__version__ = '1.0.0'
diff --git a/kubevirt_handler/datadog_checks/kubevirt_handler/check.py b/kubevirt_handler/datadog_checks/kubevirt_handler/check.py
@@ -61,6 +61,9 @@ def _parse_config(self):
             "namespace": self.__NAMESPACE__,
             "enable_health_service_check": False,
             "tls_verify": self.tls_verify,
+            "rename_labels": {
+                "namespace": "vm_namespace",
+            },
         }
 
         self.scraper_configs.append(instance)

diff --git a/kubevirt_handler/images/IMAGES_README.md b/kubevirt_handler/images/IMAGES_README.md
diff --git a/kubevirt_handler/manifest.json b/kubevirt_handler/manifest.json
@@ -35,14 +35,15 @@
       "metrics": {
         "prefix": "kubevirt_handler.",
         "check": [
-          "kubevirt_handler.can_connect", 
+          "kubevirt_handler.can_connect",
           "kubevirt_handler.vmi.cpu_system_usage_seconds.count"
         ],
         "metadata_path": "metadata.csv"
       },
       "service_checks": {
         "metadata_path": "assets/service_checks.json"
-      }
+      },
+      "process_signatures": ["virt-handler"]
     }
   },
   "author": {

diff --git a/kubevirt_handler/metadata.csv b/kubevirt_handler/metadata.csv
@@ -1,5 +1,5 @@
 metric_name,metric_type,interval,unit_name,per_unit_name,description,orientation,integration,short_name,curated_metric,sample_tags
-kubevirt_handler.can_connect,gauge,,,,Whether the check can connect to the KubeVirt Handler or not.,0,kubevirt_handler,handler connect,,
+kubevirt_handler.can_connect,gauge,,,,"Value of 1 if the agent can connect to the KubeVirt Handler, and 0 otherwise.",0,kubevirt_handler,handler connect,,
 kubevirt_handler.vmi.cpu_system_usage_seconds.count,count,,second,,"Total CPU time spent in system mode.",0,kubevirt_handler,short_name,,
 kubevirt_handler.vmi.cpu_usage_seconds.count,count,,second,,"Total CPU time spent in all modes (sum of both vcpu and hypervisor usage).",0,kubevirt_handler,short_name,,
 kubevirt_handler.vmi.cpu_user_usage_seconds.count,count,,second,,"Total CPU time spent in user mode.",0,kubevirt_handler,short_name,,

diff --git a/mimecast/README.md b/mimecast/README.md
@@ -33,7 +33,7 @@ To find your application's details in Mimecast Email Security:
      - Application Name: Enter the application name of your choice
      - Category: Select **SIEM Integration**
      - Products: Click **Select all** option
-     - Application Role: Select **SIEM Admin Role**
+     - Application Role: Select **Basic Administrator**
      - Description: Enter the description of your choice
    - In **Notifications**, provide the contact details of your technical administrator and click on **Next**
    - After clicking on **Add and Generate Keys** there will be pop up window showing Client ID and Client Secret. Please copy those keys to a safe place as they won't be displayed again.