We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
Alternatively if the current alerts could be sent with a table which clearly links the alert to the cause (or likely cause), and the severity of the impact. I have mocked up an example table/structure of how we could lay this out (if possible, and perhaps use colour coding to clearly identify the severity/cause/etc so that customers dont need to spend as much time asking questions about the nature of the alert. In cases where the a particular category is still being investigated we could place a "being investigated" response which is then updated in future alerts/responses to customers. Of course the categories of interest will likely be different to what i've outlined but I hope this demonstrates a more detailed and clearly worded type of alerting which would be valuable to many customers.
Category
Response
Alert Type
Slowness/Outage/No impact to production instances/Other
Source/Cause (confirmed or likely)
Bot attack/Azure upgrade/Opti Upgrade/Being investigated/Other
Instances affected
1/Multiple
Other relevant category