Datadog Concepts: Difference between revisions
| Line 25: | Line 25: | ||
==Application Key== | ==Application Key== | ||
{{External|https://docs.datadoghq.com/account_management/api-app-keys/#application-keys}} | {{External|https://docs.datadoghq.com/account_management/api-app-keys/#application-keys}} | ||
Application keys, in conjunction with the organization’s [[#API_Key|API key]], give users access to Datadog’s programmatic API. Application keys are associated with the user account that created them and by default have the permissions and scopes of the user who created them. | |||
Revision as of 05:45, 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. API keys are unique to an organization.
Application Key
Application keys, in conjunction with the organization’s API key, give users access to Datadog’s programmatic API. Application keys are associated with the user account that created them and by default have the permissions and scopes of the user who created them.