Ruxit identifies services in your environment based on the deployment units that it detects. Deployment units vary based on service type. For example, in the case of Apache web services, Ruxit looks for virtual hosts. In the case of Java web applications, Ruxit looks for web applications and context roots. While this approach certainly does represent your deployed services, in some cases it may be too granular a level of detail for your monitoring purposes. For example, you might have three virtual hosts in your Apache configuration that you view as a single logical service, rather than as three separate services. To accommodate this monitoring approach, you can set up a monitoring view of these services that evaluates these services as a single aggregated service.

Note: Only web-request services within the same process group can be merged. This approach is consistent with how Ruxit detects services, where process groups act as containers for services. Only processes of the same service type (for example, Apache web server, or Nginx) can be included in the same process group.

Have a look at the screenshot below. The two listed services represent two virtual hosts defined in the httpd.conf file. It’s correct to define two virtual hosts rather than one here, but this technical distinction doesn’t mean that the two ports actually serve two separate services. In fact it makes more sense to evaluate these services as a single merged service.

service merging

To set up service merging:

  1. Go to Settings > Service detection > Service merging.
    Notice that in the example below Ruxit has detected 8 services that are candidates for merging.
  2. Click Create merged service to view the list of mergable services.
    service merging
  3. Select one of the mergable services.
    In this example, I’ve selected the first service in the list, EasyTravelWebserver:8079.service merging
  4. Click Add on the Create merged service page to merge additional services with the selected service.
    Note that in this example there is only a single service that is considered a candidate for merging with the selected service. This is because there is only one other service in the same process group.
    service merging
  5. The merged service is now listed on the Service merging page with a Detecting service… status message (see the first service in the Merged services list below).
    The merged service becomes a fully functional service as soon as the first request comes in for the new service (see the second service in the Merged services list below).
    service merging
    The newly merged service behaves exactly like any other service, but it represents both of the underlying services. Have a look at the properties section of the Service page listed below. The EasyTravelWebserver:8079 service is now a Merged service, though the original services remain listed until they no longer receive new requests.
    service merging