Foglight 5.9.1 - Upgrade Guide

Upgrade Foglight for JMX

The latest version of the Foglight for JMX is version 5.9.8. Upgrades from version 5.9.x, 5.8.1, and 5.8.0 are supported.

Foglight for JMX is supported on Management Server 5.6.7 and later, and Agent Manager version 5.6.2.2 or later.

IMPORTANT: Foglight for JMX accepts connections from the JMX agents of version 5.9.x and 5.8.x. JMX agents of earlier versions (5.7.x) are not supported and must be upgraded for use with this version of the cartridge.

NOTE: Foglight for JMX version 5.9.8 is directly compatible with: • Foglight for Java EE Technologies version 5.9.2 and later. It should NOT be installed alongside any previous versions of Foglight for Java EE Technologies. • Foglight for Microsoft .NET version 5.9.2 and later. It can also be installed alongside of previous versions of Foglight for Microsoft .NET.

Upgrade Foglight for Microsoft .NET

The latest version of Foglight for Microsoft .NET is version 5.9.12. It supports upgrades from version 5.9.4 and later.

Upgrades from version 5.9.x are mandatory. Upgrades from version 5.6.x are optional, as version 5.6.x agents and version 5.9.6 agents can both run from the same Management Server, provided they are monitoring separate .NET® instances.

Foglight for Microsoft .NET is supported on Foglight Management Server version 5.6.7 and later.

The Nexus requires Foglight Agent Manager version 5.6.7.2 or later. Version 5.6.7.3 or later is recommended. The .NET agent requires Foglight Agent Manager version 5.6.2.6 or later.

NOTE: Foglight for Microsoft .NET version 5.9.11 is compatible with: • Foglight for Java EE Technologies version 5.9.4 and later. Do not attempt to use it alongside any earlier versions of Foglight for Java EE Technologies. • Foglight for JMX version 5.9.3 and later. Do not attempt to use it alongside any earlier versions of Foglight for JMX.

Upgrade Foglight for Microsoft .NET from version 5.9.x

NOTE: As the new version of the cartridge is installed, all Nexuses are automatically upgraded to the new version. While this happens, agents disconnect briefly and then reconnect once the new version of Nexus is restarted.

NOTE: Once an Agent Installation has been upgraded, you must reset IIS before the agents will reconnect.

NOTE: Once confirmed, the upgrade process starts and the Agents disconnect. The agents will reconnect only when the IISReset has been completed in Step g.

Configuration migration during upgrades

If you have modified the configuration files and you perform a minor version upgrade (for example from x.y.z to x.y.z+1), your modified files are preserved. The default contents of the configuration files from the new version are overwritten with your changes.

For example, you have version 5.9.3.2 currently installed and you have modified the Nexus recording.config and the .NET agent instrumentation.config. Upgrading to version 5.9.12 would overwrite the default contents of the 5.9.10 versions of those files with your file contents from 5.9.3.2. All other 5.9.12 configuration files are unchanged, and contain the default contents installed by the 5.9.12 cartridge.

NOTE: Configuration files managed through the Advanced dashboards (for example, nexus/aggregation.config) are not automatically migrated. If you have made any modifications to these files, they must be migrated manually, with the assistance of Customer Support where necessary. In addition, the nexus/compatible-builds.config file is never automatically migrated. If you have any patch build IDs, these must be manually added to the new version’s compatible-builds.config with the assistance of Customer Support.

IMPORTANT: No automatic migration occurs during an upgrade to the next major version (for example, from 5.9.x to 5.10.x).