SAS JMS Broker Monitoring & Management

Using SAS JMS Broker, organizations are capable of creating enterprise integration patterns (either on the JMS client or in the broker process) to support smart routing, transformation and a whole host of other powerful patterns.

This plugin auto-discovers every individual Queue defined in SAS JMS Broker and collects metrics which reflect the queue's load, performance and throughput. This helps administrators to understand how burdened the messaging server is and if individual messages are getting stalled by the performance of the SAS JMS Broker server.

Auto-Discover your hardware and SAS JMS Broker servers
Monitor every metric, log, and configuration for all SAS JMS Broker resources in your inventory
Identify problem resources with automatic baselines for every metric
Control your SAS JMS Broker resources on-demand, on schedule, or in response to alerts
Alert on any measurement, log, or security event in your SAS JMS Broker environment

System Supported Versions

• SAS JMS Broker 5.7
• For operating system support, please see our supported operating systems list.

System Monitoring Specification

Agent Monitoring & Management

For a system to be monitored, a SAS Environment Manager agent must first be installed on it. The agent is then configured to report information to the SAS Environment Manager Server.

The camagent plugin discovers and monitors the agent resources as they are configured to report information back to the server.

Auto-Discover your hardware and agent resources
Monitor every metric, log, and configuration for all agent resources in your inventory
Identify problem resources with automatic baselines for every metric
Control all your agent resources on-demand, on schedule, or in response to alerts
Alert on any measurement, log, or security event in your agent environment

EMI Framework and Service Architecture

Designed to augment the basic capabilities of SAS Environment Manager, this plugin provides the framework components of the SAS Environment Manager Service Architecture Including:

Event Integration

• Event Export – the framework’s event export capabilities allows SAS Environment Manager to generate events to be consumed by third-party monitoring products.
• Event Import – the framework’s event import capabilities provide a command line interface for generating events to appear in SAS Environment Manager. This interface can be called from both internal SAS solutions and external applications.

ACM, APM and Kits Data Mart ETL

• ACM Extract, Transform, and Load (ETL) Data Mart Service to interface and extract agent collected resource metrics.
• APM Extract, Transform, and Load (ETL) Data Mart Service to load ARM enabled SAS Application Server logs.
• KIT Extract, Transform, and Load (ETL) Data Mart Service in support of SAS solution transaction logs.

Service Architecture Report Center

Report Center is collection of SAS stored process reports that are produced from data in the SAS Environment Manager Data Mart. These reports are created to provide a comprehensive view of the performance and operational status of your SAS environment and its resources. Designed by SAS Research and Development, SAS Environment Manager Report Center helps monitor and analyze resources critical to the health and operational stability of a SAS deployment. Out of the box monitoring focus areas include:

• Platform resources including: CPU, network, memory, and swap
• System errors, TCP resets, packet failures, and network errors
• SAS Application Server consumption metrics
• SAS Web Server memory management
• HTTP web application response time
• Application response measures - monitoring SAS procedure, data set, and server Usage
• Metadata audit reports - monitoring access, logon, and metadata changes

The reports and associated stored processes in the Report Center are created when you initialize SAS Environment Manager Extended Monitoring function in the SAS Environment Manager Service Architecture. However, the SAS stored process reports operate only on data stored in the SAS Environment Manager Data Mart by APM or ACM ETL processes. Unless you initialize and enable one of those packages, no reports will be produced. Solution kits, which provide monitoring and reporting for specific applications or SAS solutions, can also add solution-specific reports to the Report Center.

Enterprise Management Integration (EMI) Monitoring & Management

The emi-services plugin offers* a series of services to the user through creating respective resources in SAS Environment Manager. The following services are currently offered by the emi-services plugin:

• PGHA service

* Please note this plugin will continue to be extended in future Maintenance Releases. Please check back for updates to the services offered by this plugin.

PGHA

PGHA is a platform service that allows administrators to monitor the status of SAS Web Infrastructure Platform (WIP) Data Servers in a primary/standby configuration, and used to host the SAS SharedServices database. The PGHA service allows SAS Environment Manager to detect when a Web Infrastructure Platform Data Server is unavailable, and optionally to promote a standby Web Infrastructure Platform Data Server to primary.

PGHA is one of two SAS components (along with the Postgres HA JDBC shim) used to configure fully-automated failover from a primary WIP Data Server to a secondary WIP Data Server.

Environment Snapshot

Environment Snapshot collects and displays the most current performance measures and configuration parameters from the SAS Environment Manager database, providing you with valuable information about your system. Environment Snapshot also has the capability to execute and gather real-time usage information reported by the Unix system commands top, who, and df system or equivalent Windows commands. In addition, you can take a snapshot of the information, which saves all of the data in a text file. This file provides an easy way to communicate the status and configuration of your system when you are working with SAS Technical Support.

Access Environment Snapshot via the Analyze pull-down in the SAS Environment Manager interface then use the Select a System menu to choose the platform whose performance data you want to view.

To save all of the environment data to a text file, click Snapshot Environment. By default, live system queries, events, and alerts are not included in the snapshot file, to add them to the file, select the check boxes beside the items that you want to include. Because the plugin queries the SAS Environment Manager database, taking a snapshot might take several minutes. This depends on the size of the installation and the number of machines being monitored by your environment. After you create a snapshot file, the location of the file is displayed in the plugin.

SAS Cache Locator 6.6.3 Monitoring & Management

SAS Cache Locator is a Gemfire distributed caching system. SAS Cache Locator is a logical entity --- a set of servers that are configured to communicate with one another. The servers in a Cache Locator are referred to as members or nodes. Member types (defined in the rows below) include:

• JMX Agent
• Gateway Hub 6.6.3
• Cache Server 6.6.3
• Application Peer 6.6.3

The GemFire plugin manages a SAS Cache Locator and the servers and services it comprises. The intended list of resource types below illustrates the hierarchial relationships among the managed components of a GemFire DS.

SAS Cache Locator
JMX Agent
Cache Server 6.6.3
Cache Server 6.6.3 Region
Application Peer 6.6.3
Application Peer 6.6.3 Region
Gateway Hub 6.6.3
Gateway Hub 6.6.3 Gateway
Gateway Hub 6.6.3 Region

Auto-Discover your hardware and SAS Cache Locator servers
Monitor every metric, log, and configuration for all SAS Cache Locator resources in your inventory
Identify problem resources with automatic baselines for every metric
Control your SAS Cache Locator resources on-demand, on schedule, or in response to alerts
Alert on any measurement, log, or security event in your SAS Cache Locator environment

System Supported Versions

• SAS Cache Locator 6.6.3
• For operating system support, please see our supported operating systems list.

JMX Remote Monitoring & Management

The JMX plugin provides a standard remote API to manage remote JMX-enabled applications. This plugin removes the requirement for connector code specific to each product.

Auto-Discover your hardware and JMX Remote resources
Monitor every metric, log, and configuration for all JMX Remote resources in your inventory
Identify problem resources with automatic baselines for every metric
Control all your JMX Remote resources on-demand, on schedule, or in response to alerts
Alert on any measurement, log, or security event in your JMX Remote environment

The JMX-enabled application to be monitored must be configured to accept remote connections. In many cases, the remote connector is enabled by default, otherwise, you must configure it for remote access.

• J2SE 1.7.0
• MX4J
• ActiveMQ
• Hadoop
• tc Server
• And more...

Other server types continue to use vendor specific connectors for backward compatibility. The Sun JVM 1.7.0 type applies to any of the above and any other JMX-enable server running under a Sun 1.7.0 JVM but has its own set of metrics and control actions. Unlike the other server types, Sun JVM 1.7.0 instances are not currently auto-discovered. All of the server types have the following configuration properties:

• jmx.url - The JMX Service URL
• jmx.username - Username if authentication is required
• jmx.password - Password if authentication is required

Network Device Monitoring & Management

The netdevice plugin discovers each interface on the device, and creates a platform service of type "Network Device Interface" for each. The plugin discovers the values of the following properties for each interface.

• IP Address
• Netmask
• Maximum Transmission Unit
• Physical Address - macaddress
• Bandwidth - Interface speed
• Interface Name

Auto-Discover your hardware and Network Device resources
Monitor every metric, log, and configuration for all Network Device resources in your inventory
Identify problem resources with automatic baselines for every metric
Control all your Network Device resources on-demand, on schedule, or in response to alerts
Alert on any measurement, log, or security event in your Network Device environment

The name of a Network Device Interface resource is forming by concatenating the following resource data:

• The parent Network Device's Fully Qualified Domain Name.
• The parent Network Device's Fully Qualified Domain Name.
• The Network Device Interface's Interface Name.
• The string "Interface".
• The Network Device Interface's Physical Address.

For example, this name:

sfo-gw.hyperic.net sfo-gw.hyperic.net bgroup0/0 Interface (0:23:9c:81:10:e)

is for a Network Device Interface whose:

• Parent Network Device's Fully Qualified Domain Name is

  sfo-gw.hyperic.net

• Interface Name is

  bgroup0/0

• Physical Address is

  0:23:9c:81:10:e

Netservices Monitoring & Management

The netservices plugin monitors and manages two types of resources, DNS and Inetaddress-ping.

Auto-Discover your hardware and Netservices resources
Monitor every metric, log, and configuration for all Netservices resources in your inventory
Identify problem resources with automatic baselines for every metric
Control all your Netservices resources on-demand, on schedule, or in response to alerts
Alert on any measurement, log, or security event in your Netservices environment

DNS

This service checks availability of a specific DNS server, as specified by the hostname property. The service will be considered available if the DNS server can be spoken to, even if there are no answers for the specified lookupname.

The optional match property can be used to change this behavior, where the service availability will report at the warning level if there are non matches in the answer section.

The match property can be a regular expression or substring, where a value of * simply means one or more answers of any value is considered a successful lookup.

Inetaddress-ping

This service checks availablility of hostname using the java.net.InetAddress.isReachable method.

SAS Web Infrastructure Platform Data Server Monitoring & Management

SAS Web Infrastructure Platform Data Server (WIP Data Server) is an instance of Postgres and is currently detected as a Postgres resource in the SAS Environment Manager inventory model. Because SAS Environment Manager uses the WIP Data Server as its built in database backend, we have aimed to provide the deepest, most comprehensive monitoring available in any management solution.

SAS Environment Manager allows discreet management of both the server engine as well as every individual table in the system, thereby providing not only a vast assortment of metrics, but also control capabilities commonly associated with the WIP Data Server monitoring and management such as vacuum, analyze, and vacuum full analyze. Performing these management tasks on an automated basis through HQ's integrated control infrastructure allows you to define policies such as reallocating free space through vacuum whenever the rate of deletes per minute on a table exceed a threshold.

SAS Environment Manager aims to provide WIP Data Server users the monitoring and management capabilities typically found in database centric tools coupled with management support for the other technologies which, along with databases, are used in today's enterprise environment. Its powerful application concept allows you to visualize monitoring data from your database tier alongside your business logic and presentation tiers by giving you the ability to measure how client activity is reflected across the various layers of your application infrastructure.

Auto-Discover your hardware and WIP Data Server servers
Monitor every metric, log, and configuration for all WIP Data Server resources in your inventory
Identify problem resources with automatic baselines for every metric
Control all your WIP Data Server resources on-demand, on schedule, or in response to alerts
Alert on any measurement, log, or security event in your WIP Data Server environment

System Supported Versions

• Web Infrastructure Platform Data Server
• For operating system support, please see our supported operating systems list.

System Monitoring Specification

SAS Application Server Tier Monitoring & Management

The SAS Application Server Tier plugin is a custom-built extension for SAS Environment Manager. The plugin provides for auto-detection and monitoring of the SAS Application Server Tier set.

The most significant difference between this plugin and the SAS Servers Plugin is that this plugin defines a new top-level resource, or a platform, to represent the entire SAS environment where the SAS Servers Plugin provides a per-machine view of the SAS environment. The 'parent' resource for the SAS servers is the host platform resource (i.e. a specific machine). For the SAS Application Server Tier Plugin, the top-level parent resource is a representation of the entire logical Application Server Tier. Child resources represent logical entities (Contexts and SAS servers that are not associated with a Context such as Operating System Services and Object Spawners).

Server detection and the collection of properties and metrics are done remotely with the local Agent acting as a proxy. Since the Metadata Server acts as a single sort of 'hub' for a multi-machine SAS environment, the proxy is set up to be the same host as the Metadata Server.

Auto-Discover your hardware and SAS Application Server Tier resources
Monitor every metric, log, and configuration for all SAS Application Server Tier resources in your inventory
Identify problem resources with automatic baselines for every metric
Control all your SAS Application Server Tier resources on-demand, on schedule, or in response to alerts
Alert on any measurement, log, or security event in your SAS Application Server Tier environment

The platform resource that represents the Application Server Tier supports two metrics:

• Availability - Involves checking availability of the Metadata Server
• Health - Involves connecting to the Metadata Server to ensure it is available to service requests

The Metadata Server processes themselves are monitored individually under each host ([hostname] SAS Metadata Server 9.4 server resources) which monitors the server pid file and collect more detailed metrics for each process.

SAS Hadoop Server Monitoring & Management

The SAS Hadoop plugin is a custom-built extension for SAS Environment Manager. The plugin provides for auto-detection and monitoring of the Hadoop server set.

As Hadoop servers are detected, resources are created in HQ. The Hadoop servers directly supported by the Hadoop plugin include:

• Hadoop Name Node - Contains metadata information about the files stored in HDFS.
• Hadoop Secondary Name Node - Contains snapshot information to allow the primary Hadoop Name Node to be restarted after a failure.
• Hadoop Data Node - Contains a portion of the actual files stored in HDFS.

The intended list of resource types below illustrate the hierarchial relationships among the managed components by the SAS Hadoop plugin:

Hadoop Name Node - Server
RPC - Service
Stats - Service
FS Namesystem - Service
Hadoop Secondary Name Node - Server
Hadoop Data Node - Server
RPC - Service
Stats - Service
FS Dataset - Service

Auto-Discover your hardware and Hadoop Server resources
Monitor every metric, log, and configuration for all Hadoop Server resources in your inventory
Identify problem resources with automatic baselines for every metric
Alert on any measurement, log, or security event in your Hadoop Server environment

System Monitoring Specification

SAS Servers Monitoring & Management

The SAS Servers plugin is a custom-built extension for SAS Environment Manager. The plugin provides for auto-detection and monitoring of the SAS server set.

As SAS servers are detected, resources are created in HQ. The SAS servers directly supported by the SAS Servers plugin include:

Config Level Directory - Server
Home Directory - Server
Metadata Server - Server
OLAP Server - Server
Object Spawner Server - Server
Stored Process Server - Service
Workspace Server - Service
Pooled Workspace Server - Service
(Logical) Stored Process Server - Service
(Logical) Workspace Server - Service
(Logical) Pooled Workspace Server - Service

Auto-Discover your hardware and SAS Server resources
Monitor every metric, log, and configuration for all SAS Server resources in your inventory
Identify problem resources with automatic baselines for every metric
Control all your SAS Server resources on-demand, on schedule, or in response to alerts
Alert on any measurement, log, or security event in your SAS Server environment

System Monitoring Specification

Spring Insight Monitoring & Management

Spring Insight Operations captures Web application events known as traces. A trace represents a thread of execution. Traces are usually started by an HTTP request but can also be started by a background job. A trace contains operations, which represent significant points in the execution of the trace, for example, a JDBC query or transaction commit. Insight Operations uses trace data to calculate summary information that helps identify the root cause of application performance issues.

Insight Operations has a two-tiered architecture that consists of Spring Insight Dashboard and Spring Insight Agent. tc Server instances that run production Web applications run the Spring Insight Agent application. Insight Agent collects trace data and sends it to a single, dedicated tc Runtime instance running Spring Insight Dashboard. Insight Dashboard provides a user interface for monitoring applications across all servers and to get detailed statistics from individual servers.

Auto-Discover your hardware and Spring Insight resources
Monitor every metric, log, and configuration for all Spring Insight resources in your inventory
Identify problem resources with automatic baselines for every metric
Control all your Spring Insight resources on-demand, on schedule, or in response to alerts
Alert on any measurement, log, or security event in your Spring Insight environment

SAS Environment Manager's Spring Insight Plugin:

• Collects application metrics from a Spring Insight Dashboard.
• Provides two built-in resource type alerts that apply to all Spring Insight Application resources.
• Provides a user interface for viewing the health of Spring Insight Applications and for analyzing application health and performance issues.

The Spring Insight plugin requires Spring Insight Operations 1.5.1 (not included with SAS 9.4 TS1M0).

This plugin creates two types of resources:

• Spring Insight - Server - Represents the Insight Dashboard application. A tc Server runtime created with the Insight-Dashboard template.
• Spring Insight Application - Service - A Spring application that is monitored by Insight. An application running in a tc Server runtime created with the Insight-Agent template.

SAS Web Application Server Monitoring & Management

SAS Web Application Server is an instance of tc Server and is currently detected as a SpringSource tc Server resource in the

SAS Environment Manager inventory model.

Auto-Discover your hardware and SAS Web Application Server resources
Monitor every metric, log, and configuration for all SAS Web Application Server resources in your inventory
Identify problem resources with automatic baselines for every metric
Control all your SAS Web Application Server resources on-demand, on schedule, or in response to alerts
Alert on any measurement, log, or security event in your SAS Web Application Server environment

System Monitoring Specification

System Monitoring & Management

The system plugin discovers a series of resources on the device, and creates platform services of respective type for each. The plugin discovers and creates platform services of the following types:

• FileServer Mount
• FileServer File
• FileServer Directory
• Script
• NetworkServer Interface
• CPU
• Process
• MultiProcess
• Windows Service
• Windows Security
• SNMP

Auto-Discover your hardware and system resources
Monitor every metric, log, and configuration for all system resources in your inventory
Identify problem resources with automatic baselines for every metric
Control all your system resources on-demand, on schedule, or in response to alerts
Alert on any measurement, log, or security event in your system environment

The system plugin also creates key metrics for its platform:

• CPU Usage
• Free Memory
• Swap used
• Availability

Furthermore, the system plugin allows you to execute the following 'live data' commands on platforms through the their "Views" tab:

• cpuinfo - displays details about the cpu(s), such as the speed of each process.
• cpuperc - displays cpu percentage usage.
• df - reports available space and space used in use in drive accessible by your system.
• ipconfig - lists the details of the installed network interfaces.
• netstat - reports the active connections for each protocol and the active socket details.
• top - displays a sorted list of processes and their details. Also displays summary informatino of the memory, cpu usage, and load for the system. This is similar to the Task Manager in Windows.

Tomcat Monitoring & Management

SAS Environment Manager's Tomcat management plugin provides detailed information about the health and performance of the server as well as every webapp and connector deployed in it. This capability allows customers to gain a level of visibility into the resource consumption of both the server as well as every webapp without requiring instrumentation of your Tomcat or JVM.

SAS Environment Manager's SIGAR monitoring technology provides users with information on JVM performance which offers measurements of the Tomcat server from the operating system's point of view.

SAS Environment Manager's Tomcat management technology allows you to answer questions without any instrumentation of your environment such as:

Which of my webapps is consuming the most amount of CPU?

How much memory is the Tomcat JVM process actually taking up?

SAS Environment Manager's web based portal allows you to build personalized views of monitoring data which compare things like CPU consumption for your tomcat instance, the response time of every webapp, and the load average of the machine hosting the Tomcat server. These easy to use views provide insight into Tomcat performance which help identify problems and do capacity planning for large environments. Environment Manager also provides real per-URL request response time monitoring which displays real performance data for each request serviced by your Tomcat webapps.

Administrators can use Environment Manager to collect information from Tomcat's logs and use it to generate alerts as well as track any exceptions reported to the log. Environment Manager can also track Tomcat's configuration, allowing you to audit any changes into Tomcat's configurations and measure their impact on performance and availability.

Environment Manager's Tomcat control capability allows you to perform immediate, scheduled, or alert-driven control operations on the server. It also allows users to perform per webapp control actions such as reload, deploy, and undeploy without affecting the availability of the server.

Auto-Discover your hardware and Tomcat resources
Monitor every metric, log, and configuration for all Tomcat resources in your inventory
Identify problem resources with automatic baselines for every metric
Control all your Tomcat resources on-demand, on schedule, or in response to alerts
Alert on any measurement, log, or security event in your Tomcat environment

SAS Web Server Monitoring & Management

The vfws plugin discovers a SAS Web Server installation and creates a series of resources to reflect it. The plugin obtains runtime information, such as performance metrics, status, configuration, and current capacity using the open source mod_bmx module to access the SAS Web Server framework.

Auto-Discover your your SAS Web Server installation, as well as Virtual Hosts
Monitor every metric, log, and configuration for the SAS Web Server installation, as well as Virtual Hosts
Identify problem resources with automatic baselines for every metric
Control all your SAS Web Server resources on-demand, on schedule, or in response to alerts
Alert on any measurement, log, or security event in your SAS Web Server environment

The BMX framework exposes the SAS Web Server through an HTTP endpont. mod_bmx uses two data providers to obtain metrics: mod_bmx_status and mod_bmx_vhost, respectively.

A server instance is considered available if it is found in the process table.

A virtual host is considered available if mod_bmx_vhost returns metrics for it.