Planning the next major version

[erikdarlingdata]

I'm considering decommissioning the Full dashboard in favor of the Lite dashboard with two modes:

1. What you're used to, standalone, easy to run and monitor tool
2. The Lite dashboard with a Windows Service that is always running, more like what enterprise monitoring tools do

The reasons for this are generally:

1. Maintaining two code bases is difficult (new features, improvements to plan viewer, bugs, and so on)
2. The schema change upgrade path testing for Full has caused major headaches

Before I do anything, I'd like to know what exactly people care about with regard to the Full dashboard.

See? I care.

[aidelia]

I've choose Always-on collection but I felt a little bit confused with the term because at first I've thought the Always On was a refrence to the SQL Server markenting term and not related to Lite data capture.

[erikdarlingdata]

That's why it says "(runs when I'm not at my desk)" next to it 😃

[lukaszherman]

My current use case is to use the dashboard on an ad hoc basis for deeper investigation when issues arise, rather than in continuous mode.

I also plan to collect data from the Performance Monitor database across all SQL instances and send it to my preferred monitoring/observability platform. This would allow developers to view selected data, such as blocking and Query Store metrics, without needing direct access to the SQL instances.