Generic APM / Infrastructure Tools | Boemska Enterprise Session Monitor | |
---|---|---|
Purpose | Generic Application Performance Monitoring ,with some plugins that enable Service control and Application Administration | Analytic Workload profiling and analysis, end-user self-service workload management, batch schedule optimisation |
Standalone, independent of Application Platform | 1 | |
Built for End Users as well as Administrators | ||
Topological auto-discovery of application stack | ||
Monitoring of JMX metrics and core components | ||
End-user Workload Management | ||
Real-time per-user performance feedback | ||
Audited self-service process management | ||
A/B Comparison with previous code instances | ||
Per-process CPU, Memory and IO measurement | ||
Per-user scratch monitoring (WORK/UTIL) | ||
Real-time annotation of Workload 2 | ||
Native integration with popular Analytics tools (SAS Base/LASR/Viya, R, Python, Julia, Netezza, others) | ||
Batch Jobs & SAS Grid 3 | ||
Suspend, resume or cancel grid jobs, pause queues | 4 | |
Audited end user self-service retrieval of job logs | ||
A/B performance comparison, critical path analysis | ||
Ability to restart or control core services from UI | ||
Departmental usage analysis and Chargeback3 | ||
Retrospective Categorisation of Resource Usage |
1 SAS Environment Manager is dependent on the SASLogon application component for authentication and access control
2 One way ESM enables developers to write more efficient code is by allowing them to programmatically annotate relevant notes and checkpoints on resource timelines for step segmentation, or by identifying those steps automatically where possible (ie. LASR/CAS, EG)
3 For this section, the APM column refers specifically to SAS Environment Manager
4 ESM can only terminate jobs, but allows end-user job owners to do so with individual audited authentication. SAS EM has much deeper integration with SAS GRID control.