Azure-docs: Multi Step WebTests
Hi,
With the deprecation of multistep webtests, Can you please provide an alternative for the same to continue with the availability tests.
Thank you
D Karthik
Document Details
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 10858323-1827-1c73-b93a-7c133bae54ba
- Version Independent ID: 3ed5fda4-c916-dcb0-a3b2-a0bb534d8bdb
- Content: Monitor availability and responsiveness of any web site
- Content Source: articles/azure-monitor/app/monitor-web-app-availability.md
- Service: application-insights
- GitHub Login: @lgayhardt
- Microsoft Alias: lagayhar
karthikdevarakonda
All 8 comments
Hi @karthikdevarakonda, thanks for the question!
I am a PM on Azure Monitor, currently focused on the availability monitoring space. This is a problem that I'm currently looking at and trying to solve.
Current state is: As of right now, we have no plans to drop support for Visual Studio multi-step tests, and (although this is not a guarantee), we do not intend to drop support for them without a 1 year lead time, a sufficient replacement, and migration guidance. Visual Studio 2019 will still have the ability to write multi-step tests, and the support lifecycle for a Visual Studio product is 5 years. My recommendation is to continue using Visual Studio multi-step web tests.
That being said, eventually support for these tests will be dropped. We understand that no one wants to invest in a technology that will eventually be deprecated , however we do not yet have a sufficient replacement in this space.
There is a workaround for which support will not be deprecated - and that is to run your own web tests in any language for which we have an SDK, run them on your own server or on Azure functions/containers/VMs, and send the results to your Application Insights resource using the TrackAvailability() API. This is a more DIY approach, as you are then responsible for ensuring your test runs at regular intervals and sending the test results to App Insights. This approach also has limitations with how much data is displayed in the portal, but we are improving the amount of information that is displayed in the next few months.
morgangrobin
on 1 Mar 2019
@karthikdevarakonda Hope @morgangrobin's response answers your question!
We are now going to close this thread as resolved, but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.
BhargaviAnnadevara-MSFT
on 2 Mar 2019
@BhargaviAnnadevara-MSFT @morgangrobin I have a few questions.
Is there any updates as to a replacement?
Are there any examples you know of with this DIY approach. I am particularly interested in multi-regional availability tests?
Is there any plan to deprecated the TrackAvailability() API that is mentioned in the DIY option?
Is there any recommended alternative that integrates with Azure Monitoring Availability?
Mexicoder
on 17 Apr 2020
Hey there,
There is a doc here that goes more in-depth on the DIY approach.
I'm not working on this project any longer so I've forwarded this question to my colleague Carter who can hopefully help with your other questions.
morgangrobin
on 18 Apr 2020
@Mexicoder We're not deprecating the Track Availability API. No alternative recommendations. We're currently working on the next version of Azure Monitor Availability that should be in Public Preview this summer
casocha
on 21 Apr 2020
This is terrible. Please provide roadmap guidance.
Cloudmersive
on 1 Jul 2020
@casocha any news on the public preview summer progress? (or private preview options)
tiny-dancer
on 10 Aug 2020
@casocha any news on the public preview summer progress? (or private preview options)
@tiny-dancer we're in private preview today with our replacement. We don't have guidance on a public preview date right now. If you're interested in participating in the private preview then please email me. @Cloudmersive you're welcome to join as well. Happy to chat about general roadmap too.
Email: [email protected]
cartersocha
on 11 Aug 2020
Related issues
bityob
·
3Comments
behnam89
·
3Comments
jamesgallagher-ie
·
3Comments
varma31
·
3Comments
AronT-TLV
·
3Comments
Most helpful comment
Hi @karthikdevarakonda, thanks for the question!
I am a PM on Azure Monitor, currently focused on the availability monitoring space. This is a problem that I'm currently looking at and trying to solve.
Current state is: As of right now, we have no plans to drop support for Visual Studio multi-step tests, and (although this is not a guarantee), we do not intend to drop support for them without a 1 year lead time, a sufficient replacement, and migration guidance. Visual Studio 2019 will still have the ability to write multi-step tests, and the support lifecycle for a Visual Studio product is 5 years. My recommendation is to continue using Visual Studio multi-step web tests.
That being said, eventually support for these tests will be dropped. We understand that no one wants to invest in a technology that will eventually be deprecated , however we do not yet have a sufficient replacement in this space.
There is a workaround for which support will not be deprecated - and that is to run your own web tests in any language for which we have an SDK, run them on your own server or on Azure functions/containers/VMs, and send the results to your Application Insights resource using the TrackAvailability() API. This is a more DIY approach, as you are then responsible for ensuring your test runs at regular intervals and sending the test results to App Insights. This approach also has limitations with how much data is displayed in the portal, but we are improving the amount of information that is displayed in the next few months.