Best Practice for Installing the NetOps Report Manager Service
search cancel

Best Practice for Installing the NetOps Report Manager Service

book

Article ID: 422909

calendar_today

Updated On:

Products

Network Observability

Issue/Introduction

What is the best practice for installing the NetOps Report Manager Service? (Operational Reports)

Environment

Dx Netops Performance Management  24.3.1 and up

Resolution

See Prerequisites for Installing the NetOps Report Manager Service

"By default, the NetOps Report Manager Service installation file (the installer) sets one fourth (1/4) of total available system memory as the maximum Java heap size for the NetOps Report Manager Service process.

For example, if the system where the NetOps Report Manager Service is installed has 8 GB of total system memory, then the NetOps Report Manager Service will use up to 2 GB."

 

The best practice for installing NetOps Report Manager Service (Operational Reports) is to put it on its own standalone host

If you install it on OneClick or Portal you must account for those additional resources to prevent performance problems

Memory allocation is handled in /opt/SRM/srm-rib/conf/srm-rib-jetty.conf