| copyright |
|
||
|---|---|---|---|
| lastupdated | 2025-01-29 | ||
| keywords | |||
| subcollection | monitoring | ||
| content-type | conref |
{{site.data.keyword.attribute-definition-list}}
{: #conref-monitoring}
{: #en-prereqs}
Your {{site.data.keyword.mon_full_notm}} instances can send events to {{site.data.keyword.en_full_notm}} instances in the same account and in other accounts. {{site.data.keyword.en_full_notm}} is available in a limited number of regions. {: important}
For this tutorial, make sure you have an {{site.data.keyword.mon_full_notm}} instance configured and collecting logs in a region where {{site.data.keyword.en_full_notm}} is supported such as us-south.
{: #en-login} {: step}
Log in to your {{site.data.keyword.cloud_notm}} account.
-
Click {{site.data.keyword.cloud_notm}} dashboard{: external} to launch the {{site.data.keyword.cloud_notm}} dashboard.
-
Log in with your user ID and password. The {{site.data.keyword.cloud_notm}} Dashboard opens.
{: #en-create-instance} {: step}
First, create an {{site.data.keyword.en_full_notm}} service instance by doing the following:
-
Click Catalog.
-
In Search the catalog enter Event Notifications.
-
In the Create tab enter:
- For Select a location select
Dallas (us-south). - For Select a pricing plan select
Lite. - For Service name enter a name of your choice. For example:
my_event_notifications. - For Select a resource group enter your resource group.
- For Select a location select
-
Read and agree to the license agreements.
-
Click Create
Your {{site.data.keyword.en_full_notm}} instance is created and is displayed.
{: #en-permissions} {: step}
To grant an instance of the {{site.data.keyword.mon_full_notm}} service access to an instance of the {{site.data.keyword.en_full_notm}} service, you must define an authorization where the source service is set to {{site.data.keyword.mon_full_notm}} and Resources based on selected attributes; the target service is set to {{site.data.keyword.en_full_notm}} and Resources based on selected attributes; and the service access includes both Reader and Event Source Manager access.
- Click Manage > Access (IAM).
- Click Authorizations.
- Click Create.
- For Source service select IBM Cloud Monitoring.
- For How do you want to scope the access? select All resources.
- For Target service select Event Notifications.
- For How do you want to scope the access? select All resources.
- For Service access make sure Reader and Event Source Manager are selected.
- Click Authorize.
For more information on how to define authorizations, see Using authorizations to grant access between services.
{: #en-notification} {: step}
To create a notification source in {{site.data.keyword.en_full_notm}} you will make the configuration change in {{site.data.keyword.mon_full_notm}}. When you create the notification channel in {{site.data.keyword.mon_full_notm}} it will be available automatically in {{site.data.keyword.en_full_notm}}.
-
In the navigation menu, select Observability.
-
Select Monitoring.
The list of instances that are available on {{site.data.keyword.cloud_notm}} is displayed.
-
Select an instance in the
us-southregion. Then, click Open dashboard.The Web UI opens.
-
In the navigation click the circle icon with your initials.
-
Click Settings.
-
Click Notification Channels.
-
Click Add Notification Channel.
-
Select IBM Event Notifications.
-
For Event Notifications Instance select the {{site.data.keyword.en_full_notm}} you created.
-
For Channel Name give your channge a unique name. For example,
my_event_notification_channel. -
For this tutorial leave all options enabled and the Shared With team as the default value.
{: caption="New IBM Event Notification Channel" caption-side="bottom"} -
Click Save.
-
Open Developer tools.
-
Open the {{site.data.keyword.en_full_notm}} instance you created. For example,
my_event_notifications. -
Click Sources.
When you configure the channel in {{site.data.keyword.mon_short}}, a source, with the same name as your {{site.data.keyword.mon_short}} instance name, is automatically added to your {{site.data.keyword.en_full_notm}} Sources list.
{: #en-topic} {: step}
Next you will define an {{site.data.keyword.en_full_notm}} topic that will receive the notification from {{site.data.keyword.mon_full_notm}}.
-
Click Topics.
-
Click Create. The Topic details panel opens.
-
In the Topic details enter the following:
- Enter the Name for your topic. For example,
MyMonitoringTopic. - For Source select the {{site.data.keyword.en_full_notm}} source, which is named the same as your {{site.data.keyword.mon_full_notm}} instance.
- Select an Event Type. For this tutorial select Alert.
- Select an Event subtype. For this tutorial select Metric.
- Select a Severity. For this tutorial select Info Severity.
- Enter the Name for your topic. For example,
-
Click Add a condition.
If you do not click Add a condition before you click Create, the topic will be created with no conditions associated with it. {: note}
-
Click Create. Your topic will be displayed in the Topics list.
{: #en-mon-notification} {: step}
Now, create an {{site.data.keyword.mon_full_notm}} alert that will trigger the {{site.data.keyword.en_full_notm}} notification.
-
In the navigation menu, select Observability.
-
Select Monitoring.
The list of instances that are available on {{site.data.keyword.cloud_notm}} is displayed.
-
Select the {{site.data.keyword.mon_full_notm}} instance that you configured to send notifications to {{site.data.keyword.en_full_notm}}.. Click Open Dashboard.
-
Click Alerts.
-
Click Add Alert.
-
Create an alert that meets the criteria of the {{site.data.keyword.en_full_notm}} topic that you created.
-
Click Metric.
-
For the new alert specify the following:
- For Name specify
MyEventNotificationAlert. - For Severity specify
Info. - Define a metric for you system that you know will trigger an alert.
- Enable the
myEventNotificationChannelfor the alert.
- For Name specify
-
Click Create.
-

