Enable chaining reactions as sources

[psmulovics]

Overview of feature request

Enable Drasi reactions to become sources for other Drasi queries. This would enable queries to be composed based on system owner knowledge of the system.

Acceptance criteria

• A new source is added that is able to take a Drasi query (signalR endpoint) and serve it up as a source

Additional context

No response

Would you like to support us?

• Yes, I would like to support you

[agentofreality]

Hello @psmulovics,

We have discussed this idea a few times since Drasi first started and it seems like it could be useful, but so far we have not identified a compelling use case or had a customer that really needed it, so it has never been prioritized over other work. I suspect it may become more important as people start to use Drasi more extensively, but for now there are workarounds using intermediary stores/queus i.e. Source -> Query -> Reaction -> Store/Queue -> Source -> Query -> Reaction -> ...

Please let us know if you have a specific use case that you need this feature for and if the lack of this feature is hampering your ability to adopt Drasi. If either are true, we would be happy to prioritize this and work with you to figure out details.

[psmulovics]

Imho the use case is relevant to enterprises where log processing knowledge is siloed in the teams, and each would have their own 'self contained block' of Drasi running.