Hi Larry!
Thanks for your question and your suggestion! Solving reporting scenarios of our customers is definitely a focus for us and from multiple conversations, one thing materialized as the prime interest: the freedom to configure custom reports.
A while ago, we looked into the various options to deliver on that expectations and opted to bank on dashboarding capabilities to solve reporting use cases, because we regarded investment in that area as "the best bang for the buck" solution. Our rationale was, that whatever people want to put on reports, would just as much make sense on dashboards and improving in that specific area was in our interest anyway. So "dashboard reports" it is.
- BTW: Yes, we do still have big plans to improve upon visualization capabilities in general to make for more compelling dashboards and reports.
To the specific question on service quality reports: It's true, that we ultimately want to map them into the "dashboard reports" approach, but we acknowledge, that we still miss some generic visualization options (like time-based comparisons) to fully manage to do so.
To your additional points:
- Providing the ability to get a "static report" (as in getting a PDF) is still under investigation. It is some challenges on the deployment side of things, that required us to pump the brakes and make sure, we're doing this the right way.
- Providing the ability for more targeted reports around applications, teams, etc. will go hand in hand with the planned feature of "Dashboard filters". This is basically about allowing to use one dashboard for multiple purposes (e.g. for a given application context). So this will come!
- Providing the ability to configure a mailing list for reports is, alongside more default schedule options (like daily or custom schedules), one of the follow-up topics for the first incarnation of dashboard-reports, which are currently in an early-adopter state.
I hope this finds you well and answers your questions. If not, don't hesitate to come forward!
Roman
