Classic Application Insights deprecation

[thomas11]

Classic Application Insights is being retired on 2024-02-29. For the next major version, we should make sure to exclude resources that don't exist anymore due to this.

[cleverguy25]

Added to epic https://github.com/pulumi/home/issues/3552

[EronWright]

Some important context (from "Migrate a Classic Application Insights resource"):

Can I still use the old API to create Application Insights resources programmatically?
For backwards compatibility, calls to the old API for creating Application Insights resources continue to work. Each of these calls creates both a workspace-based Application Insights resource and a Log Analytics workspace to store the data.

We strongly encourage updating to the new API for better control over resource creation.

[EronWright]

I took a look at the deprecation notice, and it seems to be about how your Insights applications would be migrated to use a Log Analytics backend. A new field was added to associate an app to a workspace. I don't see any API being retired in this case, because the older APIs are said to still be available. @thomas11 do you agree that we could close this?

[thomas11]

@thomas11 do you agree that we could close this?

Interesting. The two statements from Microsoft conflict, then: the first link says "retired", which normally means shut down. The second link says it will continue to work.

At the least we should put a deprecation notice on the classic resources, though, so we can remove them in v4.

I'm even tempted to remove them since the actual underlying service is not live anymore (the API redirects to the new one). Slimming down the provider is good for both ease of use and SDK size. @danielrbradley what are your thoughts?

[danielrbradley]

Can you clarify which resources you're referring to as the "classic resources"?

What's the "old" vs "new" ways users are meant to build these resources?

[thomas11]

Can you clarify which resources you're referring to as the "classic resources"?

What's the "old" vs "new" ways users are meant to build these resources?

From https://learn.microsoft.com/en-us/previous-versions/azure/azure-monitor/app/convert-classic-resource:

Can I still use the old API to create Application Insights resources programmatically?
For backwards compatibility, calls to the old API for creating Application Insights resources continue to work. Each of these calls creates both a workspace-based Application Insights resource and a Log Analytics workspace to store the data.
We strongly encourage updating to the new API for better control over resource creation.

So there is a new API. The old API seems to still exist, but with no guarantee for how long.

It also says that Insights resources have to be migrated to the new workspace-based model, which can take up to 24h and is irreversible. So it’s really a new backend.

[danielrbradley]

Open questions:

• What's the resource path of the old vs new resources?
• Do these map to different resources in our SDKs?