If we run monit summary, it lists multiple services. May we know which service is responsible for what ?
Service Name │ Status │ Type │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ abca2398 │ OK │ System │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ Xvfb │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ webdriver-agent │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ tunnel-client │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ api │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ httpbroker │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ assetsmanager │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ resultbroker │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ fpm │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ redis-server │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ rbtm1-Xvfb │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ rbtm2-Xvfb │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ rbtm3-Xvfb │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ rbtm4-Xvfb │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ rbtm5-Xvfb │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ rbtm6-Xvfb │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ php-fpm │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ nginx │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ fcgiwrap │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ exim4 │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ docker │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ bm_proxy │ OK │ Process │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ devshmfs_warning │ OK │ Filesystem │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ devshmfs_critical │ OK │ Filesystem │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ homefs_warning │ OK │ Filesystem │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ homefs_critical │ OK │ Filesystem │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ optfs_warning │ OK │ Filesystem │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ optfs_critical │ OK │ Filesystem │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ rootfs_warning │ OK │ Filesystem │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ rootfs_critical │ OK │ Filesystem │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ tmpfs_warning │ OK │ Filesystem │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ tmpfs_critical │ OK │ Filesystem │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ varfs_warning │ OK │ Filesystem │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ varfs_critical │ OK │ Filesystem │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ selenoid-docker │ OK │ Program │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ rbtm1 │ OK │ Program │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ rbtm2 │ OK │ Program │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ rbtm3 │ OK │ Program │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ rbtm4 │ OK │ Program │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ rbtm5 │ OK │ Program │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ rbtm6 │ OK │ Program │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ jmeter4-agent │ OK │ Program │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ jmeter2-agent │ OK │ Program │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ fpm-agent │ OK │ Program │
├─────────────────────────────────┼────────────────────────────┼───────────────┤
│ bm_proxy_open_fd │ OK │ Program
Release : SAAS
Component : APP SYNTHETIC MONITOR ENVIRONMENTAL
The services are the following:
abca2398 |
Memory consumption service |
this service is named by the hostname (i.e. the name is different on each OPMS) and checks the memory consumption is below 90% |
Xvfb |
Xvfb or X virtual framebuffer is a display server implementing the X11 display server protocol. |
It is used by the old Firefox agent. Firefox cannot run without display. This checks if the linux Xvfb daemon is running. |
webdriver-agent |
Running web driver checks |
This is the java agent that is responsible for webdriver monitor checks. It prepares and runs the checks using selenoid (see selenoid-docker service below). One instance is running only (using threads for concurrency) |
tunnel-client |
Tunneling Client |
Interface between OPMS and ASM backend. It is creating a connection between tunnel server and the OPMS. The monitor checks are sent by the scheduler (running on ASM core servers) through this secure channel as a proxy to the API (see below) |
api |
Api process |
Accepts check requests through the Tunnel Client, forwards them, maintains status. |
httpbroker |
HTTP Router. |
API goes through http broker and connects to PHP/CGI checkers. The HTTP Broker is used to communicate with historic Check Agents that communicate over HTTP themselves, instead of listen on a queue in Redis. The function of the HTTP Broker is to listen on the Redis queue for the chosen agent, call the agent synchronously over HTTP, and push back the result into the Result Queue in Redis for the API to process. The HTTP Broker uses a set of empirically determined timeouts that should work well with the timeouts configured in the Check Agents, the SmartAPI and the Scheduler; be careful when changing these.
|
assetsmanager |
Check Results manager. |
The final component of the SmartPoP is the Assets Manager, which is responsible of storing Check Results and assets, and managing their lifetime. It is also used for old agent only that cannot communicate with redis directly. New agents (like webdriver) manage the asset storage themselves. Next to a set of performance metrics, each check can output check detail objects. The Check agents can post assets to the Asset Manager via Redis. The Assets Manager will collect and persist them on disk. It will also keep track of expiry times (again via Redis), and purge the items that have expired.
|
resultbroker |
Check Results sender. |
The Result Broker is a component in the SmartPoP that is responsible for sending asynchronous check results back to the client callbacks. This is only needed when the client provided a ?callback URL when requesting a check, something that the Scheduler currently does not do. The Result broker support sending HTTP callbacks, but could be extended to support multiple callback protocols. |
fpm |
Full Page Monitor Checker |
The old full page monitor agent written in python and based on webkit. In 10.7, it will be replaced with the new fpm agent (see below) |
redis-server |
Redis is an open source (BSD licensed), in-memory data structure store, used as database, cache and message broker. The redis-server command is a command line to launch a Redis server. |
Redis is used for storing the check status and result and also as a queue for incoming checks. |
rbtm1-Xvfb |
Real Browser Monitoring checking. Xvfb or X virtual framebuffer is a display server implementing the X11 display server protocol. |
This is the "virtual screen" for the old Firefox check agent (rbtm). Based on number of monitors installer prepares several instances of firefox agents (rbtmX) and its corresponding virtual screens (rbtmX-Xvfb). |
rbtm2-Xvfb |
Real Browser Monitoring checking. Xvfb or X virtual framebuffer is a display server implementing the X11 display server protocol. |
another instance |
rbtm3-Xvfb |
Real Browser Monitoring checking. Xvfb or X virtual framebuffer is a display server implementing the X11 display server protocol. |
another instance |
rbtm4-Xvfb |
Real Browser Monitoring checking. Xvfb or X virtual framebuffer is a display server implementing the X11 display server protocol. |
another instance |
rbtm5-Xvfb |
Real Browser Monitoring checking. Xvfb or X virtual framebuffer is a display server implementing the X11 display server protocol. |
another instance |
rbtm6-Xvfb |
Real Browser Monitoring checking. Xvfb or X virtual framebuffer is a display server implementing the X11 display server protocol. |
another instance |
php-fpm |
PHP FastCGI Process Manager |
Some agents are written in PHP. PHP-FPM maintains pools (workers that can respond to PHP requests). |
nginx |
Nginx, stylized as NGINX, nginx or NginX, is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache. Ngnix master process |
With ASM, serves as a HTTP server, forwards requests to API and to CGI, PHP checkers |
fcgiwrap |
Fast CGI Wrapper used to communicate with a web server |
It is a simple server for running CGI applications over FastCGI. It provides CGI support to nginx. |
exim4 |
Exim is a message transfer agent (MTA) for use on Unix systems connected to the Internet. |
It is used only if customer selects the OPMS status to be sent via email. It sends these messages. |
docker |
Docker is a set of platform as a service products that use OS-level virtualization to deliver software in packages called containers. |
Used to run the Docker process associated with OPMS |
bm_proxy |
BrowserMob Proxy allows you to manipulate HTTP requests and responses and much more. |
This is an http proxy. RBTM (old firefox)and the old FPM checkers use it as a proxy for collecting metrics. New webdriver and FPM agents do not use it any more. |
devshmfs_warning |
File Space warning for /dev/shm (tmpfs). Warning when x% free space |
monitoring if the filesystem capacity is sufficient |
devshmfs_critical |
File Space warning for /home Warning when x% free space |
monitoring if the filesystem capacity is sufficient |
homefs_warning |
File Space warning for /home Warning when x% free space |
monitoring if the filesystem capacity is sufficient |
homefs_critical |
File Space warning for /home Warning when x% free space |
monitoring if the filesystem capacity is sufficient |
optfs_warning |
File Space warning for /opt Warning when x% free space |
monitoring if the filesystem capacity is sufficient |
optfs_critical |
File Space warning for /opt Warning when x% free space |
monitoring if the filesystem capacity is sufficient |
rootfs_warning |
File Space warning for /root or / Warning when x% free space |
monitoring if the filesystem capacity is sufficient |
rootfs_critical |
File Space warning for /root or / Warning when x% free space |
monitoring if the filesystem capacity is sufficient |
tmpfs_warning |
File Space warning for /tmp Warning when x% free space |
monitoring if the filesystem capacity is sufficient |
tmpfs_critical |
File Space warning for /tmp Warning when x% free space |
monitoring if the filesystem capacity is sufficient |
varfs_warning |
File Space warning for /var Warning when x% free space |
monitoring if the filesystem capacity is sufficient |
varfs_critical |
File Space warning for /var Warning when x% free space |
monitoring if the filesystem capacity is sufficient |
selenoid-docker |
Starts selenium docker process |
This service is used as a selenium grid for webdriver checks. It provides functionality to run checks in firefox or chrome and record video. Webdriver agent is communicating with this service. |
rbtm1 |
Real Browser Monitoring checking |
Old Firefox monitor (real browser). It is obsolete and if customer is not scheduling / using this monitor type, it can be stopped to save CPU and memory. The more instances (rbtmX) are running the more firefox checks can be performed in parallel. Each rbtmN is using corresponding rbtmN-Xvfb as a virtual screen. If rbtmN are stopped the corresponding rbtmN-Xvfb can be stopped too. |
rbtm2 |
Real Browser Monitoring checking |
another instance |
rbtm3 |
Real Browser Monitoring checking |
another instance |
rbtm4 |
Real Browser Monitoring checking |
another instance |
rbtm5 |
Real Browser Monitoring checking |
another instance |
rbtm6 |
Real Browser Monitoring checking |
another instance |
jmeter4-agent |
Jmeter 4 Agent process |
Jmeter agent that handles the Jmeter checks (script with version 3 and above). |
Jmeter2-agent |
Jmeter 2 Agent process |
Jmeter agent that handles the Jmeter checks (script with version 2) |
fpm-agent |
Full Page Monitor Agent Process |
This is the new full page monitor agent written in Java that will replace old FPM agent (see above). One instance is running only (using threads for concurrency) |
bm_proxy_open_fd |
monitoring of browser mob proxy |
RBM, FPM checkers use it for collecting metrics. This monitors if the file descriptor is present. |