Skip to content

Conversation

@davidmrdavid
Copy link
Member

As in title, looking to provide better diagnostics in the case of partition timeouts. Happy to start taking feedback at this stage.

/// <summary>
/// Optionally, a name for an Azure Table to use for publishing load information. If set to null or empty,
/// then Azure blobs are used instead. The use of Azure blobs is currently not supported on consumption plans, or on elastic premium plans without runtime scaling.
/// then Azure blobs are used instead.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this still accurate?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question. I don't quite remember, this was a limitation of the scale controller (couldn't read anything other than Azure Tables). Not sure if we changed that since then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants