1. Resonate RFID Reader Management User Guide
  2. Alerting Targets
  3. Sending Alerts to Zebra's OpsRamp instance
  • Resonate RFID Reader Management 2.0 User Guide
Sending Alerts to Zebra's OpsRamp instance

Sending Alerts to Zebra's OpsRamp instance

If you are using Zebra's monitoring service, use the steps below to configure
Resonate
 to send alerts to Zebra's OpsRamp instance.
Before configuring, you must:
  • Locate the file
    trifecta.prometheusrules.yaml
     packaged with the
    add-alerting-target.sh
     shell script1.
  • Switch to
    trif-user
    with the command: 
    sudo su - trif-user
  1. Copy the
    add-alerting-target.sh
    , and
    trifecta.prometheusrules.yaml
     files over to the Resonate server.
    With
    scp
    , that would be: 
    scp ./add-alerting-target.sh ./trifecta.prometheusrules.yaml
  2. Edit the file
    trifecta.prometheusrules.yaml
    so that the customer label (defined on each alert in the file) is the correct value:
    • You could do this with a
      sed
      : 
       sed -i 's@customer: .*$@customer: "Your Customer ID"@'
    • Alternatively, you can do this manually with a text editor of your choice.
  3. Install the change with the command:
    kubectl apply -f <path/to/your/trifecta.prometheusrules.yaml>
  4. Add OpsRamp as an alerting target with the command:
    ./add-alerting-target.sh --type webhook --webhook-url <URL> --name opsramp
    Your Zebra representative should provide you with the webhook URL to pass to this command. When setting up multiple alerts to OpsRamp, pass different names to
    --name
     for each different alert configuration.
Resonate is now configured to send alerts to OpsRamp.
1 In Resonate 2.0, this is located in
opsramp.zip
, which is distributed alongside the
resonate-<VERSION>.tar.gz
 installation file. Unzip this file and copy it to the home directory of trif-user.