Monitoring Sensors:
+200 monitoring sensors available.

Don’t half-monitor your servers,
use our wide range of sensors and plugins…

server sensorsServer Sensors

System Sensors (CPU, RAM, disks, network interfaces, etc.).
These “standard” sensors are self-deploying and automatically install themselves in a matter of seconds.
 

Process Sensors (processes of any OS and Services for Windows).
The user’s confirmation is required before these “advanced” sensors are installed.

sensor list
Principle & Full list of System Sensors… (click)
PRINCIPLE

The solution is based on a software agent, called the “server agent”, installed on each server (physical or virtual).

 

No client-side network or firewall modifications are required in order to install the server agent, as it uses the HTTPS protocol to communicate using an outgoing connection via port 443 (the server initiates the connection to the Satelliz platform). During the installation process, the server agent is recorded on the Satelliz platform when SSL certificates are exchanged. This communication and registration method is highly secure, as the client does not open any incoming communication ports on its network and the server agent uses a single sign-on (via a certificate).

 

Installing the server agent is very simple and takes less than 30 seconds.

 

Once the server agent is installed, it scans the server and automatically installs the appropriate System Sensors (CPU, RAM, disks and network interfaces) according to each server’s configuration. This is because the System Sensors differ depending on the server’s operating system (OS).

 

Users can install (advanced) Process Sensors manually depending on their server’s role, based on the server agent’s real-time list of system processes and Windows services running on the server, providing them with a simple, direct method of choosing which processes they want to monitor.

 

All server agent and System or Process Server Sensor management (updating the agent, reconfiguring or adding sensors, etc.) is then done in the monitoring portal, eliminating the need to configure monitoring on the server itself.

 

To see the full list of sensors available, including their descriptions and the metrics (measuring points) associated with each sensor, click below.

SERVER SENSORS / SYSTEM SENSORS FOR LINUX, UNIX, MAC OS X
Sensor name Description Metrics
CPU load CPU load average

load 1m / load 5m / load 15m

CPU utilization CPU percentage used User / System / Wait – % 

fs_[partition-name]
(ex : fs_/ ou fs_/boot)

percentage of used disk space
(1 sensor per partition)
Disk usage – MB / %
Kernel Context Switches number of context switches per second,
average value on the last 90s.
Process Contexte Switches /s
Kernel Major Page Faults  number of major page faults per second,
average value on the last 90s.
Major Page Faults /s
Kernel Process Creations number of process creations per second,
average value on the last 90s.
Process Creations /s
Memory used percentage of global memory (RAM+SWAP) used compared to the RAM size  RAM usage (MB) / RAM total (MB) / SWAP usage (MB) / SWAP total (MB) / Global Memory usage (MB) / Global Memory warning / Global memory critical
Mount options of [partition-name]
(ex : / ou /boot)
state of Mount options
(1 sensor per partition)
N/A
NIC ethX counters
(ex : NIC eth0 counters)
percentage of errors on a Network Interface Controller (NIC)
(1 sensor per NIC)
RX speed / TX speed / RX bytes / TX bytes / RX packets / TX packets / RX errors / TX errors / TX collisions
NTP Time delay in ms compared with a Network time Protocol (NTP) server  Offset / Jitter 
Number of threads CPU number of threads  Threads 
TCP Connections number of TCP connections, per type  Established / Syn_sent / Syn_recv / Last_ack / Time_wait / Fin_wait1 / Fin_wait2 / Close_wait 
Uptime time since the last boot of system Uptime 
Vmalloc address space total and used size of the Vmalloc address space  Total / Used / Largest chunk
     
SERVER SENSORS / SYSTEM SENSORS FOR WINDOWS
Sensor name Description Metrics
CPU Usage CPU percentage used Global CPU (%)
Disk I/O Disk activity: Input (writing) / Output (reading) Write speed (MB/s) Read speed (MB/s) 

fs_[nom-du-disque]
(ex : fs_C:/ )

percentage of used disk space
(1 sensor per partition) 
Disk Usage (MB) 
LOG XXX
(ex : Application, HardwareEvents, IE, Security, System, Key Management Service ; …) 
error messages from log files
(1 sensor per event log)
N/A 
Memory used percentage of global memory (RAM+SWAP) used compared to the RAM size  RAM usage (MB) / RAM total (MB) / SWAP usage (MB) / SWAP total (MB) / Global Memory usage (MB) / Global Memory warning / Global memory critical 
System Time  delay compared to a time server (NTP) Offset 
Uptime time since the last boot of system Uptime  
     
SERVER SENSORS / PROCESS SENSORS FOR LINUX, UNIX, MAC OS X
Sensor name Description Metrics
process sensor
[customizable name]

calculates the number of processes currently running on the system, per type (it is possible to specify the user under which is launched the process). The type of process is defined either by the process name or by a regular expression (regex) in order to identify the concerned processes from the list of running processes. Sensors are created manually by the user.

number of processes currently executed 

     
SERVER SENSORS / PROCESS AND SERVICE SENSORS FOR WINDOWS
Sensor name Description Metrics
process sensor
[customizable name]

calculates the number of processes currently running on the system, per type (it is possible to specify the user under which is launched the process). The type of process is defined by the process name in order to identify the concerned processes from the list of running processes. Sensors are created manually by the user.

number of processes currently executed 
service sensor
[customizable name]
checks that a Windows service is currently running. The service is defined from the list of services declared on the system. Sensors are created manually by the user. N/A

   

network and Internet sensorsNetwork & Internet Sensors

These sensors are used to monitor Web services (HTTP, HTTPS, GET/POST methods, etc.), email services (POP3, IMAP, etc.), general networking services (ICMP/TCP/UDP) or specialized ones (FTP, SSH, etc.), authentication systems (LDAP, Radius, etc.), and much more.

sensor list 2
Principle & Full list of Network & Internet Sensors… (click)
PRINCIPLES

The Network & Internet Sensors are deployed on the Satelliz platform and used to monitor services that are supposed to be open to the Internet (or at least open to users outside the corporate network).

 

These sensors can be deployed without requiring any special software on the monitored resources and are installed from the monitoring portal.

 

The Sensors are classified into categories:

  • Websites: Web (HTTP, HTTPS, GET/POST methods, content checking, SSL Certificates, etc.)
  • Cloud Providers (AWS EC2, Google Compute Engine, Microsoft Azure, etc.)
  • Email Systems (POP3, IMAP, SMTP, number/age of emails and recording of email relays in a Spam database)
  • Basic Network (ICMP, TCP and UDP)
  • Authentication Systems (Radius, LDAP and Tacacs+)
  • Network Services (SSH, FTP, RDP, etc.)
  • Communication Systems (Jabber, IRC, etc.)
To see the full list of sensors available, including their descriptions and the metrics (measuring points) associated with each sensor, click below.
WEBSITES
Sensor name Description Metrics
HTTP simple connection

checks that a webpage (HTTP URL) answers correctly (HTTP code 2## or 3##) and in a predefined time, provides also the page size and the load time

Time (s) / Size (bytes) 
HTTPS simple connection

checks that a secured webpage (HTTPS URL) answers correctly (HTTP code 2## or 3##) and in a predefined time, provides also the page size and the load time

Time (s) / Size (bytes) 
HTTP(S) URL check content

checks that a content (a character chain) is present in a webpage (accessed through a GET URL – HTTP or HTTPS) and in a predefined time, notice that the expected content must be present inside the HTML source code of the page

Time (s) 
HTTP(S) URL response time checks the load time of a webpage (accessed through a GET URL – HTTP or HTTPS) Time (s) 
HTTP(S) POST check content

checks that a content (a character chain) is present in a webpage (accessed through a POST URL – HTTP or HTTPS – specifying the POST message) and in a predefined time, notice that the expected content must be present inside the HTML source code of the page

Time (s) 
HTTP redirect checks the redirection of a webpage (HTTP URL) to another webpage (HTTP URL) N/A 
SSL Cert. Expiration checks the expiration date of a SSL certificate  N/A 
     
CLOUD PROVIDERS  
Sensor name Description Metrics
AWS EC2 instance state monitor checks the number of AWS EC2 (Amazon Web Services EC2) instances on a specified Region, with the possibility to specify a TAG and the States of instances to be counted Number 
     
EMAIL SYSTEMS  
Sensor name Description Metrics
POP3 account – login checks connection to a POP3 server on a specific mailbox (login, password) N/A 
IMAP account – login checks connection to a IMAP server on a specific mailbox (login, password) N/A 
IMAP/POP3 messages count checks the number of messages (emails) in an IMAP or POP3 mailbox Number 
IMAP messages age checks age of oldest message (email) in an IMAP mailbox Age (s)
SMTP connection & mail sending checks connection to a SMTP server and sending of a message (email)  Responses Time 
SPAMCOP relay DB check checks that a mail relay server is not present in the  SPAMCOP database N/A 
SORBS relay DB check

checks that a mail relay server is not present in the  SORBS database

N/A 
     
BASIC NETWORK
Sensor name Description Metrics
Ping (ICMP) checks the PING of an IP address (or a server) and in a predefined time, provides the latency (or RTA – response time average) and the packet lost rate    RTA – response time average (ms) / Packet Lost (%)
TCP port connection checks the connection to a TCP port on a specified IP address (or a server) and in a predefined time, provides the response time Response time (ms) 
TCP Banner connection checks the content (character chain) of a TCP Banner while connecting to a TCP port on a specified IP address (or a server) and in a predefined time, provides the response time  Response time (ms)  
UDP banner connection

checks the content (character chain) of a UDP Banner while connecting to a UDP port on a specified IP address (or a server) and in a predefined time, provides the response time

Response time (ms)  
     
AUTHENTICATION SYSTEMS
Sensor name Description Metrics
LDAP account – login checks connection to a LDAP server using a specified user (username, password) and in a specified time N/A  
LDAP account – login (SSL)

checks secured connection (via SSL) to a LDAP server using a specified user (username, password) and in a specified time

N/A 
RADIUS account – login

checks connection to a RADIUS server using a specified user (username, password, secret) and in a specified time

N/A  
Tacacs+ account – login

checks connection to a Tacacs+ server using a specified user (key, username, password) and in a specified time 

N/A  
     
NETWORK SERVICES    
Sensor name Description Metrics
FTP port connection

checks connection to a FTP server (TCP port to specify) and in a predefined time, provides the response time of the server 

Response time (ms) 
FTP Banner connection vérifie un contenu (chaine de caractère) de la bannière présentée par un serveur FTP, suite à la connexion au serveur (port TCP à spécifier)  dans un temps donné, fournit le temps de réponse du serveur Response time (ms)  
FTP account – number of files

checks the number of files present in a specified folder of a FTP server, connecting with a specified user (username, password)

Number 
TFTP account – download file checks the load time of a file from a TFTP server  Time (s) 
SSH port connection checks the connection to a SSH server (TCP port to specify) and in a predefined time, provides the response time of the server  Response time (ms)   
SSH version check checks that the SSH version is the specified one  N/A 
DNS request test checks the DNS resolution for a specified server  N/A 
SQUID connection checks the connection to a SQUID proxy and in a predefined time, provides the response time of the server  Number 
VNC port connection

checks the connection to a VNC server, provides the response time of the server

Response time (ms) 
RDP port connection checks the connection to a RDP server, provides the response time of the server Response time (ms)  
SAMBA list of shares (anonymous)

checks the list of shares on a Samba server, provides the list of shares

Number 
     
COMMUNICATION SYSTEMS    
Sensor name Description Metrics
IRC port connection checks the connection to a IRC server, provides the response time of the server Response time (ms)   
IRC account – login

checks the connection to a IRC server with a specified user (username, password), provides the response time of the server  

Time (ms)   
Jabber port connection checks the connection to a Jabber server, provides the response time of the server  Response time (ms)   

   

application pluginsApplication (& DB)
Plugins

The Application Plugins complement the System Sensors and provide detailed, application-specific monitoring.

 

These plugins cover the latest widely-used Web technologies (Apache, Nginx, JBoss, Tomcat, MySQL, etc.).

plugin list
Principle & Full list of Application Plugins… (click)
PRINCIPLE

Application Plugins are installed onto a server agent directly from the monitoring portal. Several plugins can be installed on the same server.

 

Each plugin consists of a set of sensors used to monitor a particular application. All Application Plugins are predefined and preconfigured.

 

They cover the major commercially-available Web technologies.

 

The plugins are classified into categories:

  • Web Servers (HTTP servers)
  • Application engines (Java engines and other application engines)
  • Databases (relational or NoSQL non-relational)
  • Others (Cache, etc.)

 

To see the full list of Application Plugins available, including their descriptions and the sensors/metrics (measuring points) associated with each sensor, click below.

WEB SERVERS
Plugin name Description Sensors / Metrics

Apache Web Server

Monitors a Apache web server instance per plugin.

 

During plugin configuration, the Server Status URL is required. In case of a multi-instance installation, several plugins can be installed in parallel with some different Server Status URL.

List of 8 Sensors (Metric 1 / Metric 2 / etc.): 

  • Avg. bytes per request (Average number -bytes per request)
  • Avg. bytes per second (Average number -bytes served per second)
  • Avg. requests per second (Average number – requests per second)
  • Daemon CPU load (percent)
  • Daemon uptime (uptime in seconds)
  • General status (Connection time in seconds)
  • Threads by job (number of threads)
  • Workers busy/idle (busy workers / idle workers – number)

Nginx Web Server

Monitors a Nginx web server instance per plugin.

 

During plugin configuration, the Nginx State URL is required. In case of a multi-instance installation, several plugins can be installed in parallel with some different Nginx State URL.

List of 3 Sensors (Metric 1 / Metric 2 / etc.): 

  • Active connections (number)
  • Connections by state (reading / writing / waiting – number)
  • General status (Connection time in seconds)
APPLICATION SERVERS
Plugin name Description Sensors / Metrics
Jboss

Monitors a Jboss application server instance per plugin, including several Webapps and Datasources.

 

During plugin configuration, the Webapps and Datasources to monitor are specified.

List of 7 Sensors (Metric 1 / Metric 2 / etc.): 

  • Class_loading_stats (UnloadedClassCount / LoadedClassCount / TotalLoadedClassCount)
  • Connection_pool_DefaultDS (Connections – number)
  • Garbage_collector (gcsweep.collection_count / gccopy.collection_time / gccopy.collection_count / gcsweep.collection_time – number and seconds)
  • Memory_usage (non_heap.used / heap.commited / non_heap.max / heap.used, heap.init / non_heap.commited / heap.max / non_heap.init – MB)
  • Threading_stats (DaemonThreadCount / PeakThreadCount / ThreadCount / TotalStartedThreadCount – number)
  • Uptime (JBoss uptime in seconds)
  • Webapp_host=localhost,path=/ (maxActive / activeSessions – number – one sensor per WebApp)

 

Tomcat

Monitors a Tomcat application server instance per plugin.

 

During plugin configuration, server name (where is installed the application instance, localhost by default), JMX port and Java Home are required.

List of 7 Sensors (Metric 1 / Metric 2 / etc.):

  • Uptime (Tomcat uptime in seconds) 
  • Memory used [heap] (used / commited / init / max)
  • Memory usage [non-heap] (used / commited / init / max)
  • Memory commitment (heap / non-heap / “%s heap / %s non-heap – commited per second)
  • Thread count (count / peak / daemon -
    number)
  • Thread starting rate (started threads – number per second)
  • Active web applications (number of running WebApps)

 

 

DATABASES
Plugin name Description Sensors / Metrics

MySQL

Monitors a MySQL database instance per plugin.

 

During plugin configuration, server name (where is installed the database instance, localhost by default), a user to access database instance (user, password) and TCP port (or Unix Socket) are required.

 

In the case of a multi-instance installation, it is possible to specify the TCP port (or the Unix Socket), and then several plugins can be installed in parallel with different TCP ports (or Unix Sockets). 

 

In the case of a database instance installed on a remote server, it is possible to specify the server name (or IP address) of remote host. 

 

The plugin can monitor, as an option, the Slave role of a MySQL database (Master/Slave installation). 

List of 13 Sensors (Metric 1 / Metric 2 / etc.):

  • Aborted_clients/connections (aborted clients / failed connections – number)
  • Active_slow_queries (number of long running queries / time of longest in seconds)
  • Connections (number)
  • General_status (connection time in seconds)
  • InnoDB_page_cache_hit_ratio (percent)
  • InnoDB_page_cache_usage (percent)
  • InnoDB_row_lock_time (time in ms)
  • InnoDB_row_lock_waits (number)
  • Open_files (number)
  • Percent_of_temporary_tables_on_disk (percent)
  • Statement_statistics (com_select / com_insert com_update / com_delete / com_replace – number ; r/w ratio – percent)
  • Transactional_statistics (com_commit / com_rollback – number ; rolled_backed / w/c ratio – percent)
  • Slave_status (Replication delay in ms)
MongoDB

Monitors a MongoDB database instance per plugin.

 

During plugin configuration, server name (where is installed the database instance, localhost by default), a user to access database instance (user, password) and TCP port (or Unix Socket) are required.

 

In the case of a multi-instance installation, it is possible to specify the TCP port (or the Unix Socket), and then several plugins can be installed in parallel with different TCP ports (or Unix Sockets). 

 

In the case of a database instance installed on a remote server, it is possible to specify the server name (or IP address) of remote host. 

 

In option, the plugin can monitor the SSL access to the database

 

List of 18 Sensors (Metric 1 / Metric 2 / etc.): 

  • Asserts (total / msg / regular / warning / user – number per second)
  • Collections (number)
  • Connect (time to connect in seconds)
  • Connections (percent used, number of current, number of available)
  • Current_lock (percent) 
  • Databases (number)
  • Database_size (size in MB)
  • Flushing (average flush time in seconds)
  • Index_miss_ratio (percent)
  • Journaled (size in MB)
  • Journal_commits_in_wl (number of commits in DB write lock)
  • Last_flush_time (time in ms)
  • Lock (percent)
  • Memory (usage / mapped / virtual / mapped with journal – in GB)
  • Opcounters (total / getmore / insert / update / command / query / delete – number)
  • Page_faults (number per second)
  • Queues (total / reader / writter – number)
  • Write_data_files (size in MB)
Redis

Monitors a Redis database instance per plugin.

 

During plugin configuration, server name (where is installed the database instance, localhost by default), a password to access database instance and TCP port (or Unix Socket) are required.

 

In the case of a multi-instance installation, it is possible to specify the TCP port (or the Unix Socket), and then several plugins can be installed in parallel with different TCP ports (or Unix Sockets). 

 

In the case of a database instance installed on a remote server, it is possible to specify the server name (or IP address) of remote host. 

List of 5 Sensors (Metric 1 / Metric 2 / etc.): 

  • Changes since last save (number)
  • Connection time (time in seconds)
  • Mem fragmentation ratio (percent)
  • Memory used (memory used / peak memory used – MB)
  • Uptime (Uptime in seconds)

 

OTHERS
Plugin name Description Sensors / Metrics
Memcached

Monitors a Memcached  instance per plugin.

 

During plugin configuration, server name (where is installed the  instance, localhost by default) and TCP port (or Unix Socket) are required.

 

In the case of a multi-instance installation, it is possible to specify the TCP port (or the Unix Socket), and then several plugins can be installed in parallel with different TCP ports (or Unix Sockets). 

 

In the case of a database instance installed on a remote server, it is possible to specify the server name (or IP address) of remote host. 

List of 8 Sensors (Metric 1 / Metric 2 / etc.):

  • Connection time (time in seconds)
  • Uptime (time in seconds)
  • Memory used (used / limit – in MB)
  • Items in cache
  • Network traffic (read / write – in bytes)
  • GET/SET requests count (cmd_get / cmd_set – number)
  • Connections (new connections per seconds / current connections – number)
  • Resource usage (rusage_user / rusage_system – percent)

   

custom pluginsCustom Plugins

Custom Plugins are used to:

  • create custom sensors so that any technical or business metric can be monitored!
  • reuse the powerful commercially-available Nagios plugins without requiring any technical expertise.

 

universal plugin configuration
Principle & Full list of Custom Plugins… (click)
PRINCIPLES

Custom Plugins are installed onto a server agent directly from the monitoring portal. Several plugins can be installed on the same server.

 

Each plugin can be used to create a set of sensors. You choose which metrics you want it to read and return to the Satelliz platform (they can be of any type). Any metric whose name and value you can produce from your system, application or script can be returned very simply to the Satelliz platform.

 

To see the full list of Custom Plugins available, including their descriptions and the sensors/metrics (measuring points) associated with each sensor, click below.

CUSTOM PLUGINS
Plugin name Description Sensors / Metrics
TCP Listener

opens a TCP listener port on the monitoring server agent, on which the user can “send” metrics/values collected on a regular schedule.

Metrics/values can be generated by an application, or a simple script (via scheduled job, crontab).

 

Sensors, status, outputs, metrics and graphs are totally customizable.

Customizable 
Custom Script

allows the monitoring server agent to orchestrate a customizable script.

The related script is written in Python, and it can control other scripts (SQL, etc.)

Sensors, status, outputs, metrics and graphs are totally customizable.

Customizable
Nagios Wrapper

allows the monitoring server agent to orchestrate a Nagios compatible plugin.

Sensors, status, outputs and metrics are those of Nagios plugin. The graphs are customizable. 

Same as related Nagios plugin