Create Resources with Venn

Venn sets up data sources, alert destinations, forwarders, source extensions, replays, and Fleet agents by pre-filling the real create forms for you to review and save.

All of Venn's setup flows follow one pattern, so they all feel the same:

1. You describe what you want in chat.

2. Venn stages a draft and shows a card in the conversation.

3. The real create form opens pre-filled with Venn's draft.

4. You review, complete, and save. Anything secret (passwords, tokens, API keys) is left blank for you to enter directly in the form. Secrets never pass through the chat.

What you can set up this way:

Resource	Example prompt
Data sources	"Add a Prometheus data source for our staging cluster"
Alert destinations	"Set up a Slack destination for the on-call channel"
Forwarders	"Create a Datadog forwarder for the prod namespace"
Source extensions (input plugins)	"Set up a Kafka source extension for the events topic"
Log replays	"Replay yesterday's payment logs between 2 and 3 pm to the new forwarder"
Fleet agent install	"Install a telemetry agent on Linux for the prod namespace"
Fleet configurations	"Draft an agent configuration that collects nginx access logs"
Queries and SLOs	See Dashboards and queries and Alerts and SLOs

Fleet management beyond setup

Once agents exist, Venn manages them conversationally too:

• "List my fleet agents", "which agent types are available?"

• "Restart the agents in the staging namespace" (start, stop, and restart)

• "Update the nginx collection config" and assign packages to agents

Forwarders beyond setup

• "List my forwarders and where they send data"

• "Make S3-archive the default forwarder"

• "Route checkout logs in prod to the Splunk forwarder", "remove that routing"

Forwarders whose configuration includes credentials are created through the pre-filled form flow above, where you enter the secret yourself. Non-credentialed forwarder types can be created and updated directly in the conversation.