Monitor Event Notifications service metrics with IBM Cloud Monitoring

Use IBM Cloud Monitoring to gain operational visibility into the performance and health of your applications, services, and platforms. It offers administrators, DevOps teams, and developers full stack telemetry with advanced features to monitor and troubleshoot, define alerts, and design custom dashboards.

Set up your IBM Cloud Monitoring service instance

To get started, you need to provision IBM Cloud Monitoring instance on your IBM® account. See Provisioning an instance for more details.

Currently, IBM Cloud Monitoring integration is available for Event Notifications service deployments in the following regions:

Table 1. Deployment regions
Deployment region	Monitoring region
Dallas	Dallas
London	London
Sydney	Sydney
Frankfurt	Frankfurt
Madrid	Madrid

Before you can start with Event Notifications monitoring metrics, you must first opt in and enable platform metrics

You can configure only one instance of the IBM Cloud Monitoring service per region to collect platform metrics.

To configure the IBM Cloud Monitoring instance, you must turn on the platform metrics configuration setting.
If a monitoring instance in a region is already enabled to collect platform metrics, metrics from enabled-monitoring services are collected automatically and available for monitoring through this instance. For more information about enabled-monitoring services, see IBM Cloud® services.

To monitor platform metrics, check that the IBM Cloud Monitoring instance is provisioned in the same region where the IBM Cloud instance is provisioned.

Access your IBM Cloud Monitoring metrics

Start the IBM Cloud Monitoring web UI from the Observability page.
Click DASHBOARDS.
In the Default Dashboards section, expand IBM.
Choose the Event Notifications dashboard from the list.

Access your deployment's monitoring dashboard from IBM Cloud Monitoring, it's in the sidebar, under IBM. Next, change the scope or make a copy of the default dashboard to monitor an Event Notifications service instance.

Metrics available by Service Plan

Table 2. Metrics available by service plan
Metric Name
ibm_eventnotifications_total_ingested_notifications
ibm_eventnotifications_total
ibm_eventnotifications_failed
ibm_eventnotifications_devices

ibm_eventnotifications_total_ingested_notifications

Total number of notifications that are ingested. Ingested notifications are events from a source that has at least one condition that is defined on them for filtering.

Table 3. Ingestion metadata
Metadata	Description
`Metric Name`	`ibm_eventnotifications_total_ingested_notifications`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`ibm_scope`, `ibm_ctype`, `ibm_location`, `ibm_service_name`, `ibm_service_instance`, `ibm_eventnotifications_source`

ibm_eventnotifications_total

Total number of notifications for a particular type includes successful and failed notifications.

Table 4. Notifications metadata
Metadata	Description
`Metric Name`	`ibm_eventnotifications_total`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`ibm_scope`, `ibm_ctype`, `ibm_location`, `ibm_service_name`, `ibm_service_instance`, `ibm_eventnotifications_source`, `ibm_eventnotifications_destination`, `ibm_eventnotifications_source`, `ibm_eventnotifications_type`

ibm_eventnotifications_failed

Total number of failed notifications of a particular type.

Table 5. Failed notifications metadata
Metadata	Description
`Metric Name`	`ibm_eventnotifications_failed`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`ibm_scope`, `ibm_ctype`, `ibm_location`, `ibm_service_name`, `ibm_service_instance`, `ibm_eventnotifications_destination`, `ibm_eventnotifications_source`, `ibm_eventnotifications_type`,

ibm_eventnotifications_devices

Total number of push notification devices registered.

Table 6. Total devices registered
Metadata	Description
`Metric Name`	`ibm_eventnotifications_devices`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`ibm_scope`, `ibm_ctype`, `ibm_location`, `ibm_service_name`, `ibm_service_instance`, `ibm_eventnotifications_destination`, `ibm_eventnotifications_device_type`,

Attributes for segmentation

Global Attributes

The following attributes are available for segmenting all of the metrics previously listed.

Table 7. Segmentation attributes
Attribute	Attribute Name	Attribute Description
`Cloud Type`	`ibm_ctype`	The cloud type is a value of `public`, `dedicated`, or `local`.
`Location`	`ibm_location`	The location of the monitored resource, which can be a region, data center, or global.
`Scope`	`ibm_scope`	The scope is the account, organization, or space GUID associated with this metric.
`Service instance`	`ibm_service_instance`	The service instance segment identifies the instance that the metric is associated with.

More attributes

The following attributes are available for segmenting one or more attributes as described in the previous tables. See the individual metrics for segmentation options.

Table 8. More attributes
Attribute	Attribute Name	Attribute Description
`Name of the destination`	`ibm_eventnotifications_destination`	A destination name with its associated ID.
`Name of the source`	`ibm_eventnotifications_source`	A source name with its associated ID.
`Type of event notification`	`ibm_eventnotifications_type`	The type of supported destination types. (email, SMS, or webhook)
`Type of push notification device`	`ibm_eventnotifications_device_type`	The type of supported push notification device.(push_android, push_ios)