Roadmap

What's on our list, pulled straight from the same backlog our own team works from. Nothing here is scheduled or committed — checked items have already shipped and show up in theChangelog.

Application changes

✓Deployments for Oracle, PostGres and MySQL are still placeholders, we need to deploy them. (Ported the reference app's My2 Collector / homebuilt Postgres monitor / Oracle baseline monitor scripts as LocalBundle sources, and made ScriptBatchExecutor engine-aware — per-engine batch splitting and connections instead of the SqlServer-only executor.)
Deployment is a little clunky, once you select a report, i think the select server navigation should be a popup panel, isntead of scrolling deeply south of the page.
Built in Custom Reports for sql server have a handfull of things to review: some reports are based on specific environments, other report smy be missing the cmsservername and serverlayer, lets spot check all provided reprot definitions
Snippets are an excellent baseline for "Custom Reports", which is distinct from the Multi Sheet Reports. we can generate a lot of equivilents from them for the otehr db systems.
Built in Custom Reports for postgres are very thin. spend some time going through my library and add those reports
Built in Custom Reports for mysql are very thin. spend some time going through my library and add those reports
Built in Custom Reports for oracle are very thin. spend some time going through my library and add those reports
Custom Dashboards. the two step process to edit a board, and then edit a panel is not intuitive, maybe allow edit at all times instead.
Custom Dashboards. and Line Graphs. Line graphs provide a great visualization of the data. however they need a time series to show the information over time, so intelligent decisions about spike events can be reviewed.
A. leverage the internal monitoring database as the source for some line graphs.
B. the above needs to be enhanced for all database systems.
C. Consider greatly enhancing the internal monitoring processes and databases to do the equivalent of what other systems, for example, how SQL watch uses a cron.sql agent job to store data into tables, maybe do it internally.
✓on the overview dashboards, implement a "Favorites" panel, so favorites are always on top, but all servers still searchable.
✓Implement a "Favorites Functionality, per user for the Overview. we did the same in reports, and we anticipate specific servers will often want to be visible at the top of teh views" (Done on all 5 Estate Overview views.)
✓When you go to Custom Dashboards, you can get there without having a server in focus. this should be fixed by adding a server dropdown menu. searching for a server is a pain. it should be a drop down as well as a search. we probably need the same search function, or that the page always inherits the last server touched, or that it cannot be navigated to unless a db is in scope.

Website Updates

✓The Change Log is not in sync with the applications List of Changes; lets synchronize them.
✓Web site does not yet have developer level details, i think i'd like more details, maybe a how to section for every feature.
✓Mention that this application was originally SQL Server Focused, and originated from the fact that in a medium sized or large environment will often have a footprint in more than one database system, and a dba has to bounce around a lot to get a good handle on what is going on. The big name applications that do this are always priced out as a per server, per year cost basis, which is often prohibitive for todays tighter budgets. this application hopes to fill that gap.
✓Add The Roadmap / todo should also be featured on the web site, to give the public face a bit more direction on where we are thinking, and also where we would update if we received a suggestion for the application, where we might list which features are planned, and maybe that they came from an internal or external suggestion

Have a feature you need? Tell us — customer requests are exactly how most of this list gets written.