Snippet Framework PowerPacks and Distribution

This section covers how Snippet Framework content is packaged and shared. It explains what a PowerPack can include, how the argument-driven design allows a small number of reusable snippets to power many different Dynamic Applications through configuration alone, and what happens in Skylar One when an administrator installs a toolkit PowerPack.

PowerPacks and Distribution Overview

Snippets, toolkits, Dynamic Applications, and related content are distributed through PowerPacks. A PowerPack might include any combination of:

• Snippet bodies and toolkit libraries
• Dynamic Applications that reference those snippets
• A standardized Execution Environment
• Bundled directly in Skylar One releases starting with version 12.6.0, meaning it does not require a separate PowerPack installation in those environments

How Distribution Works

PowerPacks allow Snippet Framework-based monitoring logic to be packaged, versioned, and deployed consistently across Skylar One systems. Because all collection behavior is defined through snippet arguments rather than custom code, the same snippet bodies can serve many different use cases simply by varying the YAML configuration in each Dynamic Application.

This means a single PowerPack can contain a small number of reusable snippets that support many different Dynamic Applications, all configured through their respective snippet arguments.

Installing PowerPacks

Administrators manage PowerPacks through standard Skylar One import and installation workflows. Installing a PowerPack that contains toolkit content typically:

• Installs the ScienceLogic Library package into Skylar One.
• Makes the corresponding Execution Environment available for selection in Dynamic Applications.
• Imports any included Dynamic Applications in an unaligned state, ready for device alignment.

For step-by-step PowerPack installation instructions, see the Managing PowerPacks manual.