Solaris OS Server

Introduction

Solaris is a proprietary operating system which is provided by Oracle Corporation. It is an Unix-like operating system and it is written in C and C++ programming languages. It uses a mixed-source model, which includes both open and closed source components. The initial version of Solaris was released in 1992 by Sun Microsystems, and it was later acquired by Oracle Corporation in 2010. This operating system uses a monolithic kernel with dynamically loadable modules.

Pre-requisites

• Users must have either OpsRamp Classic Gateway 10.0.
• Ensure that Adapter Integrations add-on is enabled in client configuration. Once enabled, go to Setup > Integrations > Adapter to see Solaris OS Server integration.
• User should have read permissions access to files /dev/mem, /dev/kmem in order to fetch the below metrics:
  • solaris_os_server_openFileDescriptors_Utilization
  • solaris_os_server_openFileDescriptors_UsedCount
  • solaris_os_server_loggedInUsers_Pct
  • solaris_os_server_runningProcesses_Pct
  • solaris_os_server_Semaphores_Utilization
  • solaris_os_server_messageQueueIDs_Utilization
  • solaris_os_server_sharedMemoryIDs_Utilization
• Users should have a tmp folder, the application will use it to store cache data while running Log monitoring script for fetching latest logs.
• Users who want to apply log file monitoring, must have a home directory on the system on which the script will be run.

pwd

[content@centos-node1 ~]$ pwd
/home/content

Install the integration

1. From All Clients, select a client.
2. Go to Setup > Integrations > Integrations.
3. From Available Integrations, select Adapter > Solaris OS Server. You may also search for the application in the Integration List section.

4. Click Solaris OS Server application to install it.

5. The Install Solaris OS Server Integration popup appears. Enter the following information:
   a. Name: Name of the integration
   b. Upload Logo: Optional logo for the integration.
   c. GateWay Profiles: Select a gateway management profile to associate with the client.
   

   

6. Click Install. The Integration page displays the installed integration.

Configure the integration

1. In CONFIGURATION section, click +Add.

2. On Create Adapter Configuration, enter:
   • Name: Configuration name.
   • IP Address/Host Name: IP address or host name of the target.
   • Notification Alerts: Select TRUE or FALSE. If you select TRUE, application will handle Critical/Recovery failure alert notifications for Connectivity, Authentication Exceptions.
   • Additional Configurations: Add additional configuration details, such as file system, process, and so on. The Log File Configuration is part of the additional configuration, configure the values for below fields as per your log file monitoring use case:
     • Name
     • File Name
     • Rotated File Name
     • Expression
     • Check Type
     • Threshold
     • Severity
3. From the Credential section, select Custom and enter the Username and Password.
4. From the Resource Types & Metrics section, select the metrics and configure for availability and alert conditions, for Cluster & Server.
5. In the Discovery Schedule section, configure how frequently the discovery action should trigger. Select Recurrence Pattern to add one of the following patterns:
   • Minutes
   • Hourly
   • Daily
   • Weekly
   • Monthly
6. In the Monitoring Schedule section, configure how frequently the monitoring action should trigger.

8. Click Save.
9. After saving the integration, Solaris resources are discovered and monitoring is enabled as specified by the configuration profile.

The configuration is saved and displayed on the page. You can perform the actions manually, like Discovery, Monitoring or even Disable the configuration.

Resource information

1. To view the resource information, go to Infrastructure > Resources > Server.
2. Use the search function to find your resource and then click on it.

View resource attributes

The discovered resource(s) are displayed under Attributes. In this page you will get the basic information about the resources such as: Resource Type, Native Resource Type, Resource Name, IP Address etc.

View resource metrics

To confirm Solaris OS Server monitoring, review the following:

• Metric graphs: A graph is plotted for each metric that is enabled in the configuration.
• Alerts: Alerts are generated for metrics that are configured as defined for integration.

Supported metrics

Resource Type: Server

Risks, limitations & assumptions

• We are not supporting below monitorings as of now:
  • Hardware metrics
  • Processes (we provided one metric for each process RunningStatus. i.e, hpux_server_process_RunningStatus).
• We are using below commands to fetch max limits as per the Oracle Documentation!.

Max Limit Commands

Semaphore ID Limit: echo seminfo_semmni/D | mdb -k

Shared memory ID Limit: echo shminfo_shmmni/D | mdb -k

Message Queue ID Limit: echo msginfo_msgmni/D | mdb -k

• Need below json payload as input for log monitoring:
  • Name: This can be any string used to identify individual log configuration.
  • File Name: It is a combination of folder path and file name. Folder path should contain the exact path for the file as prefix. File name can be any valid string or regular expression. In case of file not found with specified file name, alert will be generated with the severity specified by the user. Example 1: C:\Program Files (x86)\Vistara\Agent\log\Age.?t.log Matches: Agent.log, Ageat.log ,.
  • Rotated File Name: It is similar to file name field but specifying the rotated file. This is a optional field.
  • Expression: This can be any valid string or regular expression used to specify the search string. It is a mandatory field.
  • Check Type: This can be either “exists” or “not exists”(case insensitive).
  • Threshold: This can be any valid integer. Alert will be generated in case of specified threshold breach happens.
  • Severity: It is used to specify the alert type to be created in case of expression found. Possible values are CRITICAL, WARNING, INFO, and OK (case insensitive).

Log file configuration:

 [
  {
  "Name":"",
  "File Name":"",
  "Rotated File Name":"",
  "Expression":"",
  "Check Type":"",
  "Threshold":"",
  "Severity":""
  }
]

• We do not process logs of size greater than 1GB.
• We do not process logs for the first request because it creates performance issues due to a large amount of data. We will process the second request based on the most recent logs (logs generated between the first and second polls).
• No recovery alerts are generated for expression related alerts. We will get recovery only for file not found alerts.
• Application can handle Critical/Recovery failure alert notifications for below two cases when user enables Notification Alerts in configuration:
  • Connectivity Exception
  • Authentication Exception
• Application will not send any duplicate/repeat failure alert notification until the already existing critical alert is recovered.
• Application cannot control monitoring Pause/Resume actions based on above alerts.
• Component level threshold configuration is not possible.
• Resource level metric threshold customization and frequency setting are not possible
• Usability issues in application configuration page while adding/editing.
• Optional configuration parameters cannot be defined.
• Application upgrade is manual process without version change.
• The availability is shown unknown for few resources even if it is enabled on the respective resource metrics. This is because of the presence of multiple native type resources under the same resource type.