Cisco: Cloud CenterPowerPack Release Notes, version 106

Version 106 of the Cisco: Cloud Center PowerPack adds the ability to discover ELK components.

  • Minimum Required SL1 Version: 8.7.1.2

Before You Install or Upgrade

Ensure that you are running version 8.7.1.2 or later of SL1 before installing "Cisco: Cloud Center" PowerPack version 106.

For details on upgrading SL1, see the relevant SL1 Platform Release Notes.

Installing or Upgrading the PowerPack

To install this PowerPack:

  1. Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
  2. In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
  3. Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
  4. Click Browse and navigate to the PowerPack file from step 1.
  5. Select the PowerPack file and click Import. The PowerPack Installer modal displays a list of the PowerPack contents.
  6. Click Install. The PowerPack is added to the PowerPack Manager page.

By default, installing a new version of a PowerPack will overwrite all content in that PowerPack that has already been installed on the target system. You can use the Enable Selective PowerPack Field Protection setting in the Behavior Settings page (System > Settings > Behavior) to prevent the new version of the PowerPack from overwriting local changes for some commonly customized fields.

If you are currently using the Dynamic Applications in this PowerPack to monitor devices, collection errors might occur for one or two polling cycles during the installation of a new version. To prevent collection errors during an upgrade, you can optionally disable collection for monitored devices before performing the following steps and re-enable collection after the upgrade.

For more information about using the PowerPack, see the Monitoring Cisco: Cloud Center manual.

Features

This release includes the following features:

  • Dynamic Applications to discover and monitor Cloud Center devices

  • Device classes for each type of Cloud Center device that SL1 monitors
  • Event policies and corresponding alerts that are triggered when Cloud Center devices meet certain status criteria
  • Sample Credentials you can use as templates to create your own Credentials to monitor Cloud Center deployments
  • Run Book Actions that automate some aspects of the device discovery and creation process

Enhancements and Issues Addressed

The following enhancements and addressed issues are included in version 106 of the "Cisco: Cloud Center" PowerPack:

  • The PowerPack now supports the discovery of ELK components. With this update, a new "Cloud Center ELK" Device Class was added to the PowerPack, and the sample "Cisco Cloud Center - HA Example" SOAP/XML Credential was updated to include a header for ELK components.
  • The "Cisco: Cloud Center CCC Port Monitor" Dynamic Application was added to the PowerPack to collect the processes and statuses of the CCC Port Monitor script.
  • The "Cisco: Cloud Center Application Resource Usage" Dynamic Application was updated to add a new "Add Suspension Policy" Collection Object.
  • An issue was addressed in which discovery was failing on RabbitMQ because it was erroneously detecting bad headers.
  • An issue was addressed that was preventing Dynamic Applications from the Cisco: ACI PowerPack from auto-aligning to the root device when the PowerPack was installed before the Cisco: ACI PowerPack.

Known Issues and Limitations

The following known issues affect version 106 of the Cisco: Cloud Center PowerPack:

  • When monitoring a high-availability deployment, the use of Basic/Snippet credentials will cause RabbitMQ Dynamic Applications to align to RabbitMQ devices, but those Dynamic Applications will not collect data. This is because SL1 discovers the RabbitMQ load balancer devices as the RabbitMQ components, rather than the actual RabbitMQ components themselves. This means that, even if you manually discover the RabbitMQ components, the PowerPack has no way of linking them with the load balancers. If you would like to collect data for the non-load balancer RabbitMQ components, you can manually align the appropriate credentials.

  • The current implementation of the AMQP: RabbitMQ PowerPack has a known issue where the data comes only from the first node in the cluster, leading to one of the nodes having incorrect data. This issue will be addressed in version 101 of the AMQP: RabbitMQ PowerPack.

  • All devices associated with a Cisco Cloud Center instance must be monitored by the same Data Collector.
  • If you delete a Cisco Cloud Center device and subsequently want to re-discover the same Cisco Cloud Center device, you must execute the following database query on the Data Collector or All-In-One Appliance that monitored the Cisco Cloud Center device:

    • DELETE FROM cache.dynamic_app WHERE key LIKE %ccc%;