MONITOR

The MONITOR element in the Genero Application Server configuration file specifies from which machines the monitor URL is accessible. By default, the monitor page is not accessible and needs to be configured.

Important: Depending on the network configuration, the monitor is not always able to get the actual client IP address. If there is a proxy server between the client and the server, for example, the client IP address seen by the GAS may be the address from the proxy server.

Syntax

<MONITOR>
  <ALLOW_FROM>ip_address</ALLOW_FROM>[...]
</MONITOR>

The ip_address is a valid IPv4 or IPv6 address. For IPv4 it can be a complete IP address or a network address (ending with a dot)..

Child elements

Example configuring monitor access

In the default deployment monitoring is specified by the resource res.access.control, which is defined with the value NOBODY by default.
Note: MONITOR control rules will be ignored by the standalone dispatcher (httpdispatch).
Important: The standalone GAS is for development only, provided to simplify your development setup and configuration. For deployment and production systems, you must include a Web server.
To allow monitoring from hosts, in the GAS configuration file (default FGLASDIR/etc/as.xcf) you need to change the application element for MONITOR from:
<MONITOR>
   <ALLOW_FROM>$(res.access.control)</ALLOW_FROM>
    <!--
        <ALLOW_FROM>192.168.</ALLOW_FROM>
        <ALLOW_FROM>10.</ALLOW_FROM>
        <ALLOW_FROM>193.111.222.123</ALLOW_FROM>
     -->
</MONITOR>
To (for example):
<MONITOR>
  <ALLOW_FROM>127.0.0.1</ALLOW_FROM>
  <ALLOW_FROM>192.168.</ALLOW_FROM>
  <ALLOW_FROM>10.</ALLOW_FROM>
  <ALLOW_FROM>193.111.222.123</ALLOW_FROM>
</MONITOR>
In this example, the GAS monitor is reachable from localhost (127.0.0.1), 193.111.222.123 and all IP that begin with "192.168." or "10.". For more details on the monitor usage, see Monitoring Genero Application Server

Parent elements

This element is a child of one of the APPLICATION_SERVER element.