Chat now with support
Chat with Support

Foglight 5.7.5 - Upgrade Guide

Understand product versions Best practices Upgrade the Foglight Management Server Upgrade the Foglight Agent Manager Upgrade the Application Monitoring cartridges Upgrade the Database cartridges Upgrade the End User Management cartridges Upgrade the Infrastructure Management cartridges Upgrade the Integration cartridges Upgrade the cartridges in a federated or High Availability (HA) environment Appendix: Deploy an agent package using the browser interface

Upgrade Foglight for JMX

The latest version of the Foglight for JMX is version 5.9.7. 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.

3
From the Agent Hosts or Agent Status dashboard, deploy the JMX agent package to all Agent Manager hosts that you want to upgrade.

Upgrade Foglight for Microsoft .NET

The latest version of Foglight for Microsoft .NET is version 5.9.11. 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.

Upgrade Foglight for Microsoft .NET from version 5.9.x

1
Install the 5.9.11 cartridge (ApplicationServers-DotNET-5_9_11.car) as you would install a new cartridge. Do not delete or uninstall the previous version. For cartridge installation instructions, see “Installing Foglight cartridges” in the Foglight Administration and Configuration Help.
a
On the navigation panel, under Dashboards, click Application Servers > Administration > Application Servers Administration.
f
A task is added to the Task History list at the bottom of the view. Check the Result column for information on the upgrade process and its status.

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.11 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.11 configuration files are unchanged, and contain the default contents installed by the 5.9.11 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.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating