Cloudmon License Activation and Renewal

License Activation

Installation and Deployment

License Activation

View your current Cloudmon license details and extend the license when additional capacity or renewal is required. License keys are provided by the Cloudmon support team.

Viewing License Details

Navigate to Settings → License. The License Information page shows your organisation name, the editions and capabilities enabled on your deployment, and the license expiry date alongside how long remains before it expires.

Licenses are divided into two groups: Base Licenses, which every monitored resource consumes, and Add-on Licenses, which are consumed only by the specific features in use.

SectionWhat it shows
EditionsBadges indicating the editions and capabilities enabled on the deployment, such as Pro, MSP Edition, and AI Assistance.
ExpiryThe date and time the license expires, with the remaining duration shown alongside it.
Base LicensesEntity and Availability license usage, each shown as consumed against total with a percentage and a usage bar.
Add-on LicensesUsage for each add-on feature enabled on the deployment, shown in the same consumed against total format.

Base License Consumption

LicenseWhat consumes it
EntityEach monitored resource consumes one Entity license.
AvailabilityEach monitored availability check consumes one Availability license.

Add-on Licenses are consumed in addition to the Entity license for the resource. The add-ons shown depend on which are enabled for your deployment and include NetFlow, NCM, Log Analyzer, DEM, SPM, and IPAM. Log Analyzer usage is broken down further by source, covering SNMP Traps, Syslog, and Windows Event Logs. IPAM consumes one license per used IP address.

License Coverage and Breakdown

Two views are available for each base license, opened from different controls.

The information icon next to Entity or Availability opens a coverage view listing every resource type that consumes that license, grouped by category. For Entity licenses this covers network devices including the full Cisco Meraki range, servers monitored by agent or WMI, VMware, Hyper-V and Nutanix entity types, databases, cloud resources, synthetic monitors, and plugins. Use this to determine in advance whether a resource type will consume a license.

The View Breakdown button opens a usage view showing actual current consumption. It reports the total used against the total available, then breaks that down by resource type with the count of monitored resources and each type's percentage of total usage. The Entities Breakdown is hierarchical, so a category such as Virtualization can be expanded to show VMware, Hyper-V and Nutanix individually, and expanded again to reach specific entity types. Both breakdowns can be exported using the Export button.

How Licensing Works

Click "How it works?" on the License Information page to open a reference explaining how licenses are consumed in combination.

The underlying rule is that each monitored resource consumes one Entity license, and add-on features consume their respective add-on license in addition. 

NotesNote: Syslog and Trap each consume a separate Log Analyzer license. A device with both Syslog and Trap enabled consumes two Log Analyzer licenses.

Extending the License

  1. Navigate to Settings → License and click the Extend License button.
  2. An Installation ID is displayed. Copy this ID.
  3. Contact the Cloudmon support team and provide the Installation ID along with the number of additional licenses required. Refer to How to Contact Support for contact options, or email support@cloudmon.ai
  4. The Cloudmon support team will generate and provide a License Key.
  5. Return to the Extend License section in Cloudmon and enter the provided License Key in the appropriate field.
  6. Establish an SSH session with the Cloudmon Controller server using a root or sudo-enabled account and restart all Cloudmon services to apply the new license key:
service cloudmon-controller@* restart

All Cloudmon services will stop and restart. This takes approximately 1 to 3 minutes. Monitoring and alerting will be briefly interrupted during this time -- schedule the restart during a maintenance window if continuous monitoring is required.

When the restart is complete, each service listed will show active (running) in the terminal output. If any service shows failed, contact Cloudmon Support before proceeding.

Troubleshooting

SymptomLikely CauseFix
License key is rejected when entered.The key was generated against a different Installation ID, or was copied with extra whitespace.Re-copy the Installation ID from the Extend License screen and confirm with the support team that the key was generated for that exact ID. Paste the license key carefully to avoid leading or trailing spaces.
SSH restart command returns a permission error.The logged-in SSH user does not have root or sudo privileges.Run the command as root or prefix with sudo: sudo service cloudmon-controller@* restart. If you do not have sudo access, contact your system administrator.
Controller web interface is unreachable after the service restart.Services are still starting up, or one or more services failed to start.Wait 3 minutes and refresh the browser. If still unreachable, run service cloudmon-controller@* status to identify any failed service and contact Cloudmon Support.