Configure Monitoring for Solaris

​

Configuring Monitoring for Solaris with GermainUX: Steps and Best Practices

Configure GermainUX to collect availability, CPU, memory, disk, network, process, and other operating-system metrics from Solaris servers.

​

1. Open the Monitor Server Wizard

Go to: Germain Workspace -> Left Menu -> Settings → Wizards -> Monitor Server (Local or Remote) Click Add to create a monitoring component. Choose local or remote monitoring according to your deployment architecture.

​

Remote Solaris Monitoring

Use remote monitoring when a GermainUX Engine or Agent connects to the Solaris server through SSH.

​

2. Select the Component Type

Select: OS Monitor - Remote - Solaris

​

3. Select the Monitored Server

Select the Solaris server that you want to monitor. This is the target server from which GermainUX will collect operating-system metrics.

​

4. Select the Operating System

Select the appropriate Solaris operating system for the monitored application/server. This determines the operating-system commands and metrics used by the monitor.

​

5. Configure SSH Credentials

Provide or select the SSH credentials required to connect to the Solaris server. The account must have permission to execute the required monitoring commands. Use a dedicated monitoring account with the minimum permissions required whenever possible.

​

6. Configure the Monitor

Click Next and configure the monitoring component. Provide a descriptive monitor name. For example: Solaris - Production - Application Server 01 A consistent naming convention makes it easier to identify servers in dashboards, alerts, and reports.

​

7. Select the Monitoring Node and Engine

Select the GermainUX node and Engine that will execute the monitoring component. Choose an Engine that:

​

8. Configure the Schedule

Define how frequently GermainUX should collect Solaris metrics. Choose a frequency appropriate for: More frequent collection provides greater visibility but generates additional monitoring activity.

​

9. Finish the Configuration

Review the settings and click Finish. The monitoring component will execute according to the configured schedule.

​

Local Solaris Monitoring

Use local monitoring when the monitoring component executes directly on the server or monitoring environment.

​

1. Open the Monitor Server Wizard

Go to: Germain Workspace -> Left Menu -> Wizards -> Monitor Server (Local or Remote) Click Add.

​

2. Select the Local OS Monitor

Select the appropriate local OS Monitor component for the Solaris environment. Do not select a Linux-specific component unless the monitored operating system is Linux.

​

3. Select the Monitored Server

Select the server to monitor.

​

4. Select the Operating System

Select Solaris as the operating system when available for the selected monitoring component.

​

5. Configure the Component

Provide: Click Finish to create the component.

​

Configure Collected Metrics

Solaris monitoring uses operating-system commands to collect different categories of metrics. Depending on the configuration, these include: Each monitoring command can be individually configured or disabled. Disable collection when:

​

KPIs

Solaris OS Monitor data can populate KPIs including:

​

Configure SLAs

Configure SLA thresholds according to the expected behavior of each server. Examples include:

​

CPU

CPU Usage -> 90%

​

Memory

Memory Usage -> 90%

​

Disk

Disk Usage -> 85%

​

CPU Queue

CPU Queue Length -> Expected Threshold

​

Process

Required Process = Not Running Use thresholds appropriate for your environment rather than applying the same values to every Solaris server.

​

Configure Rules

Use GermainUX Rules when detection requires multiple conditions or more advanced logic. Examples: Rules can also correlate Solaris telemetry with other monitored technologies.

​

Configure Alerts and Watches

Configure notifications for conditions requiring attention. Examples: Solaris Server Unavailable → Alert Infrastructure Team Disk Usage -> Critical Threshold → Notify Server Owner Required Process Missing → Alert Application Support CPU Saturation + Application Degradation → Trigger Diagnostic Workflow GermainUX can use detected conditions to initiate alerts, Watches, reports, or approved automation.

​

Configure Dashboards

Create or configure dashboards to analyze: For infrastructure teams, group servers by:

​

Validate the Configuration

After creating the monitor, confirm that the expected KPIs are being generated. Verify:

​

Troubleshooting

​

No Solaris Data

Verify:

​

SSH Connection Fails

Verify:

​

Some Metrics Are Missing

Verify that the corresponding monitoring command: Individual Solaris commands can be configured or disabled, so a missing metric does not necessarily indicate that the entire OS Monitor has failed.

​

CPU or Memory Data Looks Incorrect

Execute the corresponding Solaris command directly on the monitored server and compare its output with the GermainUX monitoring result. Verify that the operating-system version and selected monitor type are appropriate for the target server.

​

Process Data Is Missing

Verify that: ps -A can be executed by the monitoring account and that process monitoring has not been disabled.

​

Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your Solaris environment. Contact GermainUX Support.

​

Get Help

The content of this document is proprietary to GERMAIN SOFTWARE LLC.