Re-deploy cloud service to extended, how to redirect traffic ?

Vigan Vula 0

Hi
Cloud services(classic) became end of life as of September 1st, the only upgrade option i had was re-deploying to extended support since other methods did not quite work for me(another story).

Looking into Azure I see now traffic going to both services but when i try and shut down cloud service(classic) telemetry does not work.
How can i troubleshoot and redirect traffic to the new upgraded cloud services(extended support) ?

Akshay kumar Mandha 1,040 Reputation points Microsoft Vendor

2024-09-17T16:26:09.41+00:00

Hi Vigan Vula,
Welcome to the Microsoft Q&A Platform. Thank you for posting your query here. We are looking into it and will get back to you soon.

1 answer

Akshay kumar Mandha 1,040 Reputation points Microsoft Vendor

2024-09-18T09:39:03.9+00:00

Hi Vigan Vula,

Thank you for your patience while we are reviewing your issue.

Based upon your query, To shut down telemetry, could you please try below troubleshooting steps

1.Check the configuration settings in the Azure portal for the classic Cloud Service and ensure all endpoints and monitoring settings are disabled. If you can't shut it down directly, consider stopping the service or removing any dependencies still sending data.

2.To redirect traffic to the upgraded service, update DNS records to point to the new Cloud Service (Extended Support). Ensure that all application configurations, connection strings, and environment variables are updated to the new service endpoint. Additionally, use Azure Traffic Manager or a load balancer to manage traffic effectively, and communicate with users to make sure they are aware of the new endpoint.

If you found helpful, Could you please click an accepting the answer and "Upvote" on my post to help increase visibility of this question for other members of the Microsoft Q&A community.
Please sign in to rate this answer.
Akshay kumar Mandha 1,040 Reputation points Microsoft Vendor

2024-09-19T11:20:25.29+00:00

Hi Vigan Vula,
I wanted to follow up If you had chance to please review my answer If you found helpful, Could you please click an accepting the answer and "Upvote" on my post to help increase visibility of this question for other members of the Microsoft Q&A community.

Akshay kumar Mandha 1,040 Reputation points Microsoft Vendor

2024-09-20T11:37:31.1066667+00:00

Hi Vigan Vula,
Just wanted to check If you had chance to please review my answer If you found helpful, could you please click an accepting the answer and "Upvote" on my post to help increase visibility of this question for other members of the Microsoft Q&A community.
Thank you.!

Vigan Vula 0 Reputation points

2024-09-21T13:40:27.48+00:00

I shut down cloud service (classic).

I need some details on the second point.

Is there any guide on how to update the DNS records to point to the new Cloud Service (extended support) ?

Could you be a bit more concrete with steps I need to take ?

To give you a bit more insight, on the cloud service classic, I have a Public Ip address and a site url (http://<name>.cloudapp.net/).

Let me know if you need any details of the application.

Summary:

I redeployed keeping same configuration the cloud service (extended).

I shut down the cloud service (classic)

Observing cloud service(extended) CPU and other metrics (network in and out) stay stable after shut down of classic.

I get a lot of 400 status code errors looking into app insights after this shut down.

Enable back cloud service (classic), things start working again.

Akshay kumar Mandha 1,040 Reputation points Microsoft Vendor

2024-09-23T14:09:27.47+00:00

Hi Vigan Vula,
Thank you getting back to us
I understand you are concern you are unable find out the issue it is working with old classic service but not for the new extended, there are several issues might cause service. First, check your DNS provider to ensure the records are updated to the new public IP address of your new service. Also, verify that your application configurations, connection strings, and environment variables are all aligned with the new endpoint.

To address the 400 status code errors in App Insights, ensure that any URLs or endpoints in your application are correctly referencing the new service. Please refer this document for migrating

If you found helpful, Could you please click an accepting the answer and "Upvote" on my post to help increase visibility of this question for other members of the Microsoft Q&A community.

Vigan Vula 0 Reputation points

2024-09-24T07:26:10.4066667+00:00

Thanks for the answer, I did another redeploy and now works but is super slow (e.g. telemetry is received with delays), I have a service bus trigger for the cloud service.
Do you know what could be the reason for this?

Akshay kumar Mandha 1,040 Reputation points Microsoft Vendor

2024-09-24T16:21:36.83+00:00

Hi Vigan Vula,
Thank you for getting back to us. We are looking into it and will give more info on your query regarding the issue and will get back to you soon.

Vigan Vula 0 Reputation points

2024-09-25T07:11:40.6166667+00:00

Delay is a couple of seconds to minute late, thank you.

Vigan Vula 0 Reputation points

2024-09-25T07:56:01.14+00:00

A little more context.
The cloud service (extended support) is on Standard A2_v2, CPU consumption is stable at 11.6% and available memory (bytes) 3GB.
Cloud service(worker role) is processing telemetry from service bus. What i tried is restart a couple of times.
Previous cloud service(classic) which is now stopped was processing data in 1 second (how it is suppose to), cloud service extended delays as mentioned to seconds and minute.

Akshay kumar Mandha 1,040 Reputation points Microsoft Vendor

2024-09-25T10:44:27.4933333+00:00

Hi Vigan Vula,
Thanks for patience while reviewing the issue & providing more context, I'm glad to hear as you said that service operational is working But I understand that you're experiencing delays with telemetry data processing. Based on the information, it seems that the CPU consumption and available memory are within acceptable limits, which reduces the likelihood of resource constraints being the primary cause of the delay.

Given that the previous cloud service (classic) was processing data in 1 second, I suspect that there might be some configuration or setup differences between the two services that could be contributing to the delay.

First, check that the Service Bus configuration matches between the old and new cloud services. Look at the queue size, message size, and any throttling or rate limiting settings.

Next, review the Worker Role setup to make sure it’s correctly processing telemetry data from the Service Bus. Pay attention to the instance count, scaling settings, and any custom configurations you might have.

Finally, take a closer look at the telemetry data processing pipeline to spot any bottlenecks or inefficiencies. It’s also a good idea to check the logging and monitoring
settings for any errors or warnings that could help pinpoint the cause of the delays.
Please refer this document for performance service bus

If you found helpful, could you please click an https://video2.skills-academy.com/en-us/answers/support/accept-answer and "Upvote" on my post to help increase visibility of this question for other members will get to know about this information in the Microsoft Q&A community.

Akshay kumar Mandha 1,040 Reputation points Microsoft Vendor

2024-09-26T13:05:22.1033333+00:00

Hi Vigan Vula,
Is that my previous comment helpful for you please let me know. If "yes" means, please click an accepting the answer and "Upvote" on my post. If you have any query tag me in comment

Akshay kumar Mandha 1,040 Reputation points Microsoft Vendor

2024-09-27T13:36:28.8533333+00:00

Hi Vigan Vula,
Is that issue resolve just want to check please let me know if have any doubt tag me in comment

Vigan Vula 0 Reputation points

2024-10-07T11:05:26.4366667+00:00

Configurations are the same (since the redeploy from VS i did not change any configs), I checked in Azure and the only difference with extended is that now with extended we need to have Virual Network(which was created by default for me). I do not have any custom DNS names, so i am using the default Azure ones.
On extended message are coming with long delay.

Akshay kumar Mandha 1,040 Reputation points Microsoft Vendor

2024-10-07T18:38:08.8966667+00:00

Hi Vigan Vula,
Thanks for again getting back to us
Based on your query, the virtual Network setup might be impacting performance. try checking for any network latency issues and making sure the services are communicating properly within the Virtual Network. Also, look at the security group settings that could affect traffic flow. Reviewing scaling settings and diagnostic logs might help pinpoint any bottlenecks causing the delays.

If you found helpful, Above information could you please click an https://video2.skills-academy.com/en-us/answers/support/accept-answer and "Upvote" on my post to help increase visibility of this question for other members will get to know about this information in the Microsoft Q&A community.

Akshay kumar Mandha 1,040 Reputation points Microsoft Vendor

2024-10-08T17:24:53.92+00:00

Hi Vigan Vula,
Just, I wanted to check on my previous response review, please let us know ping me in comment if you any further query

Please click an "accept the answer" & "Upvote" If the information was helpful for you

Vigan Vula 0 Reputation points

2024-10-14T09:40:54.7466667+00:00

Hmm not really helpful in this case, what are the steps to get specific help on this besides the forum ?

Vigan Vula 0 Reputation points

2024-10-14T13:18:41.3366667+00:00

I have another lead to what this might happen and that is.
When using VS to deploy cloud service(extended) Azure creates associatate Virtual Network, Load balancer and Public ip.
Load balancer by default is created as "Classic" which can cause problem as the SKU on Public Ip address resource is basic.

Akshay kumar Mandha 1,040 Reputation points Microsoft Vendor

2024-10-14T17:30:54.25+00:00

Hi Vigan Vula,
I understand your concerns about the Classic Load Balancer and the Basic Public IP. Based on your updates, it seems like switching to a Standard Load Balancer could really help improve performance. You might also want to change your Public IP to Standard, as that can handle traffic better.

It would be good to check your deployment settings in Visual Studio, too, to make sure everything is configured to use Standard resources by default. After you make these changes, keep an eye on the performance to see if things get better.

Vigan Vula 0 Reputation points

2024-10-17T12:45:50.1366667+00:00

Well turns out only Basic SKU for Public IP is supported for cloud service(extended support). Do you know where else can i turn for help on this issue ?

Akshay kumar Mandha 1,040 Reputation points Microsoft Vendor

2024-10-17T19:15:05.06+00:00

Hi Vigan Vula,
Based on your comment
I understand that there are some limitations with the Standard SKU, and that it may not work for your setup. The Basic SKU for Public IP is supported for cloud services (extended support), is that correct? If it is "yes" means, can you try to adjust your setup to make it compatible with Standard SKU? It would be a good idea to start using Standard SKU for your Public IPs soon to avoid any issues later on.

Please double-check your current setup to see if it works well with Standard SKU. Give it a try and check if it's possible or not. If it does work, that’s great! if you still can’t make it work, you can reach out to Microsoft Support and raise a ticket for assistance.

Let me know how it goes or if you need any more help!

Vigan Vula 0 Reputation points

2024-10-18T14:34:35.05+00:00

Cloud service (extended support) support Basic SKU only which is also coming from official documentation, https://video2.skills-academy.com/en-us/azure/cloud-services-extended-support/deploy-portal <- point no. 6.
Could you please inform if we can raise a ticket on Microsoft Support for free ?

Akshay kumar Mandha 1,040 Reputation points Microsoft Vendor

2024-10-18T17:46:35.0666667+00:00

Hi Vigan Vula,
Thanks for the update on this post

The basic plan is free but has limited features, while other plans offer more comprehensive support options. You can check the link provided for more details on the available support plans.
https://azure.microsoft.com/en-us/support/plans/

And, to check the current support plan for your Azure Subscription, you can follow these steps: In the Azure Portal, search for "Help + Support" services. This will allow you to view your current support plan, whether it's Basic or Standard. Additionally, you can check the pricing and features of each plan to determine which one best suit your needs. If you need to upgrade or change your support plan, you can do so through the Azure Portal or by contacting Azure Support directly. you can see the image below for your reference

If you're considering the support plan, it would be a great way to address your product queries and any related issues. If you have any questions or need assistance, please don't hesitate to reach out, we are always here to help!

Also, could you please accept an answer and give it an "Upvote"? This would really help other community members who might be facing the same issue. By doing an accept an answer, it can reach other community member, and they easily get come into conclusion on this topic before proceeding anything on this service side.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Re-deploy cloud service to extended, how to redirect traffic ?

1 answer

Your answer