Standardized diagnostics for any ASP.NET Core app

[mkArtakMSFT]

Imagine if you could go to /_diagnostics for any ASP.NET Core app and you see a list of the common things that might be issues for customers
If- you're using routing, you see the routes

• In EF, you see that your DB isn't up to date with the latest migration

• You're given an option to run the migration

• SignalR

  • You have a hub but you don't have the hub wired up in the endpoint list

• Configuration

  • A page you could go to that would show you all of the configuration providers and what's configured in each of the providers
  • We added a feature called IConfigurationRoot.Print (he thinks, something like this) that would show you all of the configuration sources and which value came from which source

• Ability to see everything related to Authz in one place

Related: https://github.com/aspnet/specs/pull/526/files?short_path=385ad1d#diff-385ad1d05710ca57612c61303ce52e6cd94e301021bc0501e6d24a653d430004

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[BrennanConroy]

@mkArtakMSFT is this something we planned for in 6.0 or is backlog appropriate?