vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud cis alert-policy pool-toggle-alert-create --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-create-pool-toggle-alert" "> --> Command options --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-create-pool-toggle-alert" "> --><-- <section "id="section-create-pool-toggle-alert-examples" "> --> Examples Create a pool toggle alert policy for instance cis-demo. ibmcloud cis alert-policy pool-toggle-alert-create --name test1 --emails test1@cn.ibm.com --enabled true --pools all --trigger-condition enabled --include-future-pools true -i "cis-demo"
Select Everything or a view.

Filter event data then click Save as new view. The Create new view page opens.

Enter a name for the view in the Name field.

Optionally, add a category. Enter a name and then click Add this as new view category.

Click Save View







 Step 2. Create the alert 

Next, you must attach an alert to the view.

You can choose any of the following options:



* Create a preset and attach the preset to the view
* Create a specific alert on the view.



You can attach multiple notification channels to a view. You can define different triggering conditions to each notification channel.



 Create an alert by using a preset 

Complete the following steps to attach a preset to a view:



1. [Configure a preset (alert template)](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-preset_uipreset_ui_create).
2. Click the Views icon ![Views icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/alerts/images/views.png). Select the view name. Then, select Attach an alert.
3. In the section Choose preset, select a preset.
4. Click Save alert.







 Create an alert on a view 

Complete the following steps to attach an alert to a view:



1. In the web UI, click the Views icon ![Views icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/alerts/images/views.png).
2. Click the view name. Then, select Attach an alert.
3. Select View-specific alert.
4.
IBM Cloud Monitoring 

You can use monitoring to gain operational visibility into the performance and health of your applications, services, and platforms. When you set up monitoring, you can define [alerts](https://docs.sysdig.com/en/alerts.html) that notify you when an event or an issue occurs that requires your attention. You can send alerts over a variety of [supported notification channels](https://cloud.ibm.com/docs/monitoring?topic=monitoring-notifications), including IBM Cloud® Functions actions. For more information, see [Sending SMS alerts using Cloud Functions](https://cloud.ibm.com/docs/monitoring?topic=monitoring-cf_sms).

IAM-secured Cloud Functions actions, as well as web actions can be used by the notification channel. For more information about setting up the Cloud Functions notification channel, see [Configure IBM Cloud Function Channel](https://docs.sysdig.com/en/configure-ibm-cloud-functions-channel.html).
Sending an SMS notification 

You can send SMS alerts to notify on data hosted in a Activity Tracker instance.

To send an SMS alert, you can choose 1 of the following options:



* Integrate with the IBM Cloud Monitoring service to send SMS alerts.

Use this option when you need alerts on log data alongside system health metrics.
* Integrate with PagerDuty to send SMS alerts.

Use this option when you require call times and escalation management processes.





 Send an SMS notification by using the IBM Cloud Monitoring service 

When the Activity Tracker service sends a notification to the IBM Cloud Monitoring service, an event is created in the IBM Cloud Monitoring instance. You can then configure the IBM Cloud Monitoring service to send an SMS.

CComplete the following steps to get an SMS notification when an alert in the Log Analysis service is triggered:



 Step 1. Configure an alert in IBM Cloud Activity Tracker 

In the Activity Tracker web UI, [configure a Monitoring alert](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-monitoring).

When an alert is triggered, a notification is sent to the Monitoring instance that you have configured. Then, you manage alerts through the Events view section in the Monitoring UI.





 Step 2. Configure the Monitoring instance 

Complete the following steps:



1. [Define an IBM Cloud Event Notifications notification channel in your Monitoring instance](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-monitoringmonitoring-config).
2. Define an alert from the event that triggers the IBM Cloud Activity Tracker alert.

In the Events section of the Monitoring UI, configure an event that send an SMS notification based on the alert that youd defined previously:



1. Select an alert. Then select Create Alert from Event.
2. Enter a name, a description, a group, and the severity level. The group default is set unless you specify a custom one.
3. Define the condition that triggers the SMS notification.

Specify events that match the alerts being sent to Monitoring from Activity Tracker.
* [App alerts](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorapp-level-alerts)
* [Worker node alerts](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorworker-node-level-alerts)
* [Zone alerts](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorzone-level-alerts)
* [Cluster alerts](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorcluster-level-alerts)
* [Account alerts](https://cloud.ibm.com/docs/containers?topic=containers-health-monitoraccount-level-alerts)
* [Block Storage for VPC alerts](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorvpc-block-storage-alerts)



* [Monitoring worker node health in with Autorecovery](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorautorecovery)



* [Understanding the configmap components](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorconfigmap-components)
* [Understanding the individual components of health checks](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorhealth-check-components)





[Reviewing service, API server, and worker node logs](https://cloud.ibm.com/docs/containers?topic=containers-health-audithealth-audit)



* [Kubernetes API server audit logs](https://cloud.ibm.com/docs/containers?topic=containers-health-auditaudit-api-server)



* [Considerations and prerequisites](https://cloud.ibm.com/docs/containers?topic=containers-health-auditprereqs-apiserver-logs)
logdnaat.alert.create This event is generated when an alert is created as a preset. 
 logdnaat.alert.update This event is generated when an alert is updated. 
 logdnaat.alert.delete This event is generated when an alert is deleted. 



The following table lists custom fields that are included in these events:



Table 24. Custom fields for view actions

 Custom fields Description 

 requestData.alertId Defines the preset ID. 
 requestData.name Defines the name of the preset. 
 requestData.preset Defines whether the alert is defined as a preset. 
 requestData.channels List of channels that are configured in a preset. Each channel includes information about the notification method and the trigger conditions per method. 
 responseData.logdnaId Defines the Activity Tracker ID that is associated with the Activity Tracker instance. 







 Dashboards 



Table 25. Events for dashboards

 Action Description 

 logdnaat.board.create This event is generated when a dashboard is created. 
 logdnaat.board.delete This event is generated when a dashboard is deleted. 
 logdnaat.board-graph.update This event is generated when a graph is added to a dashboard. 



The following table lists custom fields that are included in these events:



Table 26. Custom fields for boards

 Custom fields Description 

 requestData.boardId Defines the ID of the dashboard. 
 requestData.category Defines the category where the board is included. 
 requestData.title Defines the name of the dashboard. 
 requestData.graphId Defines the ID of a graph that is added to a board. 
 responseData.logdnaId Defines the Activity Tracker ID that is associated with the Activity Tracker instance. 









 Viewing events 

Events that are generated by an instance of the Activity Tracker service are automatically forwarded to the Activity Tracker service instance that is available in the same location. For more information, see [Cloud services locations](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-cloud_services_locations).

Activity Tracker can have only one instance per location.
[Settings icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/alerts/images/admin.png).
2. Select ALERTS.

You can see the list of alerts that are muted. Each entry informs about the view where notifications are muted, the user who requested the action, and the UTC time when notifications will be enabled.
3. Select an alert that you want to unmute.
4. Click Unmute.
A graph will help you determine the number of log entries for the timezone and time range.



6. Specify 1 or more email addresses.
7. Optional: You can click Test to test that your alert configuration is correct.
8. Click Save Alert.







 Muting an alert 

This section only applies to email alerts.

After you configure an alert on a view and receive a notification email, complete the following steps to mute the alert a period of time:



1. Go to the email account where you receive email notifications.
2. Open a notification email for a view that you want to mute.

Look for emails that are sent by IBM Cloud Activity Tracker. The subject includes the name of the view.

In the email, there is a section that includes the following text:

Mute these alerts for [1 Hour] [6 Hours] [12 Hours] [1 Day]
3. Choose a period of time.

A window opens. The information provided indicates the view, the notification that is muted, and the time period that is muted for.

For example, you can get a message that indicates the following:

Email alerting for MyView has been muted for an hour.

Unmute

Alerting is scheduled to resume at Jun 14, 11:59am.

Manage Alerts

From this page, you can select Unmute to enable notifications on the view. You can also select Manage to go to the ALERTS dashboard in the web UI.







 Unmuting a muted alert 

You can manage alerts through the ALERTS dashboard.



1. Launch the ALERTS dashboard.

In the web UI, select the Settings icon ![Settings icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/alerts/images/admin.png).

Select ALERTS.

You can see the list of alerts that are muted.
[enter API example here]

A successful response returns the CRN value of your connected Event Notifications service instance. For more information about the required and optional request parameters, see the [API docs](https://cloud.ibm.com/apidocs/projects).







 Delivering notifications to select destinations 

After you enable notifications for projects, create topics and subscriptions in Event Notifications so that alerts can be forwarded and delivered to your selected destinations.

For a complete list of supported destinations, see the [Event Notifications documentation](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-destination).



 Email notifications 

You can use the [IBM Cloud email service](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-destinations-email) as a delivery channel for projects event notifications. [Create an Event Notifications subscription](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-create-en-subscription) between an existing topic and the IBM Cloud email service to forward your alerts to various recipients by email.

An email from IBM Cloud that contains information about a projects event resembles the following example:

Subject: Validation successful for terrafrom-1234567890-a12a triggered by IBMid-12345ABCD1
Body: Validation is complete. Review and approve the validation results to deploy the changes.
Project Service event details:
Type: check.pipeline.succeeded
Target: Config terrafrom-1234567890-a12a for Project example-email-notification-project
Source: pipelinerun-123ab1ab-1a1a-1a11-1a12-ac1a1a12a12a
Triggered by: IBMid-12345ABCD1
Action URL: https://cloud.ibm.com/devops/pipelines/example
Date: Fri April 10 2023 09:15:08 GMT-0500 (Eastern Standard Time)
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-firewall-events-alert" "> --><-- <section "id="section-firewall-events-alert-examples" "> --> Examples Create a firewall-events alert for instance cis-demo. ibmcloud cis alert-policy firewall-events-alert-create --name test1 --emails test1@cn.ibm.com --enabled true --domains d2633e61-1b61-2512-1321-b61a17c3db7e --service waf,ratelimit -i "cis-demo"
<-- </section "id="section-firewall-events-alert-examples" "> --><-- </section "id="section-firewall-events-alert" "> --><-- <section "id="section-certificate-alert" "> --> ibmcloud cis alert-policy certificate-alert-create Create an alert policy for certificate events. ibmcloud cis alert-policy certificate-alert-create --type (universal | dedicated) --name NAME (--emails EMAILS | --webhooks WEBHOOKS) --enabled (true | false) --description DESCRIPTION] -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-opt-certificate-alert" "> --> Command options --type: The type of the certificate.--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.
mediumErrors ............................ 20
smartWarning ............................ 0

/opt/MegaRAID/storcli/storcli64 /c0/eall/sall show all | grep -iE "det|cou|tem|SN|S.M|fir”

You use this command to show the specific drives and any possible drive errors that it might have.
The following example shows the output:

Drive /c0/e252/s0 - Detailed Information:

Shield Counter = 0

Media Error Count = 0

Other Error Count = 0

Drive Temperature = 24C (75.20 F)

Predictive Failure Count = 0

S.M.A.R.T alert flagged by drive = No

SN = XXXX

Firmware Revision = SN04

Drive /c0/e252/s1 - Detailed Information:

Shield Counter = 0

Media Error Count = 0

Other Error Count = 0

Drive Temperature = 22C (71.60 F)

Predictive Failure Count = 0

S.M.A.R.T alert flagged by drive = No

SN = xxxx

Firmware Revision = SN03

Drive /c0/e252/s2 - Detailed Information:

Shield Counter = 0

Media Error Count = 0

Other Error Count = 0

Drive Temperature = 21C (69.80 F)

Predictive Failure Count = 0

S.M.A.R.T alert flagged by drive = No

SN = xxxx

Firmware Revision = SN04

Drive /c0/e252/s3 - Detailed Information:

Shield Counter = 0

Media Error Count = 0

Other Error Count =

Drive Temperature = 23C (73.40 F)

Predictive Failure Count = 0

S.M.A.R.T alert flagged by drive = No
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 example, --emails test1@cn.ibm.com,test2@cn.ibm.com.
* --webhooks value is the webhook IDs for dispatching an alert notification. For example, --webhooks webhookID1,webhookID2.
* --enabled value determines whether the alert policy is enabled.
* -i, --instance value is the instance name or ID.
* --output value specifies the output format; only JSON is supported.







 Creating a pool toggle alert by using the CLI 

To create a pool toggle alert by using the CLI, run the following command:

ibmcloud cis alert-policy pool-toggle-alert-create --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]

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 example, --emails test1@cn.ibm.com,test2@cn.ibm.com.
* --webhooks value is the webhook IDs for dispatching an alert notification. For example, --webhooks webhookID1,webhookID2.
<-- </section "id="section-list-alert-policies-examples" "> --><-- </section "id="section-list-alert-policies" "> --><-- <section "id="section-show-alert-policy" "> --> ibmcloud cis alert-policy get (Show) Show the details of a given policy. ibmcloud cis alert-policy get POLICY_ID -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-show-alert-policy-options" "> --> Command options POLICY_ID: The ID of alert policy. Required.-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-show-alert-policy-options" "> --><-- <section "id="section-show-alert-policy-examples" "> --> Examples Show the details of alert policy a2633e68-1a64-2512-a321-b64a17c7db7a. ibmcloud cis alert-policy get a2633e68-1a64-2512-a321-b64a17c7db7a -i "cis-demo"
<-- </section "id="section-show-alert-policy-examples" "> --><-- </section "id="section-show-alert-policy" "> --><-- <section "id="section-create-ddos-attack-l7-alert" "> --> ibmcloud cis alert-policy ddos-attack-l7-alert-create Create an alert policy for DDoS attack l7.
[Create an Event Notifications subscription](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-create-en-subscription) between an existing topic and the IBM Cloud email service to forward your alerts to various recipients by email.

An email from IBM Cloud that contains information about a Security and Compliance Center event resembles the following example:

Subject: Validation completed: my-test-validation-scan
Body: The following validation scan was successfully completed in the Security and Compliance Center: my-test-validation-scan. You can view the scan results from the Security and Compliance Center in the console. For more information, check out the docs.

To receive detailed information about an event notification in your email, select the Add notification payload option when you create an Event Notifications subscription. Your email displays the [notification payload details](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-event-notificationsevent-notifications-payload) that are associated with the event.





 Webhooks 

You can configure a webhook destination so that the properties of an incoming notification can be used programmatically by an app or service. For more information, check out the [Event Notifications documentation](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-destinations-webhook).







 Notification payload details 

Successful events that are generated by a Security and Compliance Center component contain various fields that help you to identify the source and details of an event.

Event notifications from Security and Compliance Center contain only metadata properties, such as names or identifiers of resources. Sensitive data, for example API keys or passwords, are not included in generated events.

The metadata properties that are sent to Event Notifications vary depending on the event type and subtype. For example, if an com.ibm.cloud.compliance.posture:posture-scan-completed event takes place, Security and Compliance Center sends a notification payload to Event Notifications that is similar to the following example.

{
"action": "Validation completed",
"summary": "my-test-scan",
Select on for Custom schedule.
2. Select the Timezone for the log entries.
3. Select the days of the week when alerts should be generated.
4. Optionally specify a time range for the selected days. A graph will help you determine the number of log entries for the timezone and time range.



5. Depending on the type of alert you will also need to configure additional settings:

Slack: Specify your Webhook URL and the desired Message color.

Email: Specify the Recipients of the email and a Timezone. The timezone defines the timestamp value of each event that is included in the email. To see UTC timestamps, you can select (GMT +00:00) UTC.

PagerDuty: Specify the Service. If required, you will be prompted to connect to PagerDuty.

Webhook: Specify the Method & URL, and the Headers and Body of the JSON used to interact with your webhook. You can use Validate JSON to make sure your JSON is correct before creating the alert.
6. You can click Test to test that your alert configuration is correct.

![Test option](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/alerts/images/alert_test.png)
7. Click Save Alert
8. If you want to create an additional alert channel, click + and follow the prior steps to create additional channels. You can create different channel types, for example, an email and a Slack channel. Or, you can create multiple channels of the same type with different alert criteria.





Your preset can now be used by others to setup alerts.





 Deleting a preset 

You can manage presets through the ALERTS dashboard.

Complete the following steps to delete a preset from the ALERTS dashboard:



1. In the web UI, select the Settings icon !