Standardize docs references to timeseries

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-02-06 09:57:38.488544",
-            "spec_repo_commit": "3518f3a0"
+            "regenerated": "2024-02-06 15:45:08.603113",
+            "spec_repo_commit": "46672359"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-02-06 09:57:38.506381",
-            "spec_repo_commit": "3518f3a0"
+            "regenerated": "2024-02-06 15:45:08.619048",
+            "spec_repo_commit": "46672359"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -6328,7 +6328,7 @@ components:
       description: The metrics' payload.
       properties:
         series:
-          description: A list of time series to submit to Datadog.
+          description: A list of timeseries to submit to Datadog.
           example:
           - metric: system.load.1
             points:
@@ -6381,7 +6381,7 @@ components:
           readOnly: true
           type: string
         pointlist:
-          description: List of points of the time series in milliseconds.
+          description: List of points of the timeseries in milliseconds.
           example:
           - - 1681683300000.0
             - 77.62145685254418
@@ -10409,7 +10409,7 @@ components:
       - denominator
       type: object
     SLOHistoryMetricsSeries:
-      description: 'A representation of `metric` based SLO time series for the provided
+      description: 'A representation of `metric` based SLO timeseries for the provided
         queries.
 
         This is the same response type from `batch_query` endpoint.'
@@ -10530,18 +10530,18 @@ components:
           type: string
         history:
           description: For `monitor` based SLOs, this includes the aggregated history
-            as arrays that include time series and uptime data where `0=monitor` is
+            as arrays that include timeseries and uptime data where `0=monitor` is
             in `OK` state and `1=monitor` is in `alert` state.
           example:
           - - 1579212382
             - 0
           items:
-            description: Represents an array time series data.
+            description: Represents an array timeseries data.
             example:
             - 1579212382
             - 0
             items:
-              description: A time series data point which is a tuple of (timestamp,
+              description: A timeseries data point which is a tuple of (timestamp,
                 value).
               format: double
               type: number
@@ -10712,18 +10712,18 @@ components:
           type: string
         history:
           description: For `monitor` based SLOs, this includes the aggregated history
-            as arrays that include time series and uptime data where `0=monitor` is
+            as arrays that include timeseries and uptime data where `0=monitor` is
             in `OK` state and `1=monitor` is in `alert` state.
           example:
           - - 1579212382
             - 0
           items:
-            description: Represents an array time series data.
+            description: Represents an array timeseries data.
             example:
             - 1579212382
             - 0
             items:
-              description: A time series data point which is a tuple of (timestamp,
+              description: A timeseries data point which is a tuple of (timestamp,
                 value).
               format: double
               type: number

.generator/schemas/v2/openapi.yaml

@@ -11083,7 +11083,7 @@ components:
       description: The metrics' payload.
       properties:
         series:
-          description: A list of time series to submit to Datadog.
+          description: A list of timeseries to submit to Datadog.
           example:
           - metric: system.load.1
             points:

lib/datadog_api_client/v1/models/metrics_payload.rb

@@ -21,7 +21,7 @@ module DatadogAPIClient::V1
   class MetricsPayload
     include BaseGenericModel
 
-    # A list of time series to submit to Datadog.
+    # A list of timeseries to submit to Datadog.
     attr_reader :series
 
     # Attribute mapping from ruby-style variable name to JSON key.

lib/datadog_api_client/v1/models/metrics_query_metadata.rb

@@ -42,7 +42,7 @@ class MetricsQueryMetadata
     # Metric name.
     attr_accessor :metric
 
-    # List of points of the time series in milliseconds.
+    # List of points of the timeseries in milliseconds.
     attr_accessor :pointlist
 
     # The index of the series' query within the request.

lib/datadog_api_client/v1/models/slo_history_metrics.rb

@@ -23,7 +23,7 @@ module DatadogAPIClient::V1
   class SLOHistoryMetrics
     include BaseGenericModel
 
-    # A representation of `metric` based SLO time series for the provided queries.
+    # A representation of `metric` based SLO timeseries for the provided queries.
     # This is the same response type from `batch_query` endpoint.
     attr_reader :denominator
 
@@ -33,7 +33,7 @@ class SLOHistoryMetrics
     # Optional message if there are specific query issues/warnings.
     attr_accessor :message
 
-    # A representation of `metric` based SLO time series for the provided queries.
+    # A representation of `metric` based SLO timeseries for the provided queries.
     # This is the same response type from `batch_query` endpoint.
     attr_reader :numerator
 

lib/datadog_api_client/v1/models/slo_history_metrics_series.rb

@@ -17,7 +17,7 @@
 require 'time'
 
 module DatadogAPIClient::V1
-  # A representation of `metric` based SLO time series for the provided queries.
+  # A representation of `metric` based SLO timeseries for the provided queries.
   # This is the same response type from `batch_query` endpoint.
   class SLOHistoryMetricsSeries
     include BaseGenericModel

lib/datadog_api_client/v1/models/slo_history_monitor.rb

@@ -31,7 +31,7 @@ class SLOHistoryMonitor
     # For groups in a grouped SLO, this is the group name.
     attr_accessor :group
 
-    # For `monitor` based SLOs, this includes the aggregated history as arrays that include time series and uptime data where `0=monitor` is in `OK` state and `1=monitor` is in `alert` state.
+    # For `monitor` based SLOs, this includes the aggregated history as arrays that include timeseries and uptime data where `0=monitor` is in `OK` state and `1=monitor` is in `alert` state.
     attr_accessor :history
 
     # For `monitor` based SLOs, this is the last modified timestamp in epoch seconds of the monitor.

lib/datadog_api_client/v1/models/slo_history_sli_data.rb

@@ -31,7 +31,7 @@ class SLOHistorySLIData
     # For groups in a grouped SLO, this is the group name.
     attr_accessor :group
 
-    # For `monitor` based SLOs, this includes the aggregated history as arrays that include time series and uptime data where `0=monitor` is in `OK` state and `1=monitor` is in `alert` state.
+    # For `monitor` based SLOs, this includes the aggregated history as arrays that include timeseries and uptime data where `0=monitor` is in `OK` state and `1=monitor` is in `alert` state.
     attr_accessor :history
 
     # For `monitor` based SLOs, this is the last modified timestamp in epoch seconds of the monitor.

lib/datadog_api_client/v2/models/metric_payload.rb

@@ -21,7 +21,7 @@ module DatadogAPIClient::V2
   class MetricPayload
     include BaseGenericModel
 
-    # A list of time series to submit to Datadog.
+    # A list of timeseries to submit to Datadog.
     attr_reader :series
 
     # Attribute mapping from ruby-style variable name to JSON key.