Hello, I am using dapr components to publish and subscribe events between services of single connection string (event hub). is that possible to have different connection string (eventhubs) in the same dapr ? so that instead of creating multiple container services based on connection string, i can use same dapr component.

Hello SriRaghavendran Prabhakaran To configure Dapr in Azure Container Apps, you can create a dapr.yaml file and include it in your container image. Here's an example of a dapr.yaml file that configures two Event Hubs components: apiVersion: dapr.io/v1alpha1 kind: Configuration metadata: name: pubsub-config spec: pubsub: - name: eventhub1 pubsubType: azure.eventhubs metadata: - name: connectionString value: - name: consumerID value: - name: eventhub2 pubsubType: azure.eventhubs metadata: - name: connectionString value: - name: consumerID value: You can then reference the pubsub name in your .NET Core web API's by using the Dapr SDK. Here's an example of how you can publish an event to a specific topic using the Dapr SDK: using Dapr.Client; public class MyController : ControllerBase { private readonly DaprClient daprClient; public MyController(DaprClient daprClient) { this.daprClient = daprClient; } [HttpPost("publish/{pubsubName}/{topic}")] public async Task PublishEvent(string pubsubName, string topic, [FromBody] object data) { await daprClient.PublishEventAsync(pubsubName, topic, data); return Ok(); } } In this example, we're using the DaprClient to publish an event to a specific topic. The pubsubName parameter specifies the name of the Event Hubs component, and the topic parameter specifies the name of the topic to publish to. Similarly, you can use the DaprClient to subscribe to events from a specific topic. Hope this helps.

Dapr component - Microsoft Q&A

Accepted answer

vipullag-MSFT 26,211 Reputation points

2023-11-15T05:57:03.3966667+00:00
Hello SriRaghavendran Prabhakaran

To configure Dapr in Azure Container Apps, you can create a dapr.yaml file and include it in your container image. Here's an example of a dapr.yaml file that configures two Event Hubs components:

apiVersion: dapr.io/v1alpha1 kind: Configuration metadata: name: pubsub-config spec: pubsub: - name: eventhub1 pubsubType: azure.eventhubs metadata: - name: connectionString value: - name: consumerID value: - name: eventhub2 pubsubType: azure.eventhubs metadata: - name: connectionString value: - name: consumerID value:

You can then reference the pubsub name in your .NET Core web API's by using the Dapr SDK. Here's an example of how you can publish an event to a specific topic using the Dapr SDK:

using Dapr.Client; public class MyController : ControllerBase { private readonly DaprClient daprClient; public MyController(DaprClient daprClient) { this.daprClient = daprClient; } [HttpPost("publish/{pubsubName}/{topic}")] public async Task PublishEvent(string pubsubName, string topic, [FromBody] object data) { await daprClient.PublishEventAsync(pubsubName, topic, data); return Ok(); } }

In this example, we're using the DaprClient to publish an event to a specific topic. The pubsubName parameter specifies the name of the Event Hubs component, and the topic parameter specifies the name of the topic to publish to.

Similarly, you can use the DaprClient to subscribe to events from a specific topic.

Hope this helps.
Please sign in to rate this answer.
SriRaghavendran Prabhakaran 300 Reputation points

2023-11-21T07:09:07.38+00:00

thanks vipullag-MSFT.

can you please suggest me on the below error. I am getting this error recently and subscribe is not working.

ime="2023-11-21T06:39:41.860461461Z" level=error msg="error occurred while beginning pubsub for topic pubsub on component pubsubtest: failed to subscribe to topic pubsub: error trying to establish a connection: unable to connect to the checkpoint store: unable to connect to the checkpoint store: PUT https://pubsubstorage.blob.core.windows.net/pubsub\n--------------------------------------------------------------------------------\nRESPONSE 401: 401 Server failed to authenticate the request. Please refer to the information in the www-authenticate header.\nERROR CODE: InvalidAuthenticationInfo\n--------------------------------------------------------------------------------\n\ufeff<?xml version="1.0" encoding="utf-8"?><Error><Code>InvalidAuthenticationInfo</Code><Message>Server failed to authenticate the request. Please refer to the information in the www-authenticate header.\nRequestId:4709fcd9-201e-0000-4945-1c3109000000\nTime:2023-11-21T06:39:41.7383273Z</Message><AuthenticationErrorDetail>Issuer validation failed. Issuer did not match.</AuthenticationErrorDetail></Error>\n--------------------------------------------------------------------------------\n" app_id=servicetwo instance=servicetwo-app--d5f69u5-64645dccc8-m6szw scope=dapr.runtime type=log ver=1.11.5-msft.1

vipullag-MSFT 26,211 Reputation points

2023-11-21T08:14:41.2666667+00:00

Hello SriRaghavendran Prabhakaran
The error message indicates that there is an authentication issue with the checkpoint store for the pubsub component. The error message suggests that the server failed to authenticate the request and that the issuer validation failed.

To resolve this issue, you should check the following:

-Check that the connection string for the checkpoint store is correct and that it has the necessary permissions to access the storage account.

-Check that the storage account key is correct and that it has not expired.

-Check that the storage account name is correct and that it matches the name of the storage account that you are using.

-Check that the issuer of the authentication token matches the expected issuer.

If you have verified that the above items are correct, you may need to regenerate the storage account key and update the connection string in your Dapr configuration file.

Hope this helps.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Dapr component

0 additional answers

Your answer