Preparing for Planned Maintenance

[jpd1]

Is your feature request related to a problem? Please describe.

Within Azure Spring Cloud, we sometimes find after a planned maintenance that some of our apps seem to be impacted by planned maintenance. We have an alert setup on the resource health, so we're notified of any degraded apps after the event.

Additionally, we are looking to setup alerts of planned application lifecycle events and understand that the underlying Kubernetes version is updated every 2-4 months. However, the planned maintenance description does not provide any details on the change or what functionality that has changed within Azure Spring Cloud. This makes it tricky to proactively plan for any planned maintenance.

Describe the solution you'd like

Further information within the description as to what change is being planned so we can proactively plan for the maintenance in advance. It would also be good it we had control as to when it is applied into different environments. For example, apply the planned maintenance into a non-production environment first.

Describe the Customer Impact

Degraded apps after a planned maintenance.

[allxiao]

We are currently working on the maintenance window design to allow the user to define preferred time window for the maintenance tasks.

Before this is ready, for the current maintenance operations, if you have special requirement (For example, apply the planned maintenance into a non-production environment first.), please reach out to [email protected] and we can further follow up with you on the preferred schedule.

Thanks!

[bryandx]

I tried to send an email to [email protected] about this but the email was rejected:

Your message couldn't be delivered to multiple recipients.
The groups only accept messages from people in their organization or on their allowed senders list, and your email address isn't on the lists.

Couldn't deliver to the following groups:
[email protected], [email protected], [email protected]

[allxiao]

Hi @bryandx

Sorry that it seems the email group has some policies that prohibits external emails.

Could you please fire a ticket so that the support team can take care of this, and forward to the maintenance group.
You can find the "New Support Request" link at the bottom of the service's actions blade.

Thanks,

[allxiao]

You can send email to [email protected], which is in the issue template and accepts external emails.
Sorry for the error messages delivered earlier.

[bryandx]

A couple of weeks ago I emailed ***@***.******@***.***> with our planned maintenance needs. Do I still need to create support ticket for it? Thanks, Bryan From: Menghua Xiao ***@***.***> Sent: Friday, May 19, 2023 12:16 AM To: Azure/Azure-Spring-Apps ***@***.***> Cc: Bryan Dixon ***@***.***>; Mention ***@***.***> Subject: [EXT] Re: [Azure/Azure-Spring-Apps] Preparing for Planned Maintenance (Issue #41) Hi @bryandx<https://github.com/bryandx> Sorry that it seems the email group has some policies that prohibits external emails. Could you please fire a ticket so that the support team can take care of this, and forward to the maintenance group. You can find the "New Support Request" link at the bottom of the service's actions blade. [Image removed by sender. image]<https://user-images.githubusercontent.com/423695/239435608-b2c6d243-7ae8-4c67-9c35-d5c0a608e0f5.png> Thanks, - Reply to this email directly, view it on GitHub<#41 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AILT76DEENWJMDI72H627NLXG3XZLANCNFSM6AAAAAAWCEGPZU>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[zhiszhan]

A couple of weeks ago I emailed @.@.> with our planned maintenance needs. Do I still need to create support ticket for it? Thanks, Bryan From: Menghua Xiao @.> Sent: Friday, May 19, 2023 12:16 AM To: Azure/Azure-Spring-Apps @.> Cc: Bryan Dixon @.>; Mention @.> Subject: [EXT] Re: [Azure/Azure-Spring-Apps] Preparing for Planned Maintenance (Issue #41) Hi @bryandxhttps://github.com/bryandx Sorry that it seems the email group has some policies that prohibits external emails. Could you please fire a ticket so that the support team can take care of this, and forward to the maintenance group. You can find the "New Support Request" link at the bottom of the service's actions blade. [Image removed by sender. image]https://user-images.githubusercontent.com/423695/239435608-b2c6d243-7ae8-4c67-9c35-d5c0a608e0f5.png Thanks, - Reply to this email directly, view it on GitHub<#41 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AILT76DEENWJMDI72H627NLXG3XZLANCNFSM6AAAAAAWCEGPZU. You are receiving this because you were mentioned.Message ID: @.***>

Tickets is the source of truth. If you have a request for a specific resource or subscription, filing a ticket is the best channel with proper SLA and tracking.

Thanks for using Azure Spring Apps!

[allxiao]

@bryandx If your problem was resolved with emails or in other communication channels earlier, no need to create another support ticket.
If you have any other problems, feel free to fire a ticket and it will be handled and well tracked.

Thanks

[vermegi]

Seems to be available now in preview? https://learn.microsoft.com/en-us/azure/spring-apps/enterprise/how-to-configure-planned-maintenance?tabs=Azure-portal

[zhiszhan]

Yes, it's in preview. We are planning to GA it. @vermegi