1. Resonate RFID Reader Management 2.1 User Guide
  2. Alerting Targets
  3. Sending Alerts to Zebra's OpsRamp instance
  • Resonate RFID Reader Management 2.1 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. You should perform the steps as root or a user with sudo privileges. If you do not have the required permissions, contact your system administrator.
To proceed, you need the webhook URL for Zebra's OpsRamp instance, provided by your Zebra representative. Replace the placeholders in the URL with your tenant-id and token, if they are not already included.
  1. Log in to the
    Resonate
     server1 via SSH.
  2. Switch to the
    trif-user
     account:
    sudo su - trif-user
  3. Verify that you are in the
    trif-user
    's home directory (
    /opt/zebra/trifecta
    ):
    pwd
  4. Change the customer label in alerts to your customer name.
    Skip this step if you specified your customer name for Zebra's OpsRamp alert monitoring server during
    Resonate
     installation with the
    --customer-label-value
     or
    -l
     option.
    1. Create a variable for your customer name:
      CUSTOMER="Your Customer Name"
      Replace
      Your Customer Name
       with your customer name (for example,
      CUSTOMER="CustomerXYZ"
      ).
    2. Run the following command to update the
      trifecta.prometheusrules.yaml
       file with your customer name:
      sed -i "s@customer:.*@customer: \"${CUSTOMER}\"@" manifests/base/trifecta.prometheusrules.yaml
      Copy and paste this line exactly how it is (but on one line). All spaces are required.
    3. Run the following command to apply the changes:
      kubectl apply -f manifests/base/trifecta.prometheusrules.yaml --server-side
  5. Verify the customer label.
    1. Run the following command: 
      kubectl get configmap prometheus-k8s-rulefiles-0 -n monitoring -o yaml | grep -B 3 customer:
    2. Verify that
      monitoring-trifecta-rules
       has a "customer: " label.
      In the following example, you can see that the customer label is now
      CustomerXYZ
      :
      monitoring-trifecta-rules-528dd340-635b-42dc-ba0b-c074adb40f24.yaml: |
  groups:
  - labels:
      customer: CustomerXYZ
  6. Add Zebra's OpsRamp instance as an alerting target.
    1. Run the following command to add Zebra's OpsRamp instance as an alerting target so that alerts are sent to it.
      ./add-alerting-target.sh --type webhook --webhook-url <URL> --name opsramp
      Replace
      <URL>
       with the webhook URL that you received from your Zebra representative. When setting up multiple alerts to OpsRamp, pass different names to
      --name
       for each different alert configuration.
      The output should look similar to the following.
      ./add-alerting-target.sh --type webhook --webhook-url https://zebra.api.opsramp.com/integrations/alertsWebhook/<tenant-id>/alerts?vtoken=<token> --name opsramp
   {com.zebra.alt.logging}PROMPTConfiguring Alerting Target With The Following Options:
   {com.zebra.alt.logging}PROMPT  Type: webhook
   {com.zebra.alt.logging}PROMPT  Name: opsramp
   {com.zebra.alt.logging}PROMPT  CA Certificate: <default TLS certificates>
   {com.zebra.alt.logging}PROMPT  Alert Group: both
   {com.zebra.alt.logging}PROMPT  Group By: ...
   {com.zebra.alt.logging}PROMPT  Group Wait: 30s
   {com.zebra.alt.logging}PROMPT  Group Interval: 5m
   {com.zebra.alt.logging}PROMPT  Repeat Interval: 4h
   {com.zebra.alt.logging}PROMPT  Continue: true
   {com.zebra.alt.logging}PROMPT  Webhook URL: https://zebra.api.opsramp.com/integrations/alertsWebhook/<tenant-id>/alerts?vtoken=<token>
   {com.zebra.alt.logging}PROMPT  Webhook Max Alerts: 0
   {com.zebra.alt.logging}PROMPT  Webhook Authorization Type: <not set>
   {com.zebra.alt.logging}PROMPT  Matchers: <none>
   [2025-10-23T15:39:41+00:00] INFO    Provisioning Alerting Target
   [2025-10-23T15:39:42+00:00] INFO    Applied AlertManagerConfig: opsramp
   Successfully Configured Alerting Target: opsramp

   The AlertManager configuration has been updated to send alerts to your specified target.
   Please ensure your webhook endpoint at https://zebra.api.opsramp.com/integrations/alertsWebhook/<tenant-id>/alerts?vtoken=<token> is properly configured to receive alerts.
    2. Verify the alert manager config is in the monitoring namespace:
      kubectl get alertmanagerconfig -n monitoring
      The output should look similar to the following:
      NAME                    AGE 
alerting-sidecar-target 58m
opsramp                 13m
Resonate
 is now configured to send alerts to Zebra's OpsRamp instance.
1 Note: These steps are only applicable to
Resonate RFID Reader Management
 version 2.1 and greater.