Our main way of doing resource governance is to rely on follower databases. We have a locked down production cluster which doesn't accept any non-production workload and then if anyone else needs access to the data, we have them set up a follower database. It sounds like ADX has a single-region restriction for those follower databases and this is going to put a pretty major kink in our arch. Please consider adding this feature.21 votes
Thanks for the suggestion Ben and others, but due to the latency of doing high frequency calls to storage accounts located in other regions to synchronize the cluster cache, the quality of the service is expected to significantly degrade and thus this scenario is not supported.
If the motivation for follower clusters is to provide high availability and disaster recovery our recommendation is to create two clusters one in each region and duplicate the data ingestion.
Hello, thanks for the suggestion!
A cluster with one node is a dev/test cluster and cannot be turned into a production cluster. We are not planning to support this scenario.
Sorry for the inconvenience,
Do you have any KustoConnection library for .Net Core(BOT) framework?2 votes
The right forum for questions is stack-overflow or other channels. If this is a feature request, please elaborate what is required (it is not clear what is .NET core bot framework)
the EU is using XML for all financial reporting, it would be great if Azure Data Explorer could ingest and flattten the XML data2 votes
There is a parse_xml() function that can be used inside UpdatePolicy. It allows you to ingest data as string into a staging table, and use UpdatePolicy transform string into a dynamic table.
- Don't see your idea?