Version 101 of the "SL1: Execution Environment Check" PowerPack includes several updates to the "SL1: 12.1.2 Execution Environment Check" Dynamic Application.
- Minimum Required SL1 Version: 11.3.1
All Snippet Dynamic Applications include a linked execution environment that includes any libraries needed for the snippet to run. SL1 version 12.1.2 includes a change to better isolate these environments, so one bad library does not break other Dynamic Applications.
However, these changes in SL1 12.1.2 cause some execution environments to no longer work properly after upgrading to 12.1.2, which in turn can cause multiple PowerPacks that use those problematic execution environments to not run after you upgrade.
For more information about the specific issues that can cause an execution environment in SL1 12.1.2 to not deploy or function correctly post-upgrade, see the following knowledge base article: https://support.sciencelogic.com/s/article/15301
For the 12.1.2 release, you should download and install the latest version of the "SL1: Execution Environment Check" PowerPack, which includes a Dynamic Application that can be used to detect execution environments that will fail to deploy or fail to work after they are deployed.
This PowerPack can be run on SL1 versions 11.3.1 to 12.1.2, so ScienceLogic recommends performing this check before you upgrade to 12.1.2, so long as you're currently on version 11.3.1 or later.
This document covers the following topics:
- The installation process for the PowerPack
- The features included in the PowerPack
- The enhancements included in version 101
- Using the PowerPack to Check for Problematic Execution Environments
- Resolving Library Issues with Problematic Execution Environments
Installing or Upgrading the PowerPack
To install the "SL1: Execution Environment Check" PowerPack, perform the following steps:
-
Ensure that you are running a version of SL1 between 11.3.1 and 12.1.2.
-
From the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site, search for and download the latest version of the "SL1: Execution Environment Check" PowerPack.
-
In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
-
Click the menu and choose Import PowerPack. The Import PowerPack modal appears.
-
Click and navigate to the "SL1: Execution Environment Check" PowerPack file that you downloaded in step 2.
-
Select the PowerPack file and click . The PowerPack Installer modal displays a list of the PowerPack contents.
-
Click . The PowerPack is added to the PowerPack Manager page.
Included Features
The "SL1: Execution Environment Check" PowerPack includes:
- One Dynamic Application, "SL1: 12.1.2 Execution Environment Check," which detects potentially problematic execution environments that may have difficulty running or working properly after upgrading to SL1 version 12.1.2.
Enhancements
The following enhancements are included in version 101 of the "SL1: Execution Environment Check" PowerPack:
- The following updates were made to the "SL1: 12.1.2 Execution Environment Check" Dynamic Application:
- Only one instance of the Dynamic Application can be run at a time.
- Multiprocessing support was added to enable the Dynamic Application to process execution environments more quickly.
- The Dynamic Application now stops itself after running for 12 minutes and returns the results that it was able to collect.
- The Dynamic Application now uses the same temp directory each time it runs, resulting in it overwriting the data from previous failed attempts rather than creating a new directory for each attempt.
Using the PowerPack to Check for Problematic Execution Environments
After you have installed the "SL1: Execution Environment Check" PowerPack, you must create a virtual device on which you can run the Dynamic Application that is included in the PowerPack, and then review the data collected from that Dynamic Application to determine which execution environments might not run properly in SL1 12.1.2.
To do so:
-
Go to the Device Manager page (Devices > Device Manager).
-
Click the button and select Create Virtual Device from the menu. The Virtual Device modal page appears.
-
Enter values in the following fields:
-
Device Name. Enter a name for the device.
-
Organization. Select the organization for this device.
-
Device Class. Select any device class.
-
Collector. Select a collector group.
The Dynamic Application you will need to run on the virtual device will fully use one CPU core while it is running. Therefore, ScienceLogic recommends selecting a collector group that is not already overloaded, as doing so could impact data collection.
-
-
Click to create the virtual device.
-
You must now manually align the "SL1: 12.1.2 Execution Environment Check" Dynamic Application, which was included in the PowerPack, to your new virtual device. To do so, go to the Devices page (Devices > Devices).
-
Locate your new virtual device and click its name to open the Device Investigator.
-
In the Device Investigator, click the tab.
-
Click the button at the top of the page, then click the button.
-
In the Align Dynamic Application modal, click Choose Dynamic Application.
-
Locate the "SL1: 12.1.2 Execution Environment Check" Dynamic Application and click .
-
In the Align Dynamic Application modal, de-select the Use Device SNMP Credential checkbox. Click the Choose Credential option that appears.
-
Select any credential except the default SNMP credential, and click .
-
Click to align the Dynamic Application with the virtual device. The Dynamic Application appears on the Collections tab.
-
On the tab, click the Poll Frequency value for the "SL1: 12.1.2 Execution Environment Check" Dynamic Application. A sidebar opens where you can edit the Dynamic Application properties.
-
In the Poll Frequency field, select 15 minutes, and then click .
-
Wait at least 15 minutes for collection to run.
-
From the Device Investigator, click the tab and check results from the collection. This page shows the results of the collection from the "SL1: 12.1.2 Execution Environment Check" Dynamic Application, and indicates the following information for each execution environment:
-
Environment GUID. The execution environment's globally unique identifier.
-
Environment Name. The name of the execution environment.
-
Deploys? Indicates whether the execution environment will deploy successfully on SL1 12.1.2.
-
Script Runs? Indicates whether the execution environment will be able to run Dynamic Applications successfully in SL1 12.1.2.
-
-
For each environment that has a "No" value in the Deploys? or Script Runs? columns, SL1 will trigger an event that appears on the Events page as well as on the tab of the Device Investigator for the virtual device you created.
After noting which execution environments have a "No" value in the Deploys? or Script Runs? columns, you should change the polling frequency for the "SL1: 12.1.2 Execution Environment Check" Dynamic Application to 24 hours, so the Dynamic Application stops performing collection every 15 minutes. To do so, go to the Devices page and locate the virtual device you previously created. Click its name to open the Device Investigator, and then click the tab. Click , and then click the Poll Frequency value for the "SL1: 12.1.2 Execution Environment Check" Dynamic Application. On the sidebar that opens, change the Poll Frequency value to 24 hours, and then click .
Resolving Library Issues with Problematic Execution Environments
If the "SL1: 12.1.2 Execution Environment Check" Dynamic Application indicated that you have problematic execution environments, see the following knowledge base article for resolution steps: https://support.sciencelogic.com/s/article/15301
When you are finished resolving these issues and you have confirmed that all execution environments are updated properly, you should disable the "SL1: 12.1.2 Execution Environment Check" Dynamic Application. To do so, go to the Dynamic Applications Manager page (System > Manage > Dynamic Applications) and locate the "SL1: 12.1.2 Execution Environment Check" Dynamic Application. Click its wrench icon. On the Dynamic Applications Properties Editor modal, in the Operational State field, select Disabled. Then click .