Skip to content

Learn · Guides

Install a rule pack

Take a published set of warning labels and pin it to a version.

Checked against the product on · written for everyone

A rule pack is a published set of warning labels with examples behind each one. Installing a pack gives your rules more labels to watch for.

console.dmzagent.com/labels

Respond

Library

1All categoriesFreePaidPublish a pack
2
Industrial safety basicsFree

41 labels · reviewed · 2.3.0

Support conductFree

18 labels · reviewed · 1.1.2

Financial promotionsPaid

96 labels · reviewed · 3.0.1

3A pack is pinned to the version you install. A new version never changes your rules on its own.
Figure. The library. Each card is a published pack with its label count and version. The rule pack library: packs with their author, version, label count, price and install button.

  1. Open Labels and select Browse the library.1

  2. Pick a pack and read its label count and version.2

  3. Read the pinning line.3

    An installed pack stays on the version you installed until you move it.

Read the pack before you install it

console.dmzagent.com/labels

Respond

Industrial safety basics 2.3.0

1LabelsTestsVersionsManifest
2
Warning labelGroupExamples
temperature-excursionThermal24
pressure-excursionMechanical19
repeat-excursionThermal11
3View manifest hashInstall
Figure. One pack. Labels, test results, version history, and the manifest hash. One rule pack: its labels, its test results, its version history, and an install button.

  1. Open the Labels tab and read what the pack will add.1

  2. Open Tests and read the results.2

    A published pack carries the test suite it passed and the examples it was measured against.

  3. Select Install.3

    The labels appear in your rule builder within a few seconds.

Note. Every published version has a manifest hash. Quoting that hash back to the platform returns the exact manifest that was installed, which is how an auditor confirms what a rule was reading on a given day.

From code

curl 'https://api.dmzagent.com/v1/library/canons?limit=25' \
  -H 'Authorization: Bearer YOUR_API_KEY'
curl -X POST 'https://api.dmzagent.com/v1/library/canons/CANON_ID/install' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"version": "2.3.0"}'
curl 'https://api.dmzagent.com/v1/library/manifests/MANIFEST_HASH' \
  -H 'Authorization: Bearer YOUR_API_KEY'

The audit replay door: the exact manifest that hash names.

Moving to a new version

  1. Open the pack in Labels and select Versions.

  2. Read the change summary for the version you are moving to.

    It lists labels added, labels retired, and examples changed.

  3. Select Test against past events.

    The test reports which of your rules would fire differently under the new version.

  4. Select Pin to this version.

    The move is written to the logbook with your name on it.

Ask the assistant to wire this in →Open your organization