Update docs

Author: sarah-witt

octopus_deploy/assets/configuration/spec.yaml

@@ -20,21 +20,21 @@ files:
     - name: spaces
       display_priority: 5
       description: |
-        Optional configuration to indicate the spaces that we want to be processed. If not configured,
+        Optional configuration to indicate the spaces to process. If not configured,
         all spaces and their corresponding project groups and projects are be processed.
 
         The 'include' key indicates the regular expressions of the spaces for reporting metrics 
         and the configuration to be applied to each of them. Each group can have a 'project-groups'-like configuration,
         that enables or disables metric collection for the project groups matching that condition. For further details
         see the next section, 'project-groups'. If no configuration associated with the key is indicated with the regular
-        expression, they are be processed with the default configuration.
+        expression, they are processed with the default configuration.
 
         The spaces are processed in the order indicated in the 'include'.
         If a space is matched on an 'include' key, it is only processed there and not in a later 'include'
         that it might match on.
 
         The 'exclude' key indicates the regular expressions of those spaces for not reporting metrics.
-        The excludes have priority over the includes, that is, if a space matches an exclude, it is not
+        The excludes have priority over the includes; that is, if a space matches an exclude, it is not
         processed even if it matches an include. The 'include' key must be used if using the 'exclude' key.
 
         The 'limit' key allows limiting the number of spaces processed to avoid a combinatorial explosion of tags
@@ -81,28 +81,28 @@ files:
     - name: project_groups
       display_priority: 5
       description: |
-        Optional configuration to indicate the project groups that we want to be processed. If not configured,
+        Optional configuration to indicate the project groups to process. If not configured,
         all project groups are processed.
 
         The 'include' key indicates the regular expressions of the project groups for reporting metrics
         and the configuration to be applied to each of them. Each group can have a 'projects'-like
         configuration, that enables or disables metric collection for the projects matching that condition. For
         further details see previous section 'projects'. If no configuration associated with the key is indicated with
-        the regular expression, they are be processed with the default configuration.
+        the regular expression, they are processed with the default configuration.
 
         The project groups are processed in the order indicated in the 'include'.
         If a project group is matched on an 'include' key, it is only processed there and not in a later 'include'
         that it might match on.
 
         The 'exclude' key indicates the regular expressions of those project groups for not reporting metrics.
-        The excludes has priority over the includes, that is, if a project group matches an exclude, it is not
+        The excludes have priority over the includes; that is, if a project group matches an exclude, it is not
         processed even if it matches an include. The 'include' key must be used if using the 'exclude' key.
 
         The 'limit' key allows limiting the number of project groups processed to avoid a combinatorial explosion of
         tags associated with a metric.
 
         The 'interval' key indicates the validity time of the last list of project groups obtained through the
-        endpoint. If 'interval' is not indicated, the list of project groups are obtained each time the check is
+        endpoint. If 'interval' is not indicated, the list of project groups is obtained each time the check is
         executed and is not cached.
 
         In the following example, all project groups are processed except those whose name begins with 'tmp_'
@@ -139,17 +139,17 @@ files:
     - name: projects
       display_priority: 5
       description: |
-        Optional configuration to indicate the projects that we want to be processed. If not configured,
+        Optional configuration to indicate the projects to process. If not configured,
         all projects are processed.
 
         The 'include' key indicates the regular expressions of the projects for reporting metrics.
 
         The projects are processed in the order indicated in the 'include'.
-        If a projects is matched on an 'include' key, it is only processed there and not in a later 'include'
+        If a project is matched on an 'include' key, it is only processed there and not in a later 'include'
         that it might match on.
 
         The 'exclude' key indicates the regular expressions of those projects for not reporting metrics.
-        The excludes has priority over the includes, that is, if a projects matches an exclude, it is not
+        The excludes have priority over the includes; that is, if a project matches an exclude, it is not
         processed even if it matches an include. The 'include' key must be used if using the 'exclude' key.
 
         The 'limit' key allows limiting the number of projects processed to avoid a combinatorial explosion of tags
@@ -187,7 +187,7 @@ files:
     - name: environments
       display_priority: 6
       description: |
-          Optional configuration to indicate the environments that we want to be processed. If not configured,
+          Optional configuration to indicate the environments to process. If not configured,
           all environments are processed.
 
           The 'include' key indicates the regular expressions of the environments for reporting metrics.
@@ -197,7 +197,7 @@ files:
           that it might match on.
 
           The 'exclude' key indicates the regular expressions of those environments for not reporting metrics.
-          The excludes has priority over the includes, that is, if an environment matches an exclude, it is not
+          The excludes have priority over the includes; that is, if an environment matches an exclude, it is not
           processed even if it matches an include. The 'include' key must be used if using the 'exclude' key.
 
           The 'limit' key allows limiting the number of environments processed to avoid a combinatorial explosion of

octopus_deploy/datadog_checks/octopus_deploy/data/conf.yaml.example

@@ -90,7 +90,7 @@ instances:
 
     ## @param spaces - mapping - optional
     ## Optional configuration to indicate the spaces to process. If not configured,
-    ## all spaces and their corresponding project groups and projects are processed.
+    ## all spaces and their corresponding project groups and projects are be processed.
     ##
     ## The 'include' key indicates the regular expressions of the spaces for reporting metrics 
     ## and the configuration to be applied to each of them. Each group can have a 'project-groups'-like configuration,
@@ -286,7 +286,7 @@ instances:
     ## @param metric_patterns - mapping - optional
     ## A mapping of metrics to include or exclude, with each entry being a regular expression.
     ##
-    ## Metrics defined in `exclude` take precedence in case of overlap.
+    ## Metrics defined in `exclude` will take precedence in case of overlap.
     #
     # metric_patterns:
     #   include:

octopus_deploy/metadata.csv

@@ -1,12 +1,12 @@
 metric_name,metric_type,interval,unit_name,per_unit_name,description,orientation,integration,short_name,curated_metric,sample_tags
 octopus_deploy.api.can_connect,gauge,,,,Whether or not the check can connect to the Octopus Deploy API,-1,octopus_deploy,octopus_deploy api,,
-octopus_deploy.deployment.completed_time,gauge,,second,,Duration of deployment,-1,octopus_deploy,octopus_deploy deploy dur,,
+octopus_deploy.deployment.completed_time,gauge,,second,,Duration of deployment,-1,octopus_deploy,octopus_deploy deploy completed,,
 octopus_deploy.deployment.count,gauge,,,,Number of deployments monitored,-1,octopus_deploy,octopus_deploy deploy count,,
 octopus_deploy.deployment.executing,gauge,,,,Whether or not the deployment is currently executing,-1,octopus_deploy,octopus_deploy deploy executing,,
-octopus_deploy.deployment.executing_time,gauge,,second,,How long the deployment has been executing,-1,octopus_deploy,octopus_deploy deploy dur,,
-octopus_deploy.deployment.queued,gauge,,second,,Whether or not the deployment is currently in the queue,-1,octopus_deploy,octopus_deploy deploy queue,,
-octopus_deploy.deployment.queued_time,gauge,,second,,Time deployment was in queue,-1,octopus_deploy,octopus_deploy deploy queue,,
-octopus_deploy.deployment.waiting,gauge,,second,,Whether or not the deployment is in a waiting state,-1,octopus_deploy,octopus_deploy deploy waiting,,
+octopus_deploy.deployment.executing_time,gauge,,second,,How long the deployment has been executing,-1,octopus_deploy,octopus_deploy deploy execute,,
+octopus_deploy.deployment.queued,gauge,,,,Whether or not the deployment is currently in the queue,-1,octopus_deploy,octopus_deploy deploy queue,,
+octopus_deploy.deployment.queued_time,gauge,,second,,Time deployment was in queue,-1,octopus_deploy,octopus_deploy deploy queue time,,
+octopus_deploy.deployment.waiting,gauge,,,,Whether or not the deployment is in a waiting state,-1,octopus_deploy,octopus_deploy deploy waiting,,
 octopus_deploy.environment.allow_dynamic_infrastructure,gauge,,,,Whether or not the environment allows dynamic infrastructure,-1,octopus_deploy,octopus_deploy env infra,,
 octopus_deploy.environment.count,gauge,,,,Number of environments discovered,-1,octopus_deploy,octopus_deploy env count,,
 octopus_deploy.environment.use_guided_failure,gauge,,,,Whether or not the environment is in guided failure mode,-1,octopus_deploy,octopus_deploy env guided failure,,