Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
LogicMonitor’s Kubernetes monitoring involves two semantically versioned applications: Argus and the Collectorset-Controller. New versions of these applications provide bug fixes, improvements, and new features. You can see the latest available versions of these applications (and the enhancements they provide) on their respective GitHub host pages.
Argus images are tagged with semantic versioning in addition to a tag for the major version (for example, v5) which will match all images that get published with that major version (including minor improvement and bug fix increments). This ensures that new images with minor improvements and bug fixes are used automatically.
For example, for Argus version 5.0.0, the following tags are applied to the image: “v5” and “5.0.0”. If you reference “v5” in your Helm deployment at the time 5.0.0 is released, that tag would also match subsequent Argus versions 5.1.0, 5.1.1, and so on upon their release.
Opt-in is still required when a new major version is released. This means that if your Helm deployment for Argus and Collectorset-Controller currently references “latest” or hard-coded version image tags, you will need to opt into the upgrade using the instructions provided in the next section.
Ensure the following requirements are met before upgrading:
General upgrade instructions for Argus are listed next, but some major versions have specific upgrade steps. Please see LogicMonitor’s Argus GitHub page and locate the major version you’re upgrading to in order to review any version-specific steps that may be necessary.
To upgrade the Argus chart from older versions to the latest version, you require an Argus configuration file for running the helm upgrade command.
For creating .yaml configuration files for argus and collector-set controller, complete the following steps:
1. Download the configuration file template from here.
2. Get existing values using the command:
helm get values argus
3. Save in the backup configuration file.
4. Put all existing values in the downloaded configuration file at their appropriate places. And leave the remaining values at their default.
Note: If you using Argus v6.0 or later, and the existing filtering configuration contains “ * ” for excluding all the resources from monitoring, you must remove “ * ” from the filtering configuration.
With Argus v6.0, a new parameter “disableResourceMonitoring” is added for excluding all the resources of a specific type.You must specify the resourcetype in the disableResourceMonitoring parameter list, as follows:
disableResourceMonitoring
resourcetype
disableResourceMonitoring:
- nodes
- services
- deployments
For upgrading to the latest version of Argus, complete the following steps:
helm repo update
helm upgrade -f argus-config.yaml argus logicmonitor/argus
Note: You may need to recreate the Argus pod if the pods are not recreated automatically.Helm does not recreate pods if there is no change in definitions.
To check the latest version of the Argus helm chart, see Configuration templates of Helm charts values.yaml.
In This Article
