FlowFuse
High Availability: Make HA more discoverable
Description
Friction
Unless it's been explicitly requested by a Team/Customer, or seen on our pricing page, the concept of High Availability is difficult to discover within FlowFuse.
We just had a customer hitting CPU limitations at Enterprise, where HA was the solution, and they weren't aware it was an option.
Proposed Solution
Adding a "High Availability: Not Active" option in the "Info" section here.
Epic/Story
No response
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
Only if it includes a link to some docs explaining the limitations (e.g. that flows need to written in a way to make use of this, e.g. mqtt shared subscriptions or both will see all messages)
Can you put the link in here please @hardillb - just so that it's recorded against the issue.
With the Performance feature in place, audit logging of excessive usage, and email notifications sent for excessive usage, this seems like something we can link to for Enterprise customers hitting a limit on a Large instance. I think the solution Joe has proposed gets us part of the way there, but the user will still need more information to understand that High Availability will solve their problem.
The email notifications that already go out for 75% usage should mention that if usage limits are being hit on a Large instance, the next option is High Availability.
@gstout52 as a first iteration as i've proposed here btw this is a size 0.5 item just in case we want this sooner rathe than later