The user help docs are broken down into several main sections. You can find the sections in the menu on the left, or read through the below and follow the links there.
Looking at calls and running simple call reports.
If you need to see basic information about all or certain calls, your main tool will be the Browse > Calls page. To learn more about this page and the things you can do with it, see the Usage page. Some sample uses cases covered:
Generating Reports and Charts
At the other extreme is high level reporting and analytics, crunching statistics across your entire CUCM deployment and displaying the results as a pretty chart or a big exportable table. For this you will use the pages that you see listed under the “Report” section in the app Navigation bar. In particular you will use the Report > General Report page a lot. Please see the documentation in the Advanced Usage pages for specific use cases and help. Again, some examples:
Viewing 911 call information
Seeing who has called 911 or setting up alerts for when 911 gets called is done through the 911 pages. They are documented in these sections of the Usage page.
In addition to the above main feature set, there are also a slew of less well known capabilities.
Automating reports and dashboards, firing alerts
Any of the reports, charts and tables you can create can also be automated. Nearly every page has a “Create” button you can use to create an “Alert” or a “Dashboard Panel”.
When you use these you’ll be at times moving out of functionality that our app has built and into core framework functionality of Splunk itself. As such you can get a lot of value out of Splunk’s own user documentation. Here for example if you skip down to the “Create Dashboard Panel” section, you can see a walkthrough of creating dashboards that applies just as well to our app.
The best thing you can do to start though, is to just play with it. Create a dashboard, create an alert.
Sharing reports with others
When you get started you might be just sending screenshots to people. There’s nothing wrong with this but from there you can move up to:
If you have any comments at all about the documentation, please send it in to email@example.com.