When it comes to the Operations Console there are a few configuration options you want to make sure you are aware of.

These configuration options have to do with clustering and auto discovery of engines by the Operations Console.

By default, Flux will scan your network for any Flux engines it finds. If you are in a stable environment where new engines aren't being added, you can skip this step and set auto_discovery to false in your .fluxwebapp.properties file.

The .fluxwebapp.properties file exists in either the /home/username/ or the C:\Documents and Settings\username\ directory and contains configuration options that pertain directly to the Operations Console.

To turn auto discovery off, add the following configuration option to your .fluxwebapp.properties file

auto_discovery_enabled=false

If you look at the .fluxwebapp.properties file you will notice several other entries, all of these entries relate to the engine, including cluster id (which you can cross reference with the flux_cluster table) and other engine information that the engines grid in the Operations Console uses.

The other set of configuration options you will want to set in your .fluxwebapp.properties file, relate to clustering.

If you have any clustering options set on your engine (cluster_enabled, cluster_networking, cluster_networking_tcp_hosts, etc.) you will also need to set them in your .fluxwebapp.properties file.

This is especially important if you have turned cluster_networking communication from UDP multicast to TCP point to point communication. In order for the real time monitor to work successfully, you will need to set the cluster_networking_tcp_hosts configuration option in the .fluxwebapp.properties file and in your engine configuration.