Skip to content

docs: warn against adding logs inside the logs pipeline #1307

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lym953 merged 2 commits into from
Jul 18, 2026
Merged

docs: warn against adding logs inside the logs pipeline #1307

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
897ebdb
docs(agents): warn against adding logs inside the logs pipeline
lym953 Jul 17, 2026
6a5e8f1
docs(agents): tighten logs-pipeline gotcha wording
lym953 Jul 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,3 +71,15 @@ Event sources
| `appsec/` | Application Security Monitoring |
| `tags/` | Tag extraction and propagation |
| `fips/` | FIPS mode cryptography support |

## Gotchas

### Be careful adding logs inside the logs pipeline

The extension re-ingests its own stdout/stderr as logs, so a line logged while handling a log
(in `logs/` — processor, agent, flusher) feeds back through the same pipeline. In a
per-log-line hot path this self-amplifies into a flood of both CloudWatch and Datadog logs,
worst at `DD_LOG_LEVEL=debug`.

Avoid logging in this area unless necessary; prefer a temporary instrumented build, or surface
signal via a metric instead.
Loading