Skip to content

Comments

docs: add section for dapr agents regarding default values to cover default agent statestore naming for auto attachment#4979

Open
CasperGN wants to merge 13 commits intodapr:v1.16from
CasperGN:docs/agents-defaults
Open

docs: add section for dapr agents regarding default values to cover default agent statestore naming for auto attachment#4979
CasperGN wants to merge 13 commits intodapr:v1.16from
CasperGN:docs/agents-defaults

Conversation

@CasperGN
Copy link
Contributor

Please follow this checklist before submitting:

  • Commits are signed with Developer Certificate of Origin (DCO - learn more)
  • Read the contribution guide
  • Commands include options for Linux, MacOS, and Windows within tabpane
  • New file and folder names are globally unique
  • Page references use shortcodes instead of markdown or URL links
  • Images use HTML style and have alternative text
  • Places where multiple code/command options are given have tabpane

In addition, please fill out the following to help reviewers understand this pull request:

Description

Add "Default Settings" section for dapr agents explaining the default attachment to statestores and pubsub if none is supplied.

Issue reference

N/A

…efault agent statestore naming for auto attachment

Signed-off-by: Casper Nielsen <casper@diagrid.io>
@CasperGN CasperGN requested review from a team as code owners December 16, 2025 14:26
CasperGN and others added 3 commits January 29, 2026 10:51
…-concepts.md

Co-authored-by: Mark Fussell <markfussell@gmail.com>
Signed-off-by: Casper Nielsen <whopsec@protonmail.com>
…untimeconf & secrets

Signed-off-by: Casper Nielsen <casper@diagrid.io>
Copy link
Contributor

@marcduiker marcduiker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small clarification is suggested

marcduiker and others added 2 commits February 13, 2026 13:44
…-concepts.md

Co-authored-by: Marc Duiker <marcduiker@users.noreply.github.com>
Signed-off-by: Casper Nielsen <whopsec@protonmail.com>
Copy link
Contributor

@marcduiker marcduiker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@msfussell msfussell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@CasperGN @bibryam - A few comments on formatting


### Default settings

Dapr Agents comes with pre-set sensible defaults on different settings. Descriptions of each of them are below.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Dapr Agents comes with pre-set sensible defaults on different settings. Descriptions of each of them are below.
Dapr Agents comes with pre-set defaults on different settings. Descriptions of each of them are below.


#### State store

By ensuring the following statestores with these metadata names are present, the Dapr Agent will resolve these from the Dapr Metadata API:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
By ensuring the following statestores with these metadata names are present, the Dapr Agent will resolve these from the Dapr Metadata API:
By ensuring the following statestores with these metadata names are present, Dapr Agents resolves these from the Dapr Metadata API:

The default key is set to the agents name in lowercase with space replaced by `-` with the `-session` suffix.
- `agent-runtimestatestore`: Agent runtime configuration
The statestore is loaded with key `agent_runtime` expecting field `data` containing a dictionary (i.e., `{ "key": "value" }`)
currently the agent supports auto-instrumenting itself with OpenTelemetry by setting the following available options:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
currently the agent supports auto-instrumenting itself with OpenTelemetry by setting the following available options:
Dapr Agents supports auto-instrumenting with OpenTelemetry by setting the following environment variables:

| OTEL_TRACING_EXPORTER | "otlp_grpc"/"otlp_http"/"console" | Which exporter to use. Default: "console" |


For `DurableAgent` you can also rely on the workflow statestore:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For `DurableAgent` you can also rely on the workflow statestore:
For `DurableAgent` you can also set on the workflow statestore:


#### Pub/Sub

By ensuring the following pubsub component with appropriate naming is present, the Dapr Agent will resolve it from the Dapr Metadata API:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
By ensuring the following pubsub component with appropriate naming is present, the Dapr Agent will resolve it from the Dapr Metadata API:
By ensuring the following pubsub component with appropriate naming is present, Dapr Agents resolves it from the Dapr Metadata API:


#### Secret store

By ensuring the following secret component with approproate naming is present, the Dapr Agent will resolve it from the Dapr Metadata API:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
By ensuring the following secret component with approproate naming is present, the Dapr Agent will resolve it from the Dapr Metadata API:
By ensuring the following secret component with appropriate naming is present, Dapr Agents resolves it from the Dapr Metadata API:

By ensuring the following secret component with approproate naming is present, the Dapr Agent will resolve it from the Dapr Metadata API:

- `agent-secretstore`: Secrets for agent runtime
The agent will bulk load all secrets and insert them into it's runtime secrets. The currently supported secrets are:
Copy link
Member

@msfussell msfussell Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The agent will bulk load all secrets and insert them into it's runtime secrets. The currently supported secrets are:
The agent bulk loads all secrets and inserts them into it's runtime secrets. The supported secrets are:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants