--- title: Schedule and retrieve LogRhythm alarms description: After you preview the security incident with the LogRhythm alarms that you have selected and mapped, you are ready to schedule alarm retrieval. After you complete this step, the alarm profile is ready to be activated. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/security-management/security-incident-response/schedule-and-alarm-retrieval-logrhythm.html release: australia product: Security Incident Response classification: security-incident-response topic_type: task last_updated: "2026-03-12" reading_time_minutes: 3 breadcrumb: [Create an alarm profile, LogRhythm Overview, Security Incident Response integrations, Security Incident Response, Enterprise security case management applications, Security Operations] --- # Schedule and retrieve LogRhythm alarms After you preview the security incident with the LogRhythm alarms that you have selected and mapped, you are ready to schedule alarm retrieval. After you complete this step, the alarm profile is ready to be activated. ## Before you begin Role required: sn\_si.admin ## About this task Scheduling permits you to modify the scheduling and the types of alarms selected for retrieval. You filter the alarms you ingest based on a date range or on specific alarm IDs. With this step, you determine whether you want to ingest historical alarms, and how often you poll for future alarms that match the alarm profile configuration. ## Procedure 1. Click the **Scheduling** step on the progress bar. \[Omitted image "logrhythm\_scheduling.png"\] Alt text: Scheduling highlighted on progress bar. 2. Choose from the following options to configure your alarm retrieval.
| Option | Description |
|---|---|
| **Enable incremental alarm retrieval** | Default is selected. Select this option to retrieve incremental alarms. |
| **Polling interval \(in minutes\)** | The ServiceNow AI Platform instance pulls from the LogRhythm Client Console for new alarms every one minute. If mapped alarms are found, and filtering criteria are matched, security incidents are created. This setting can be changed, however, the default setting balances alarm ingestion against server load and retrieves the most current data. |
| **Next Alarm ingestion time \(estimated\)** | Displays when the next scheduled ingestion would occur for the current alarm profile. This is only an estimated time. |
| **Enable historical alarm retrieval** | Default is cleared. No historical data is pulled.If selected, the following fields are displayed. Choose one to configure retrieval either by date or alarm ID. - **Enable pulling start date** Default is cleared. Select this option to enable the pulling date. - **Pulling start date** Default is cleared. Select this option to set the pulling start date. Click the calendar icon to enter a date and time. Alarms are pulled from the date and time you enter to the current date. - **Ingest specific alarm Alarm ID\(s\)** Default is cleared. Select this option to ingest specific alarm Alarm IDs. - **AlarmID\(s\)** Enter specific alarm IDs. You pull the specified alarms, and you can enter multiple alarm IDs separated by commas. **Note:** After a historical, one-time pull of alarms is completed, this check box is cleared. You will need to select this check box again before you execute another one-time pull of historical alarms. |