Metadata API reference

Detailed documentation on the Metadata API

Dapr has a metadata API that returns information about the sidecar allowing runtime discoverability. The metadata endpoint returns among other things, a list of the components loaded and the activated actors (if present).

The Dapr metadata API also allows you to store additional information in the format of key-value pairs.

Note: The Dapr metatada endpoint is for instance being used by the Dapr CLI when running dapr in standalone mode to store the PID of the process hosting the sidecar and the command used to run the application.

Get the Dapr sidecar information

Gets the Dapr sidecar information provided by the Metadata Endpoint.

HTTP Request

  1. GET http://localhost:<daprPort>/v1.0/metadata

URL Parameters

ParameterDescription
daprPortThe Dapr port.

HTTP Response Codes

CodeDescription
200Metadata information returned
500Dapr could not return the metadata information

HTTP Response Body

Metadata API Response Object

NameTypeDescription
idstringApplication ID
actorsMetadata API Response Registered Actor[]A json encoded array of Registered Actors metadata.
extended.attributeNamestringList of custom attributes as key-value pairs, where key is the attribute name.
componentsMetadata API Response Component[]A json encoded array of loaded components metadata.

Metadata API Response Registered Actor

NameTypeDescription
typestringThe registered actor type.
countintegerNumber of actors running.

Metadata API Response Component

NameTypeDescription
namestringName of the component.
typestringComponent type.
versionstringComponent version.

Examples

Note: This example is based on the Actor sample provided in the Dapr SDK for Python.

  1. curl http://localhost:3500/v1.0/metadata
  1. {
  2. "id":"demo-actor",
  3. "actors":[
  4. {
  5. "type":"DemoActor",
  6. "count":1
  7. }
  8. ],
  9. "extended": {
  10. "cliPID":"1031040",
  11. "appCommand":"uvicorn --port 3000 demo_actor_service:app"
  12. },
  13. "components":[
  14. {
  15. "name":"pubsub",
  16. "type":"pubsub.redis",
  17. "version":""
  18. },
  19. {
  20. "name":"statestore",
  21. "type":"state.redis",
  22. "version":""
  23. }
  24. ]
  25. }

Add a custom attribute to the Dapr sidecar information

Adds a custom attribute to the Dapr sidecar information stored by the Metadata Endpoint.

HTTP Request

  1. PUT http://localhost:<daprPort>/v1.0/metadata/attributeName

URL Parameters

ParameterDescription
daprPortThe Dapr port.
attributeNameCustom attribute name. This is they key name in the key-value pair.

HTTP Request Body

In the request you need to pass the custom attribute value as RAW data:

  1. {
  2. "Content-Type": "text/plain"
  3. }

Within the body of the request place the custom attribute value you want to store:

  1. attributeValue

HTTP Response Codes

CodeDescription
204Custom attribute added to the metadata information

Examples

Note: This example is based on the Actor sample provided in the Dapr SDK for Python.

Add a custom attribute to the metadata endpoint:

  1. curl -X PUT -H "Content-Type: text/plain" --data "myDemoAttributeValue" http://localhost:3500/v1.0/metadata/myDemoAttribute

Get the metadata information to confirm your custom attribute was added:

  1. {
  2. "id":"demo-actor",
  3. "actors":[
  4. {
  5. "type":"DemoActor",
  6. "count":1
  7. }
  8. ],
  9. "extended": {
  10. "myDemoAttribute": "myDemoAttributeValue",
  11. "cliPID":"1031040",
  12. "appCommand":"uvicorn --port 3000 demo_actor_service:app"
  13. },
  14. "components":[
  15. {
  16. "name":"pubsub",
  17. "type":"pubsub.redis",
  18. "version":""
  19. },
  20. {
  21. "name":"statestore",
  22. "type":"state.redis",
  23. "version":""
  24. }
  25. ]
  26. }

Last modified September 20, 2021 : Merge pull request #1800 from greenie-msft/gRPC_proxying_video (36dff3c)