Discussion Forums
A place for dialogue and discovery about our products and services
Resource Library
Access our collection of helpful videos, guides, templates, and more
User Groups
Connect with members that have common interests or goals
Node Navigation
Recent Content
Versa Syslog Alerts
Hi - We are trying to create events from Versa syslog alarms. The format of the syslog message is in the below URL. Syslog Message Format Forwarded by Versa Analytics : Versa Support The issue is the PRI is missing from the syslog header and rsyslog does not create the alert in SL1. Is there a way to use a rsyslog policy to create an alert for these messages missing the PRI? If I use the same syslog message and add <165> to the start of the message for the PRI it works. Thanks
APM Monitoring for ScienceLogic
Hi All, Anyone thought of monitoring the ScienceLogic stacks with full stack observability tools like APPD, Dynatrace etc.? Basically i am interested to see what is happening inside the SL1 appliance like DC ,MC and CDB process level . Whether SL1 supports to install apm agents in the appliance.Cisco: UCS Standalone Rack Server v105 Py3 PowerPack Release Notification
We are pleased to announce that the Cisco: UCS Standalone Rack Server v105 Py3 PowerPack has been released. The download for this release can be found on the Support Portal under the PowerPack filename: https://support.sciencelogic.com/s/release-version/aBu0z000000XZLqCAO/cisco-ucs-standalone-rack-server Enhancements and Issues Addressed The following enhancements and addressed issues are included in this release: Converted the "Cisco UCS SA Reclassification" Dynamic Application to Python 3. Created the new "Cisco: UCS SA Environment v105" execution environment to support the change to Python 3. Updated the "Cisco: UCS Device Class Realignment" run book action policy to run with the new "Cisco: UCS SA Environment v105" execution environment. Updated the "Cisco: UCS Standalone Rack Server Reclassification" run book action policy to remove hyphens from device model names so that devices can be discovered. (Cases: 00360803, 00400242) Updated the run book action log location and name to "/var/log/sl1/cisco_ucs_sa_rba.log" Updated the "Cisco UCS SA Reclassification" Dynamic Application to support sslverifypeer, certpath, and proxy information provided in a credential. Please refer to the Cisco: UCS Standalone Rack Server v105 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Cisco: UCS Standalone Rack Server v105 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Cisco: UCS Standalone Rack Server v105 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Cisco: UCS Standalone Rack Server v105 Py3 PowerPack Release can be found in the Release NotesAP2 release IcePop
We're happy to announce that AP2 IcePop release (8.17.23.18) is now available! This release includes improvements to the Service Policy tab of the Service Investigator page, service policy management from the Edit Service Policy page; additional bulk actions on the Devices page and better visibility of event data on the Device Investigator. Please see the associated Release Notes for more information on these and other changes found in this release. You can download IcePop and associated release notes following this link: https://support.sciencelogic.com/s/release-file/aBtVL0000000inR0AQ/icepopAP2 release IcePop.01
We're happy to announce that AP2 IcePop.01 release (8.17.23.45) is now available! This release fixed critical bugs in IcePop release (8.17.23.18). If you have deployed IcePop, it's recommended that you deploy IcePop.01 to take these fixes. Before you install or upgrade to AP2 IcePop.01, ensure you are running one of the following SL1 versions: 12.2.3, 12.2.4.1, 12.2.5 12.3.0 You can download IcePop.01 and associated release notes following this link: https://support.sciencelogic.com/s/release-file/aBtVL0000000sA50AI/icepop01Restorepoint 5.6 03262025 Release
Hello - We are pleased to announce an important update to our Restorepoint appliances. This afternoon, the team pushed out the Restorepoint 5.6 03262025 release to all appliances. This release provides significant enhancements to Domains, allowing you to limit user access based on domain assignment. Domain support has been added to the release as follows: You can now add a Domain ID to device commands, command schedules, reports, report schedules, and device policies. NOTE--If a command is assigned to a command schedule, you cannot delete the command. Likewise, if a report is assigned to a report schedule, you cannot delete the report. You can now add multiple Domain IDs to Commands and Reports. When creating or editing a credential, agent, command, or policy, devices shown in the list are filtered based on the domain to which they belong. If a device command, command schedule, report, report schedule, or device policy is in the global domain, any global domain user with the correct permissions can view or edit it. Users assigned to the global domain with the appropriate permission within the global domain can create or change any element that belongs to more than one domain. Caveats: You cannot delete a label, command, policy, agent, or credential that is assigned to a device. You cannot change the domain of a label, command, policy, agent, or credential when it is assigned to a device which shares that domain. You cannot change the domain of a report when it is assigned to a report schedule which shares that domain. If a user does not have access to the same domain as a report, report schedule, command, command schedule, or policy, the form appears disabled. Additionally, important changes were included for permissions: The following permissions were added to allow for interactions with schedules, such as pausing or postponing schedules, on the Schedules page: View All Schedules Modify All Schedules The following permissions replace View Schedule and Modify Schedule: View Backup Schedule Modify Backup Schedule The following permissions were updated for Schedule groups to allow you to assign one or more domains to a report schedule: View Device Report Schedule Modify Device Report Schedule The following permissions were added to control who can view or change Device Control commands: View Device Command Modify Device Command The Command Device permission is enforced only when controlling or sending a command to a device. The following permissions replace View Rules, Modify Rules, and Apply Rules: View Device Policy Modify Device Policy Apply Device Policy Renamed the Old Report permissions to Legacy Permissions to clarify the permissions interact with the Legacy Reports that reside in the old user interface. You can now filter Device Control > Schedule so command schedules are filtered based on the command's device type. Updated Report Schedules (Reports > Schedules) and Reports (Report > Reports) to be filtered by domain. Thank you, Release ManagementConvert Customization to PowerFlow Jinja Template
1 MIN READ Sometimes when syncing devices from SL1 into ServiceNow as a Configuration Items there can be a mismatch. ServiceNow may list the name as Fully Qualified Domain Name and SL1 will use short name. This setting can be updated in SL1, but in some cases the SL1 team would rather see short name than FQDN. This can be setup on a per SL1 Device Class basis. PowerFlow Using the following Jinja2 “if statement” the device name in SL1 can be converted to use “Device Hostname,” in SL1 instead for Microsoft SQL Server Databases. This excerpt of code would go under attribute mappings for name on the ScienceLogic side mapping to name on the ServiceNow side: {%- set output = [] -%} {%- if (device.device_class|trim) in ['Microsoft | SQL Server Database'] } {%- set output = device.hostname -%} {%- else -%} {%- set output = device.name -%} {%- endif -%} {{ output }} Example:Updates to EM7_RESULT handling?
Hi, During SL1 version update we have noticed that EM7_RESULT variable is going to be re-formatted to different type during snippet execution. For example if we populate the variable with list and with tuple elements, the variable is getting re-formatted to nested list. For example EM7_RESULT = [("test1", "test2")], is re-formatted after snippet execution to [["test1", test2"]] format. Is this change documented somewhere and in which version this update was implemented?AP2 release Halwa.01
We're happy to announce that AP2 Halwa.01 release (8.16.1.41) is now available! This release fixed critical bugs in Halwa release (8.16.1.14). If you have deployed Halwa, or 12.3.0, it's recommended that you deploy Halwa.01 to take these fixes. Before you install or upgrade to AP2 Halwa.01, ensure you are running one of the following SL1 versions: 12.2.3 12.3.0 - 12.3.3 You do not need to download or install AP2 Halwa.01 if you will deploy SL1 version 12.3.3 ( to be released in April 2025), as it is included by default. You can download Halwa.01 and associated release notes following this link: https://support.sciencelogic.com/s/release-file/aBtVL0000000rp70AA/halwa01
Check out our NEW Pro Services Blog for great SL1 Tips and Tricks!
