Skip to main content
ComponentsEngine
Availability2014.1 or later

CPU Monitoring

Spot CPU saturation early

Local and Remote Monitoring

Deployment options for Solaris

SLAs and Automated Analysis

Set thresholds and rules

Root Cause Analysis

Correlate Solaris with other telemetry
Solaris Observability
Monitor the availability, health, performance, and resource utilization of Solaris servers with GermainUX.

​
Metrics Collection Overview

GermainUX periodically collects operating-system metrics from Solaris servers to provide real-time and historical visibility into CPU, memory, disk, network, processes, and overall system health.

​
Server Availability

Continuously monitor Solaris servers to identify availability and connectivity issues. GermainUX can help detect:
  • Server unavailable
  • SSH connectivity failure
  • Authentication failure
  • Monitoring command failure
  • Unexpected server restart
  • Server uptime changes
  • Monitoring interruption

​
CPU Monitoring

Monitor CPU utilization and workload to identify resource saturation and performance degradation. Analyze:
  • CPU usage
  • CPU queue length
  • CPU utilization trends
  • Sustained high CPU
  • Workload spikes
  • CPU-related performance degradation
CPU metrics can be correlated with processes and other system resources to help determine what is contributing to increased utilization.

​
Memory Monitoring

Monitor Solaris memory utilization and identify memory pressure. Analyze:
  • Memory usage
  • Memory cache faults
  • Available memory
  • Memory-utilization trends
  • Sudden changes in memory consumption
  • Sustained memory pressure
Historical analysis can help identify gradual resource growth and recurring periods of high memory consumption.

​
Disk Monitoring

Monitor file-system capacity and disk activity. Analyze:
  • Disk usage
  • Disk queue length
  • Disk I/O
  • File-system utilization
  • Disk-performance trends
  • Capacity growth
GermainUX can identify conditions such as:
  • File system approaching capacity
  • High disk utilization
  • Increased I/O
  • Disk queues
  • Abnormal disk activity

​
Network Monitoring

Monitor Solaris network activity and performance. Analyze:
  • Network bandwidth
  • Network bandwidth usage
  • Network queue length
  • Network latency
  • Interface activity
  • Network-performance trends
Network telemetry can be correlated with application and infrastructure monitoring to help identify the impact of connectivity or throughput issues.

​
Process Monitoring

Monitor operating-system processes running on Solaris. Analyze:
  • Running processes
  • Process count
  • Process availability
  • Unexpected process changes
Process monitoring can help identify when a required application or service is no longer running or when abnormal process activity occurs.

​
Server Configuration

GermainUX can collect Solaris system information using operating-system commands such as:
  • prtconf
  • vmstat
  • df
  • iostat
  • netstat
  • kstat
  • ps
The commands executed depend on the configured Solaris OS Monitor. Individual commands and corresponding OS metrics can be enabled or disabled when collection of a particular metric is not required.

​
Local and Remote Monitoring

Solaris monitoring can be deployed according to your infrastructure architecture.

​
Local Monitoring

Run the OS Monitor from a GermainUX component located on the monitored server when local execution is supported and appropriate.

​
Remote Monitoring

Monitor a Solaris server remotely through SSH. This enables a GermainUX Engine or Agent to periodically connect to the Solaris server, execute the configured monitoring commands, and collect the resulting metrics.

​
KPIs

Solaris monitoring provides KPIs including:
  • Memory Usage
  • Memory Cache Faults
  • CPU Usage
  • CPU Queue Length
  • Disk Usage
  • Disk Queue Length
  • Disk I/O
  • Network Queue Length
  • Network Bandwidth
  • Network Bandwidth Usage
  • Network Latency
  • OS Process
  • Process Count

​
Analytics

Analyze Solaris performance by:
  • Server
  • Application
  • Environment
  • Operating system
  • Monitoring location
  • Time period
  • Resource
  • Process
Historical data helps identify trends, recurring resource constraints, and changes in server behavior.

​
SLAs and Automated Analysis

Configure SLAs and Rules to identify conditions such as:
  • High CPU usage
  • High CPU queue length
  • High memory usage
  • Disk approaching capacity
  • High disk I/O
  • High disk queue length
  • Network degradation
  • Required process unavailable
  • Abnormal process count
  • Server unavailable
Thresholds should reflect the capacity and expected workload of each Solaris environment.

​
Alerts and Automation

When GermainUX detects a Solaris condition requiring attention, it can:
  • Send an alert
  • Notify subscribed users through a Watch
  • Generate a report
  • Trigger an approved diagnostic action
  • Execute an authorized automation

​
Root Cause Analysis

Solaris OS metrics can be correlated with other telemetry collected by GermainUX, including:
  • Application performance
  • Java
  • Web servers
  • Databases
  • APIs
  • Logs
  • Network
  • User activity
  • Business processes
This helps teams determine whether an application issue is associated with CPU, memory, disk, network, process, or another monitored dependency.

​
Get More Information

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

​
Get Help

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

Can't find what you need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.