vania-janet/multiturn-rag-retrieval-data huggingface dataset:
When you configure index rate alerts, you can gain insight into which applications, sources, or tags produce data spikes, as well as any recently added sources. The alert message that is sent includes the following information:



* The top 20 sources and apps that have had the largest index rate growth in the past 2 hours.
* The list of the 20 newest sources added.
* A link to download generated lists of all applications and sources. You can view the “Manage Usage” Dashboard to download these lists at any time.



Complete the following steps:



 Step 1. Configure 1 or more rules 

Choose 1 or more of the following options to activate the index rate alert feature:



* Max lines/s: Set an index rate threshold by configuring the max lines alert field so that you can get an alert when the value of lines per second is exceeded.
* Max z-score: Set a threshold value by configuring the max z-score field so that you can get an alert when the hourly index rate is significantly higher than the monthly mean.







 Step 2. Configure the notification channels 

Choose 1 or more notification channels to receive an alert when the threshold of a rule is exceeded:



* Configure the email notification channel by selecting Add email and entering 1 or more emails.
* Configure the Slack notification channel by selecting Add slack and configuring the channel details.
* Configure the PagerDuty notification channel by selecting Add PagerDuty and entering the credentials.
* Configure the Webhook notification channel by selecting Add Webhook and entering the credentials.







 Step 3. Configure the notification frequency 

Choose the notification frequency. Valid options are:



* Hourly notifications
* Daily notifications at midnight UTC



Notifications are sent until the index rate reports a value that is below the thresholds that you have configured.

Individual recipients may mute alert emails.

You can also configure a custom schedule to set the days and hours that you want alerts to be send if the thresholds are exceeded.







 Configuring index rate alerts using the API
Sample queries to notify on account configuration changes 



 Notify when services are created, modified, and deleted 

The following table outlines queries that you can use to alert on configuraton changes that report when services are created, modified, and deleted:



Table 1. Query samples when services are created, modified, and deleted

 Notify on Query UI Source API hosts 

 Create a service instance instance.create N/A N/A 
 Create a service instance for service type instance.create You can choose a specific service in the source filter section of the UI.<br><br>For example, to notify when a Key Protect service instance is created, choose kms as the source. You can specify the service in the hosts patameter.<br><br>For example, to notify when a Key Protect service instance is created, add "hosts": "kms" 
 Delete a service instance instance.delete N/A N/A 
 Delete a service instance for service type instance.delete You can choose a specific service in the source filter section of the UI.<br><br>For example, to notify when a Key Protect service instance is deleted, choose kms as the source. You can specify the service in the hosts patameter.<br><br>For example, to notify when a Key Protect service instance is deleted, add "hosts": "kms" 
 Modify a service instance instance.update N/A N/A 
 Modify a service instance for service type instance.update You can choose a specific service in the source filter section of the UI.<br><br>For example, to notify when a Key Protect service instance is changed, choose kms as the source. You can specify the service in the hosts patameter.<br><br>For example, to notify when a Key Protect service instance is changed, add "hosts": "kms" 
 Create, delete or modify any service instance instance.create OR instance.delete OR instance.update N/A N/A 







 Notify when account settings are modified 

The following table outlines queries that you can use to alert on configuraton changes that report when account settings are modified:



Table 2. Query samples when account settings are modified
Generating alerts on IBM Cloud account configuration changes 

In IBM Cloud® Activity Tracker, you can create alerts to notify on configuration changes on the IBM Cloud account. For example, you can generate notifications that report when services are created, modified, and deleted. These alerts can be limited to specific resources, or can apply to any services offered within the IBM Cloud.



 Configuring alerts using the console 

The following will generate an alert when a service instance is created, deleted, or updated. These events are recorded in the Frankfurt region, regardless of the region of the service instance.

If you already have an instance in the Frankfurt region, you should use that existing instance.



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).

After you log in with your user ID and password, the IBM Cloud UI opens.
2. [Launch the Activity Tracker instance UI](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-launch). The Everything view opens.
3. [Define the rule that determines the scope of the data that you want to monitor](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-viewsviews_step2).

In the search bar, enter a query such as instance.create OR instance.delete OR instance.update. The view will now only display events when an instance is created, deleted, or updated.

Check that you can see in the view events that report creation, deletion or change of a service instance.

Filtering on different configuration changes is also possible. You can filter events that are related to a specific service type. For example, you can filter on all IBM Key Protect instances by specifying kms.instance.

To filter when keys are created or deleted in the IBM Key Protect service, you can specify kms.secrets.create OR kms.secrets.delete.

See the events that are generated by the services to determine what configuration changes you want to be alerted.
ibmcloud cis alert-policy pool-toggle-alert-update POLICY_ID --name NAME (--emails EMAILS | --webhooks WEBHOOKS) --enabled (true | false) --pools POOLS --trigger-condition (enabled | disabled | either) --include-future-pools (true | false)] --description DESCRIPTION] -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-opt-update-pool-toggle-alert" "> --> Command options POLICY_ID: The ID of alert policy. Required.--name: The name of the alert policy.--description: The description for the alert policy.--emails: The email addresses for dispatching an alert notification. For example: --emails test1@cn.ibm.com,test2@cn.ibm.com--webhooks: The webhook ID that for dispatching an alert notification. For example: --webhook webhookID1,webhookID2--enabled: Whether or not the alert policy is enabled.--pools: The IDs of origin pool, if set to all, the all pool IDs will be used.--trigger-condition: The condition of pool toggle status.--include-future-pools: Whether or not include the future pools.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-opt-update-pool-toggle-alert" "> --><-- <section "id="section-update-pool-toggle-alert-examples" "> --> Examples Update a pool toggle alert policy for instance cis-demo.
* For more information on how to configure an alert, see [Creating alerts through the UI](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-create_alert_ui).
* For more information on how to create alerts programmatically, see [Managing views and alerts programmatically](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-config_api).







 Deleting alerts 

You can delete alerts graphically through the Log Analysis UI, or programmatically.



* For more information on how to delete an alert, see [Removing alerts through the UI](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-remove_alert_ui).
* For more information on how to delete alerts programmatically, see [Managing views and alerts programmatically](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-config_apiconfig-api-create-view-alert).







 Managing presets (alert templates) 

To reuse an alert configuration, a service administrator can configure an alert preset (alert template).



* For more information on how to create a preset, see [Create a preset](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-preset_uipreset_ui_create).
* For more information on how to delete a preset, see [Delete a preset](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-preset_uipreset_ui_delete).







 Muting alert notifications 

By default, the feature that controls the ability of a user to mute notifications is enabled when you configure an alert on a custom view. The Mutable feature applies to email notifications only.

When the mutable feature is enabled on an alert, a user can pause notifications for a period of time.
Now that you have configured monitoring of your peer, CA, and ordering nodes, the final important step is to configure alerts in IBM Cloud Monitoring so that a notification is triggered when a specified condition is met. You can trigger an alert notification via email, slack, PagerDuty, Webhooks, OpsGenie, and VictorOps channels. First configure the notification channel and then define the alert triggers.



1. Configure your preferred notification channel by clicking on your user icon followed by Settings.

Zoom

![IBM Cloud Monitoring settings panel](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/configure-alert-channel.png)

Figure 2. IBM Cloud Monitoring settings panel

When you subsequently click Notification Channels > Add Notification Channel you are able to select how you want to be notified when an alert is triggered.

Zoom

![IBM Cloud Monitoring notifications](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/configure-sysdig-notification.png)

Figure 3. IBM Cloud Monitoring notifications

For more information about configuring notifications, see [Working with notification channels](https://cloud.ibm.com/docs/monitoring?topic=monitoring-notificationsnotifications).
2. If you return to one of the dashboards that you created, you can click on the action menu in the upper right corner for any panel, and then click Create Alert from the drop-down menu.

Zoom

!
The alerts that you set up might not be related to a storage volume issue, but to issues that occurred within your app, on the worker node, or in the cluster.



* [Troubleshooting persistent storage volumes](https://cloud.ibm.com/docs/containers?topic=containers-debug_storage_file).
* [Troubleshooting worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_reload).
* [Troubleshooting apps](https://cloud.ibm.com/docs/containers?topic=containers-debug_apps).
* [Troubleshooting clusters](https://cloud.ibm.com/docs/containers?topic=containers-debug_clusters).
* [Open a support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).
Sending SMS alerts by using IBM Cloud Event Notifications 

In the IBM Cloud Monitoring service, you can configure single alerts and multi-condition alerts to notify support staff by an SMS (Short Message Service) message about problems that might require attention. Alerts can generate notifications to the IBM Cloud Event Notifications service to be handled as configured in that service.

[IBM Cloud Event Notifications is available in a limited number of regions](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-regions-endpoints). Your IBM Cloud Monitoring and IBM Cloud Event Notifications instances must be in the same region to communicate with one another. Because of this, support for integration with IBM Cloud Event Notifications is limited to the regions where IBM Cloud Event Notifications is supported and where IBM Cloud Monitoring is also installed.

SMS messages can only be sent to phone numbers in the United States and Canada.

IBM Cloud Event Notifications supports message concatenation so SMS messages longer than 160 characters can be sent. However, messages will be sent in blocks of at most 160 characters. Multiple messages might result in additional charges to the recipient.

For a step-by-step tutorial, see [Sending SMS notifications to IBM Cloud Event Notifications](https://cloud.ibm.com/docs/monitoring?topic=monitoring-tutorial-en-sms).

To configure 1 instance of the IBM Cloud Monitoring service to send notifications to IBM Cloud Event Notifications to be sent as an SMS message, do the following:



 Step 1. Provision an IBM Cloud Event Notifications instance 

Provision an [IBM Cloud Event Notifications instance.](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-create-en-instance)

The IBM Cloud Event Notifications instance must be provisioned in the same region as the Monitoring instance.

The number of events and filters that are available with IBM Cloud Event Notifications depends on the pricing plan selected. Review the limitations statement when creating your IBM Cloud Event Notifications instance for [plan limitations](https://cloud.ibm.com/catalog/services/event-notifications).





 Step 2.
Make the changes that you want to the name and description, add or delete email addresses, and add, remove, or edit webhooks.
3. Click Edit to save your changes.







 Deleting an alert policy by using the console 

To delete an alert policy:



1. Click the overflow menu of the alert in the Alerts section and select Delete.
2. Click Delete in the confirmation message.



You can delete only alerts that you created.







 Configuring alert policies by using the CLI 

Configure alert policies by using the CLI.



 Listing all alert policies by using the CLI 

To list all alert policies by using the CLI, run the following command:

ibmcloud cis alert-policy list [-i, --instance INSTANCE] [--output FORMAT]

Where:



* -i, --instance value is the instance name or ID.
* --output value specifies the output format; only JSON is supported.







 Getting the details of an alert policy by using the CLI 

To get the details of an alert policy by using the CLI, run the following command:

ibmcloud cis alert-policy get POLICY_ID [-i, --instance INSTANCE] [--output FORMAT]

Where:



* POLICY_ID is the ID of alert policy.
* -i, --instance value is the instance name or ID.
* --output value specifies the output format; only JSON is supported.







 Creating a DDoS Attack Alert by using the CLI 

To create a DDoS attack alert policy by using the CLI, run the following command:

ibmcloud cis alert-policy ddos-attack-l7-alert-create --name NAME (--emails EMAILS | --webhooks WEBHOOKS) --enabled (true | false) [--description DESCRIPTION] [-i, --instance INSTANCE] [--output FORMAT]

Where:



* --name value is the name of the alert policy.
* --description value is the description for the alert policy.
* --emails value is the email addresses for dispatching an alert notification.
For more information, see [Collecting metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-about-collect-metrics).





 Sending metrics 

You can send metrics via the public or the private endpoints by using the appropriate ingestion URL. Details can be found in the [endpoints](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpointsendpoints) section.





 Viewing metrics 

You can monitor and manage metrics through the Monitoring Web UI. For more information, see [Viewing metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-monitoring).

Notice that there is a delay showing metric data for new time series. Data is not ready until the initial indexing of a new metric source is completed. Therefore, new sources such as clusters, platform metrics, or systems that you configure, all take some time to become visible through the Monitoring UI.





 Sending notifications 

You can configure single alerts and multi-condition alerts to notify about problems that may require attention. When an alert is triggered, you can be notified through 1 or more notification channels. An alert definition can generate multi-channel notifications.

An alert is a notification event that you can use to warn about situations that require attention. Each alert has a severity status. This status informs you about the criticality of the information it reports on.

For example, you can set up Monitoring to send alert notifications to IBM Cloud Event Notifications.



* [Sending email notifications to IBM Cloud Event Notifications](https://cloud.ibm.com/docs/monitoring?topic=monitoring-tutorial)
* [Sending SMS notifications to IBM Cloud Event Notifications](https://cloud.ibm.com/docs/monitoring?topic=monitoring-tutorial-en-sms)



For more information, see [Working with alerts and events](https://cloud.ibm.com/docs/monitoring?topic=monitoring-alerts).





 Data location 

Metric data is hosted on the IBM Cloud.
* Preconfigured vSphere alarms - The vSphere event and alarm subsystem has a number of default alarms, which monitor the operations of vSphere inventory objects. You must set up actions only for these alarms.









 Alarm setup workflow 

VMware provides preconfigured vCenter alarms that are described in the following tables, but they are set with an action to display within the vCenter web client only. Configure the SMTP server details and then set the alert actions to send an email to the system administrators for the following alarms only initially so not to inundate the system administrator team. For more information, see [Send email as an alarm action](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.monitoring.doc/GUID-1F940DAF-933B-44B7-A200-7A11B5D3E3D5.html).

The setting alarms workflow is as follows.



* Configure the SMTP server details.
* Configure the alert actions for clusters, hosts, datastores, and critical virtual appliances, such as vCenter Server Appliance, PSC, NSX Manager, and controllers.



* Cluster - a VMware High Availability error.
* Hosts - CPU status, memory status, storage status, hardware status that is, voltage, temperature, or power status changes.
* Datastore - low on free disk space.
* Critical virtual appliance - CPU usage, memory usage, disk latency



* Use the proactive daily task to review the following information.



* Review the alerts sent - are the alerts required?
* Review the alerts that weren't sent - do you need to know about them?
* Review the metrics - are the metrics correct? For example, confirm that CPU usage must be set to 75% rather than 90% now that you understand your baseline.
* Do you need to configure your own alarms?
* Do you need to include virtual machines?









 Typical alarm workflow
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-create-alert-webhook-options" "> --><-- <section "id="section-create-alert-webhook-examples" "> --> Examples Create an alert webhook for instance cis-demo. ibmcloud cis alert-webhook-create --name testwebhook --url https://hooks.slack.com/services/Ds3fdBFbV/1234568 --secret 007 -i "cis-demo"
<-- </section "id="section-create-alert-webhook-examples" "> --><-- </section "id="section-create-alert-webhook" "> --><-- <section "id="section-update-alert-webhook" "> --> ibmcloud cis alert-webhook-update Update an alert webhook. cis alert-webhook-update WEBHOOK_ID --name NAME] --url URL] --secret SECRET] -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-update-alert-webhook-options" "> --> Command options WEBHOOK_ID: The ID of alert webhook. Required.--name: The name of the webhook.--url: The POST endpoint to call when dispatching an alert.--secret: The secret that will be passed in the webhook auth header when dispatching a webhook alert.-i, --instance: Instance name or ID.
Filtering on different configuration changes is also possible. You can filter events that are related to a specific service type. For example, you can filter on all IBM Key Protect instances by specifying kms.instance.

To filter when keys are created or deleted in the IBM Key Protect service, you can specify kms.secrets.create OR kms.secrets.delete.

See the events that are generated by the services to determine what configuration changes you want to be alerted.

[Save the rule](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-view_logsview_logs_step7).
4. [Configure the alert](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-alertsalerts_create). Select 1 or more notification channels. Valid channels are email, Slack, PagerDuty, webHook, and Monitoring. Select the type of alert, and define the condition that determines when the alert is triggered. For more information, see [Working with alerts](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-alerts).



For the query instance.create OR instance.delete OR instance.update, the alert will trigger when a service instance is created, deleted, or updated in any region in your account. If you choose an email notification channel, the notification will be sent to the designated email address.





 Configuring alerts by using the API 

You can configure alerts in Activity Tracker by using the Configuration REST API.



* You can use the POST method to create an alert.
* You can use the PUT method to modify an existing alert. You can use the DELETE method to delete a view and associated alerts.
* You can use the DELETE method to delete an alert.



For more information, see [Managing views and alerts programmatically](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-config-api).
,"transaction_id":"6a25fd3d-8530-43b9-96a5-ede2a7712bc9"}
Show more
* The following example shows the target device configuration example.

{"fcm_devices": "deviceidstring"],"user_ids": "useridstring"], "platforms": "G"]!!!!!!}
* The following example shows the send notification general payload for cli version above 0.1.1

ibmcloud en send-notifications --instance-id <instance-id> --body '{"id": "b2198eb8-04b1-48ec-a78c-ee87694dd845", "time": "2018-04-05T17:31:00Z","type": "","subject": "This is a simple monitoring test alert","message_text": "Hi, Welcome from the IBM Cloud - Event Notifications service", "message_subject": "This is a simple monitoring test alert","source": "apisource/git", "specversion": "1.0","ibmensourceid": "e9785d21-4780-467a-8836-c530f5v6738:api","data": {"alert": "En Proactive monitoring","message": "Hi, Welcome from the IBM Cloud - Event Notifications service"},"ibmenfcmbody": "{"notification": {"title": "En Proactive monitoring test alert"}}","ibmenpushto": "{"platforms": "push_chrome", "push_firefox", "push_android"]!!!!! ! ! ! ! ! ! ! ! ! ! ! ! !
The value of this parameter must be a multiple of 60000000 microseconds.





 version (integer) 

Version of an alert.

The version changes every time you update an alert.

The version is used for optimistic locking.







 Query parameters 



 alertId (integer) 

ID of an alert.





 from (long) 

Defines the start timestamp, in microseconds, that is used when you request information about alerts that are defined.





 to (long) 

Defines the end timestamp, in microseconds, that is used when you request information about alerts that are defined.