REST API Connector with Azure func

PubSub+ Event Broker
, , ,
1

Hello Guys,
Please have a look into below scenario:-
I have implemented a REST API Connector using the Portal Wizard, which is configured to interact with an HTTP-triggered Azure Function App. This function app includes two queue bindings for processing messages.
Currently, I would like to identify the specific topic subscriptions from which incoming messages originate. However, I’ve encountered a limitation: the REST API Connector does not allow me to specify or filter by individual topic subscriptions.

Could you please advise on how to achieve this filtering within the REST API Connector setup? Anything I can do at func app to see the message properties to identify topics subscriptions where message is published.
Please note Azure func app connector option is not feasible for my scenario.
Any quick guidance or workaround would be greatly appreciated.
Regards,
Swap

2

Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:

Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.

AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

The documentation provided does not contain specific information about identifying topic subscriptions from incoming messages in a REST API Connector connected to an Azure Function App. While there is information about configuring REST connectors to Azure Functions and general information about topic subscriptions, there is no direct mention of how to identify topic subscriptions in this specific scenario.

Here are relevant sources that might help you find the information you’re looking for:

I recommend searching the Solace documentation for more specific information about REST API Connectors and message headers.

3

Hi @swapnil_mahajan

All events in a queue have the original Destination address i.e. the topic where they were published on.

When consuming events via RDPs (REST Delivery Points), the original topic destination isn’t automatically included in the outbound REST request. You need to explicitly configure this using request headers:
To access the Destination property in RDP-delivered messages:

  1. Configure a request header on the queue binding
  2. Use the topic substitution expression ${topic} as the header value

Example configuration

create request-header Original-Topic 
header-value ${topic}

This adds a custom header containing the original topic to every outbound REST request, allowing your REST consumer application to access this information.

You can access this property in the azure function app and use it for processing. You should be able to find it in header properties

Hope this helps.

Regards
Hari

1 Like
4

Hi @Hari_Rangarajan Thanks for reply. Do I need to add ${topic()} both in Request header and substitution expression? Please let me know.
BR, Swap