vLLM Monitoring PowerPack Release Notes Version 100

Version 100 of the "vLLM Monitoring" PowerPack is the initial version of the PowerPack. With this PowerPack, you can collect and analyze metrics from vector Language Learning Model (vLLM ) deployments.

Before You Install or Upgrade

Ensure that you are running version 12.1.2 or later of SL1 before installing the "vLLM MonitoringPowerPack.

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

Installation and Upgrade Process

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.

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.

Features

This release includes the following features:

  • The following Dynamic Applications that discover and collect data from a vLLM deployment:
    • vLLM Metrics Config
    • vLLM Metrics Performance
  • A device dashboard to display information about vLLM deployments

Known Issues

The following known issues affect version 100 of the "vLLM Monitoring" PowerPack:

  • You may see a "No Data Found" message or a blank dashboard when viewing the vLLM Dashboard. If you do, clearing the SL1 system cache (Misc > Clear SL1 Cache or Toolbox button ()> Clear SL1 Cache in the classic SL1 user interface) should resolve the issue.