Datadog Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
==API Key== | ==API Key== | ||
An API key is required by the [[#Agent|Datadog Agent]] to submit metrics and events to Datadog. The API keys are also used by other third-party clients, such as, for example, the [[Managing_Datadog_with_Pulumi#Datadog_Resource_Provider|Pulumi Datadog resource provider, which provisions infrastructure on the Datadog backend. | An API key is required by the [[#Agent|Datadog Agent]] to submit metrics and events to Datadog. The API keys are also used by other third-party clients, such as, for example, the [[Managing_Datadog_with_Pulumi#Datadog_Resource_Provider|Pulumi Datadog resource provider]], which provisions infrastructure on the Datadog backend. | ||
==Application Key== | ==Application Key== | ||
Revision as of 05:42, 14 January 2022
Internal
Agent
The Datadog agent has a built-in StatsD server, exposed over a configurable port.
Agent and Kubernetes
TO CONTINUE: https://docs.datadoghq.com/developers/dogstatsd/?tab=kubernetes#
DogStatsD
DogStatsD is a metrics aggregation service bundled with the Datadog agent. DogStatsD implements the StatsD protocol and a few extensions (histogram metric type, service checks, events and tagging).
DogStatsD accepts custom metrics,events and service checks over UDP and periodically aggregates them and forwards them to Datadog.
Events
Custom Metrics
Security
API Key
An API key is required by the Datadog Agent to submit metrics and events to Datadog. The API keys are also used by other third-party clients, such as, for example, the Pulumi Datadog resource provider, which provisions infrastructure on the Datadog backend.