Notifications on Session Host Limits

Thank you for submitting your feature request—we truly value input from our community.

Next steps:
     • We will review your request and update its status as it progresses through our evaluation process.
     • If any clarification is needed, we'll follow up with you directly in the comments.

We also encourage the community to influence our decision through comments, votes, and feedback.

I like the premise of the notification condition and thought I'd weigh in.

Can you provide more context on the details of the deployment, that would warrant this notification?   I ask only because my typical deployments, there is no need to be worried about tickets, but again, my typical might quite different from yours.

- If auto-scale is enabled, it could be tweaked with metric triggers that have the new session brought online automatically.   There might be a concerning delay if the session host needs to be created, vs just powered on.  Depending on the overall size of the environment, we typically ensure that even at normal full capacity, there is always an extra session host created but left powered off - so that there is always some easy to have online buffer

- If there is a reason not to use auto-scale, that is fine - but seems to chip away a significant value-add proposition that Nerdio Manager brings.   I have a few environments like that, but after a few years now we still haven't had a need to add a session host, we just scale the host up.   All very small deployments where a single session host is still cost effective. 

- Having thought through the topic a bit, I would propose a twist on the original request for Product to consider.   What about a notification condition that tells you when approaching, or having reached, the host pool user limit.   Auto-scale is capable of quickly bringing hosts online, and has the awesome ‘burst’ feature, allowing your pool to temporarily exceed the configured limit to meet unexpected demand.   But a condition that would allow us to see that the org is about to, or has met that limit unexpectedly would be valuable to ensure that ever elusive “quality user experience”.

As a fellow partner, i appreciate the idea and look forward to seeing what the Product team might consider doing with it.