...
Applying a license key for the agent to start collecting data
Applying the PowerConnect user credentials created during the pre-installation steps
Setting the JMX RMI URL from the pre-installation steps
Configuring an outbound connection
Enabling the various extractors to collect data
...
In the PowerConnect Agent UI click Overview in the menu on the left
Under the Authentication section enter the PowerConnect username and password created in the pre-installation steps
Note - The CMS System and CMS Authentication should be left at default values unless there is a problem with authentication
Click Save
The PowerConnect credentials have now been applied
Setting the JMX RMI URL
In the PowerConnect Agent UI click JVM under the Extractors menu on the left
Enter the JMX RMI URL
Click Save
Click Administration in the menu on the left and click the Health tab
Under Test Connections click JMX
The JMX Connection test should be successful
Note - If the test fails it means the JMX RMI URL is incorrect or the PowerConnect user credentials are incorrect
The JMX RMI URL is now configured
Creating an Outbound Connection
...
Configuration | Description | Required | Default Value | Comments |
|---|---|---|---|---|
license_key | License key for the agent | True |
|
|
powerconnect_user | User for the agent to use to collect data from web services and jmx | True | ||
powerconnect_password | Password for the PowerConnect user | True | ||
cms_system | Which CMS system that PowerConnect user should connecto to | False | auto | Setting to auto means the agent will try to automatically discover the CMS system endpoint. Do not change this setting unless there is a problem with authentication |
cms_authentication | The type of authentication used | False | secEnterprise | Do not change this unless there is a problem with authentication |
jmx_enabled | Enable the JMX extractor | False | true | |
jmx_rmi_url | The JMX RMI url | True | This should be set to the JMX RMI in the pre-installation steps | |
jmx_mbeans | List of JMX Mbeans to collect | False | java.lang:type=OperatingSystem;java.lang:type=Threading;java.lang:type=Memory;java.lang:type=ClassLoading;java.lang:type=Runtime | |
jmx_interval | How often to collect JMX data (ms) | False | 60000 | |
cpu_monitoring_enabled | Enable operating system CPU monitoring |
| false |
|
cpu_monitoring_interval | How often to collect CPU metrics (ms) |
| 60000 |
|
memory_monitoring_enabled | Enable operating system memory monitoring |
| false |
|
memory_monitoring_interval | How often to collect memory metrics (ms) |
| 60000 |
|
os_process_monitoring_enabled | Enable operating system process monitoring |
| false |
|
os_process_monitoring_interval | How often to collect process metrics (ms) |
| 60000 |
|
disk_monitoring_enabled | Enable disk iops monitoring |
| false |
|
disk_monitoring_interval | How often to collect disk iops metrics (ms) |
| 60000 |
|
disk_space_monitoring_enabled | Enable disk space monitoring |
| false |
|
disk_space_monitoring_interval | How often to collect disk space metrics (ms) |
| 60000 |
|
network_monitoring_enabled | Enable network interface monitoring | False | false |
|
network_monitoring_interval | How often to collect network interface metrics (ms) | False | 60000 |
|
thread_monitoring_enabled | Enable thread monitoring | False | false | |
thread_monitoring_interval | How often to collect thread data (ms) | False | 60000 | |
ds_job_monitoring_enabled | Enable Data Services Job monitoring | False | false | |
ds_job_monitoring_interval (ms) | How often to collect job data | False | 60000 | |
db_job_monitoring_lag | Lag setting for audit log collection (ms) | False | 60000 | This setting is to deal with scenarios where there is a lag between the data being written to the Data Services database and its availability for query via the Web Service (usually high load) |
ds_job_monitoring_repositories | Which repositories to collect job data from | False | auto | Setting to auto means the agent will try and discover the repositories available. Otheriwse a comma separated list of repository names can also be provided |
ds_job_monitoring_trace_logs | Collect trace logs for each job | False | false | |
ds_job_monitoring_monitor_logs | Collect monitor logs for each job | False | false |
...