datadog
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| datadog [2025/12/30 16:52] – Roman Sheydvasser | datadog [2026/03/30 20:32] (current) – [Export Resources From a Datadog Account] Roman Sheydvasser | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| This table organizes Datadog topics by priority level—core, | This table organizes Datadog topics by priority level—core, | ||
| - | | Topic | Priority | | + | | **Datadog |
| | Tagging | 1 - Core | | | Tagging | 1 - Core | | ||
| | Logs | 1 - Core | | | Logs | 1 - Core | | ||
| Line 83: | Line 83: | ||
| * https:// | * https:// | ||
| * https:// | * https:// | ||
| + | |||
| + | ===== Export Resources From a Datadog Account ===== | ||
| + | |||
| + | https:// | ||
| + | |||
| + | The `import` command is somewhat misleading. It refers to reading the specified resources from a Datadog organization and then storing them locally as JSON files. | ||
| + | |||
| + | < | ||
| + | $ datadog-sync import \ | ||
| + | --source-api-key=" | ||
| + | --source-app-key=" | ||
| + | --source-api-url=" | ||
| + | </ | ||
datadog.1767113549.txt.gz · Last modified: by Roman Sheydvasser
