Pipeline presets
Embed
<a href="https://watchtowerops.net/docs/pipeline-presets"><img src="https://watchtowerops.net/docs/_api/public/orgs/aa5959cb-1a0b-4a9a-bc9a-913e7ac31cd9/spaces/b7aac181-9916-4805-b253-becc5fd2ca62/pages/3f62d9e6-d872-4679-9019-953550bc58bc/social-card.svg?v=3e7ae33eec8b" alt="Pipeline presets" width="600" height="315"></a>GET /v1/projects/{prj}/pipelines/presets lists the ready-made pipeline configs (also at .../pipelines/packs). Each entry has an id, the signal, a v1 config to start a pipeline from, and, for source presets, what it attaches to by itself.
Attached automatically
For logs, these presets run without any setup on the records they fit:
Preset | Attaches when | or agent integration is |
|---|---|---|
|
|
|
| (library; no service name) |
|
|
|
|
|
|
|
The agent integration is the agent.integration attribute the Watchtower agent sets on logs collected for that integration. A preset only touches records that match; a line it cannot parse passes unchanged. The preset stages run first, before your own pipeline.
To turn this off for a project, set logs.disable_auto_presets to true in the project's logs and traces settings. For a project that already has a saved pipeline the change takes effect with its next pipeline version.