DEVPROD-8819: make more specific host creation failure event for spawn host outcome #8552
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DEVPROD-8819
Description
The user subscription for previously listened for host creation errors in general, which would notify them when their spawn host fails to start up (e.g. due to insufficient capacity). However, the way the notification infrastructure works that means all host creation errors have to be processed for notifications, even for non-spawn-hosts. This can put strain on the notification system when lots of hosts are failing to start (e.g. because many task hosts are hitting insufficient capacity).
Since we only want to process notifications for spawn hosts failing to be created, I made a more specific error message.
Testing
Documentation
N/A