log-configuration

Manage Datadog log archives, pipelines, indexes, and custom forwarding destinations via the pup CLI.

5|2|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/lauhon/pi --skill log-configuration-lauhon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log-configuration
Source: https://github.com/lauhon/pi/tree/main/skills/log-configuration
Command: npx skills add https://github.com/lauhon/pi --skill log-configuration-lauhon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing Datadog log infrastructure—archives, processing pipelines, indexes, and external forwarding destinations—requires navigating complex APIs and configurations. This Skill provides guided, command-driven management of the entire log configuration lifecycle through the pup CLI. ## Core Features & Use Cases - Log Archives: Create, update, and order archives to S3, GCS, or Azure Blob Storage, including rehydration settings and storage class selection. - Log Pipelines: Build processing pipelines with 15+ processor types (grok parser, remappers, GeoIP, lookup, arithmetic) to parse and enrich logs. - Log Indexes: Configure indexes with retention periods, exclusion filters, daily limits, and priority ordering. - Custom Destinations: Forward logs to HTTP endpoints, Splunk HEC, Elasticsearch, or Microsoft Sentinel with flexible authentication and tag filtering. - Logs RBAC: Create restriction queries and grant roles to control which users can access specific log data. - Use Case: Set up a production logging strategy by creating an S3 archive for compliance, a grok pipeline to parse Nginx logs, a 30-day retention index with debug-log exclusion, and Splunk forwarding for the security team. ## Quick Start Ask the agent to list all current log archives and indexes, then create an S3 archive for production logs with a 30-day retention index.

Frequently Asked Questions about log-configuration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Datadog log archive to S3?

Use the pup logs archives create command with destination-type s3, specifying the bucket, path, AWS account ID, and IAM role name. You can optionally add rehydration tags, max scan size, and an S3 storage class like GLACIER_IR.

How do I parse unstructured logs with a Datadog pipeline?

Create a pipeline with a grok-parser processor that matches your log format using grok patterns against the message field. Combine it with date-remapper, status-remapper, and service-remapper processors to set official log attributes.

What log destinations does Datadog custom forwarding support?

Custom destinations support generic HTTP endpoints with basic auth or custom headers, Splunk HEC with access tokens, Elasticsearch with optional index rotation, and Microsoft Sentinel via data collection endpoints and rules.

Can I restrict which logs specific users can see in Datadog?

Yes, use logs restriction queries to define log query filters, then grant roles to those queries. Users with restriction queries only see matching logs across Explorer, Live Tail, rehydration, and dashboards.

Why can't I reuse a deleted Datadog index name?

Index deletion is permanent and the name cannot be reused afterward. Before deleting an index, confirm you will not need the name again, and consider updating the index configuration instead.

What permissions are required to manage Datadog log configuration?

You need logs_read_config for reading configuration, logs_write_archives for archives, logs_modify_indexes for indexes, and logs_write_pipelines for pipelines. Set DD_API_KEY, DD_APP_KEY, and DD_SITE environment variables for the pup CLI.