enhancementhelp wantedregistry: datadog
Metriche repository
- Star
- (4220 star)
- Metriche merge PR
- (Merge medio 1g 21h) (100 PR mergiate in 30 g)
Descrizione
Due to various issues when transmitting metrics, I contacted datadog and was told to upgrade the API version.
So, after checking to resolve the issue, I found that datadog-related APIs were hard-coded into the code.
Are you planning to upgrade the API version? The recommended content is to transfer to /api/v2/series rather than /api/v1/series.
Related information will be attached below. Datadog says that transmission efficiency and stability have improved due to the upgrade.
POST https://api.datadoghq.com/api/v1/series
The metrics end-point allows you to post time-series data that can be graphed on Datadog’s dashboards. The maximum payload size is 3.2 megabytes (3200000 bytes). Compressed payloads must have a decompressed size of less than 62 megabytes (62914560 bytes).
If you’re submitting metrics directly to the Datadog API without using DogStatsD, expect:
- 64 bits for the timestamp
- 64 bits for the value
- 40 bytes for the metric names
- 50 bytes for the timeseries
- The full payload is approximately 100 bytes. However, with the DogStatsD API, compression is applied, which reduces the payload size.
-----
POST https://api.datadoghq.com/api/v2/series
The metrics end-point allows you to post time-series data that can be graphed on Datadog’s dashboards. The maximum payload size is 500 kilobytes (512000 bytes). Compressed payloads must have a decompressed size of less than 5 megabytes (5242880 bytes).
If you’re submitting metrics directly to the Datadog API without using DogStatsD, expect:
- 64 bits for the timestamp
- 64 bits for the value
- 20 bytes for the metric names
- 50 bytes for the timeseries
- The full payload is approximately 100 bytes.