Administering Cloud EPM: The Platform Beneath the Business Processes · Module 14 · Monitoring the Estate
The activity report: application and Essbase
Lesson 162 of 201 · 14 min
Walk application size and artefacts, connecting to Module 12's size limits. Then the Essbase statistics — metrics, runtime data, design statistics — outline warnings and what they indicate, calculation script statistics, business rules information, application design and runtime information, and manual database and Essbase access information, and why that section matters. APPLICATION SIZE HERE IS YOUR MODULE 12 GROWTH TREND. Track it monthly and you get the projection that lets you act before the limit. Outline warnings and calculation statistics are how an Essbase-shaped problem announces itself. You are not tuning Essbase; you are recognizing that somebody should. THE MANUAL ACCESS SECTIONS ARE A SECURITY CONTROL. They record direct access to the underlying stores. Review them; that is their purpose.
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.
In this module: Module 14 · Monitoring the Estate
- 1Monitoring as a routine, not a reaction
- 2The activity report: environment and users
- 3The activity report: usage and performance
- 4The activity report: application and Essbase
- 5Business-process-specific metrics
- 6Access logs
- 7Automating report download
- 8The role assignment report
- 9Audit, login and usage reporting
- 10Building the routine, and what breaks
- 11Lab: read a report, then build the routine