Target Latency

Latency for all data flowing from the time a piece of data is ingested into Listener until the time it is written to a target. Latency values are returned in millisecond values; therefore, to get the value in seconds, multiply by 1,000.
Note
Due to aggregation, this is useful for obtaining a sense of how well Listener is writing data to the system.

Definition

GET https://listener-app-services.teradata.com/v1/targets/{target_id}/latency?interval,timeframe HTTP/1.1
ParameterRequiredTypeSamplePurpose
target_idRequiredstring758fbda4-accc-4f90-8f09-cc0a164c8c28Time interval for each data point.
intervalOptionalstring1mTime interval for each data point.
timeframeOptionalstring7dTime frame to query into the past.
Parameters use an integer and character combination to denote the time range:
  • s = seconds
  • m = minutes
  • h = hours
  • d = days
  • w = weeks
  • M = months

Example Request

curl \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer TOKEN" \
  -X PUT \
  -i \
  https://listener-app-services.teradata.com/v1/targets/758fbda4-accc-4f90-8f09-cc0a164c8c28/latency

Example Response

HTTP/1.1 200 OK
Content-Type: application/json
[
  {
    "doc_count": 375,
    "latency": {
      "avg": 2982.816,
      "count": 375,
      "max": 13953,
      "min": -7418,
      "std_deviation": 6946.194437878245,
      "std_deviation_bounds": {
        "lower": -10909.57287575649,
        "upper": 16875.204875756488
      },
      "sum": 1118556,
      "sum_of_squares": 21430053172,
      "variance": 48249617.168810666
    },
    "time": "2015-12-11T21:13:00Z"
  }
]

Response Codes

CodeDescription
201Metrics successfully loaded.
401Authorization header not found.
404Resource not found.

results matching ""

    No results matching ""