Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manage multiple AzureWebJobsStorage #214

Open
MarcoTranfaglia opened this issue Oct 14, 2024 · 6 comments
Open

Manage multiple AzureWebJobsStorage #214

MarcoTranfaglia opened this issue Oct 14, 2024 · 6 comments
Labels
question Further information is requested

Comments

@MarcoTranfaglia
Copy link

At the moment the Durable Function Monitor manages one instance of Azure Storage, via Env Var: AzureWebJobsStorage.
Would it be possible to have more than one Azure Storage connection?
Configuration can be achieved (for example) via comma separated values of connection strings

So in the UI, it should be added a combo box that makes possible to choose between different storages configured,
(and for each storage we can have multiple Task Hub choices)

Image

@scale-tone
Copy link
Contributor

Hey @MarcoTranfaglia ,

DfMon InProc does supports multiple Storage accounts, via DFM_ALTERNATIVE_CONNECTION_STRING_XXX config settings. Note though, that those alternative connection strings can only be access key-based (not identity-based).

DfMon Isolated does not support those, and is unlikely to ever support. After all, you can always run multiple DfMon instances on the same App Service Plan - and that would eliminate the cost concern (if that is the concern). If there're any other concerns - please, share.

DfMon as a VsCode ext automatically shows you all Task Hubs in all Storage accounts visible to you, so that is also an option.

@scale-tone scale-tone added question Further information is requested and removed Needs: Triage 🔍 labels Oct 14, 2024
@scale-tone
Copy link
Contributor

@MarcoTranfaglia , does that answer your question?

@MarcoTranfaglia
Copy link
Author

Hi! It anwers my question, but unluckly does not solve our scenario .
It's not only a mattern of costs (as you said, we are using the Same Service Plan).

Since we have many Functions App (with different storage account) we wanted to have 1 single instance of DFM that monitors multiple functions.

@scale-tone
Copy link
Contributor

So, why not using one single instance of DfMon InProc?

@MasterKuat
Copy link

Hi @scale-tone InProcess worker mode is in path of deprecation : https://azure.microsoft.com/fr-fr/updates/retirement-support-for-the-inprocess-model-for-net-apps-in-azure-functions-ends-10-november-2026

I'm in same situation than Marco, should be far more user friendly if you have 1 DfMon for all function.
Is there any technical issue with multiple Storage accounts in Isolated mode ?

@mdddev
Copy link

mdddev commented Dec 12, 2024

So, why not using one single instance of DfMon InProc?

I have the same scenario, one dfm instance to monitor multiple taskhubs on different storage accounts. For security purposes, these accounts have their access keys disabled. As you stated earlier, in-proc does dfmon does not support identity-based storage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants