Component compatibility

Although certain version combinations may be compatible, it is strongly advised for all users to upgrade all components as soon as possible to the same version as the server.

Compatibility and Support

Components are said to be compatible, if they can connect and offer any kind of functionality together. For a specific feature to work, the support of all involved components (Agents, Collectors, Server, Client) is required.

Example: Infrastructure: Process Availability

When using 6.2 Host Agents with a 6.5 Server and Client, you can configure Process Availability patterns, but these have no effect and do not fire incidents as the 6.2 Agent does not support them. This feature was introduced starting with 6.5.

Agent-Collector Compatibility

Agents need to have the same or lower version (eg. 6.5, 7.0, ..) than the Collector. Compatibility is guaranteed for Collectors of supported versions, but typically also true for all Agent versions greater than 5.6.

Bootstrapped Agents are upgraded automatically upon restart of the monitored application up to the version of their Collector. Therefore, upgrade first the Server, then Collectors and last the Agents.

Collector-Server Compatibility

Collectors need to have the same or lower version (eg. 6.5, 7.0, ..) than the Server. Compatibility is guaranteed for Agents of supported versions, but typically also true for all Collector versions greater than 6.0

Collectors are upgraded manually like Servers.

Client-Server Compatibility

The major and minor version of the client has to match that of the Server. Lower-version Clients can auto-upgrade to the Server version if the major version matches.

Examples:

  • 6.5.0 Client cannot connect to a 2017 May (7.0) Server - requires a new installation
  • 6.5.0 Client can connect to a 6.5.10 Server
  • 6.3.0 Client when connecting to a 6.5.0 Server can auto-upgrade to 6.5.0.
  • After such an auto-upgrade: a 6.5 Client cannot connect to a 6.3 Server