Subscriptions

IT-Conductor Notification is based on the Subscription model, where users subscribe to service elements to receive notifications on status changes and alerts related to the elements.

The Subscriptions are created for individual Users, Groups, Roles, or Organizational Units.

Subscriptions can be configured for various monitored service elements in IT-Conductor. This allows notifications to be routed to the appropriate teams when alerts or status changes occur. You can create subscriptions for service elements such as:

• SID alerts

• DB alerts

• Queues (tRFC / qRFC)

• HANA alerts

• SAP jobs

• SAP objects

• Gateway alerts

• Table growth alerts

• Errors

Practical examples of how subscriptions can be used with these monitoring elements are provided in the Use Case scenario below.

How to Subscribe to Email Notifications

1. Visit service.itconductor.com and enter your login credentials.

2. Navigate to the IT-Conductor Service Grid and choose the service element you want to subscribe to for notifications.

3. Click on the service element icon to display the object menu and choose Subscriptions.

Figure 1: IT-Conductor Service Grid View

1. Click the Create New Subscription icon to subscribe for notifications.

Figure 2: Create New Subscription icon

1. Supply the necessary information to complete the subscription. Click the Finish icon to complete the process.

Figure 3a: Create Service Element Subscription

a. Name - refers to an identifiable name for the subscription

b. Description - refers to a brief explanation of the subscription

c. Subscriber type - Select User/Group/Role/Organization to choose the subscription targets from a list of IT-Conductor users or groups. Select External Integration if you want to route the subscription through a third-party integration provider.

d. Subscriber - Select the IT-Conductor user, distribution list, or notification target that will be the receiver of the alert. If you selected External integration in the previous step, select the integration provider. IT-Conductor supports integrations with Derdack, ilert, PagerDuty, Jira, Microsoft Teams, and Slack.

Figure 3b: Create Service Element Subscription - Derdack Subscription

Figure 3c: Create Service Element Subscription - MS Teams Subscription

Figure 3d: Create Service Element Subscription - Pager Duty Subscription

e. Recursive - Check Recursive if you would like to receive a notification on all children of this subscription

f. Minimum severity - Defines the minimum severity level at which the subscription triggers a notification. By default, this is set to Warning.

g. Alert class - Select the type of alert related to the service element for which you want to create the subscription.

Figure 3e: Create Service Element Subscription - Choose an Alert Class

h. Alert criteria - refers to the specific criteria for selective alert targeting. You can add one or several criteria to make your alert more specific. To add more criteria, click on the Add New Row button, then fill in the following fields:

1. Attribute - refers to the exact criteria that the alert will target. You can choose one of the available criteria from the drop-down menu.

2. Oper - refers to the operator validation (=, !=, >, <, in, regex, NULL, etc).

3. Value - refers to the exact value that the alert will target. This is an open field where you can specify file names or file formats to further specify your alert’s target.

Figure 3f: Create Service Element Subscription - Add Alert Criteria

1. Click on Finish

Note: The more criteria there are, the more specific the override is and the higher the precedence.

1. The Subscription details will be available in the list. You should start receiving notifications at your email address within 15 minutes (for performance reasons, the subscriptions are cached and refreshed every ~15 minutes).

Once the subscription is configured, notification activities can be incorporated into a workflow, allowing alerts to be sent at specific stages. Subscribers can be assigned as recipients to these activities, so they receive notifications as each step of the workflow is executed. In this example, subscribers are notified upon completion of each stage of the system copy workflow. If an issue arises that requires immediate attention, they are informed early and can take action promptly.

Figure 4: Notifications as Part of the Workflow

Check Active Subscriptions

1. In the IT-Conductor main menu, navigate to Management → Notification → Subscriptions.

Figure 5: IT-Conductor Management Menu

1. Select any of the subscriptions on the list. From here, you’ll be able to do any of the following activities:

   1. Edit subscribers

   2. Edit alert criteria

   3. Maintenance mode

   4. Check notifications sent

   5. Duplicate/Create new subscription

Figure 6: List of Existing Subscriptions

Edit Subscribers

1. On the list of subscriptions, click on the icon → Edit subscribers

Figure 7a: Edit Subscribers

1. Alternatively, the option can be found inside the subscription page.

Figure 7b: Edit Subscribers

1. Add or remove the desired users, lists, or groups to the subscription.

2. Click on the Save button to finish.

Figure 7c: Edit Subscribers

Edit alert criteria

1. On the subscription page, scroll down to the Alert Criteria

2. Click on the icon to add a new criteria, or click on the existing one and click on the to edit it

Figure 8: Edit Alert Criteria

Maintenance mode

1. Pause your alerts by placing them in maintenance mode

2. Click on the icon

Figure 9a: Set Subscription on Maintenance Mode

1. Click on Yes

Figure 9b: Set Subscription on Maintenance Mode

1. Turn off maintenance mode by clicking the icon once again.

Check subscription notifications

1. Review the messages sent by this subscription by clicking on the icon

Figure 10: Check Subscription Notifications

1. Review details such as the start time, completion time, recipient, and delivery status of the subscription.

   1. Click on the Restart activity icon to manually initiate the subscription activity

   2. Click on the Source alert icon to view the alert related to the subscription

Figure 11: Notification Subscriptions

Duplicate/Create new subscription

1. Create a new subscription from an existing one by clicking on the → Copy

Figure 12: Copy an Existing Subscription

1. Make all the necessary adjustments to the name, target, or alert criteria as shown in the previous section, and click the to finish

Figure 13: Modify Subscription

Use Case: Notifying the SAP Basis Team of Queue Alerts

In this scenario, we demonstrate how to tailor a subscription so that a specific team is notified only when alerts occur for queues with a particular name. This adds a filtering layer, allowing general queue alerts to be sent to everyone while routing alerts for specific queues to the appropriate team.

Pre-requisites

1. Create an alert or override for the queue (see Alerts | IT-Conductor Documentation for more details). This configuration acts as the first filtering layer that triggers the notification. In this example, we create an alert that is triggered when the state of an inbound queue becomes stuck.

   1. Target object type is set to SAPRFCQueue

   2. Object criteria is set to SAPRFCQueue.QSTATE_NAME in NOSEND, SYSFAIL. This will send an alert whenever a queue is in either of those states.

Figure 14: Set Target Object Type & Object Criteria in Override

1. Create a distribution list for the SAP Basis team (see Distribution Lists | IT-Conductor Documentation for more details). The users on this list will be on the receiving end of the alert

Figure 15: Create a Distribution List

Now that we have the alert and the distribution list, we’ll create the subscription.

1. On the service grid, navigate to the desired SID → tRFC & qRFC

2. Click on → Subscriptions

Figure 16: Check First Entry Queues Subscriptions

1. This will show you all the existing subscriptions for inbound queue alerts. Click on Subscriptions to create a new one, or the Alerts icon to create a new subscription from an existing one.

   1. In Subscriber, select the SAP Basis distribution list that we created

   2. In Alert class, open the Object Related Alert menu → Abstract SAP Alert → SAP qRFC Alert

   3. Set your alert criteria like this

      1. Attribute -> SAPQRfcAlert.QNAME

      2. Oper → regex

      3. Value → ^(TEST). The ^ symbol indicates that the queue name must begin with TEST. As a result, the subscription will only apply to queues such as: TEST_QUEUE, TEST_INBOUND, TEST_INT_PROCESS )

   4. Click on Finish

Figure 17: Set Subscriter, Alert Class & Alert Criteria in Subscription

This scenario is only one example. You can adapt the alert criteria to match different queue naming patterns depending on your requirements.

For example:

Goal	Example Filter
Match queues that start with TEST	regex ^TEST
Match queues that contain TEST anywhere in the name	regex TEST
Exclude queues that contain TEST	!regex TEST
Match queues that start with TEST or DEV	!regex ^(?:TEST)

Note: For more information on the variables and operators used in IT-Conductor, visit our Threshold Overrides Variables

Related features

• Threshold overrides

• Alerts

• Distribution lists

• Notification targets

• Integration providers

• SMTP Notification Providers