---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Edit a log policy

# Edit a log policy {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

You can edit published Agent Client Collector log policies. For
example, modify a default log policy if your organization always uses a specific non-default
log path.

## Before you begin

Role required: agent_client_collector_admin

## Procedure

1. Navigate to AllACC Log AnalyticsACC Log Policies.
2. Select a policy for which the Publish status is Published.
3. Select Edit in Sandbox.  
   The policy is now in Draft view, and its fields and check instances are editable.  
   Note:  
   Although the policy is in Draft view, its publish status remains Published.
4. On the Monitored CIs tab, edit the CIs to which the policy applies as needed.
   1. Choose the CI type to be monitored.  
      * Monitored CI type by filter: Select the monitored CI type. You can narrow down the CIs that will be monitored by using filter conditions.
      * Monitored CI type by script: Specify the monitored CIs by using a script.
      * Monitored CI type by CMDB Group: Specify the monitored CIs by using CMDB group queries.

      {#accl-edit-log-policy__ul_s2v_z5g_btb}

      For more information about choosing monitored CI types, see [Create an Agent Client Collector policy](https://servicenow-prod.fluidtopics.net/0KxRUBj1j0vmDDgouYKZ0g "Policies consist of the CIs monitored by the Agent Client Collector and the checks that run on those CIs. When creating a policy, you configure a filter which determines the CIs on which the checks are to run. For example, a policy to run checks on all Apache web servers. You can create new policies or edit the default policies.").
   2. **Optional:** Monitor only CIs that are associated with an Application Service by selecting Filter Monitored CIs by Application Service.  
      You can specify the Application Services to be monitored by using filter conditions. Agent Client Collector will only retrieve the logs of CIs that are associated with these Application Services.
   {#accl-edit-log-policy__substeps_bgc_y5g_btb}
5. **Optional:** In the Check Instances table, select the log shipper check instance record and edit it.  
   For more information, see [Edit log path configurations](https://servicenow-prod.fluidtopics.net/_ls13zN1mEeC69xa45t6Eg "Modify a log path configuration in the log shipper check instance.").
6. Select Save to save the changes you entered into the Sandbox policy fields.  
   The policy remains in Draft view, and the Publish status is Published\*. The asterisk (\*) indicates that the current published version is not the most up to date one, because it contains saved changes that have not yet been published.
7. Select Republish to publish the updates.  
   The policy returns to Published state and opens as the published policy.  
   Note:  
   This option appears only after entering updates into the policy fields, for a policy whose Publish status is Published\*.
8. Determine the active status of the policy by selecting either Activate or Deactivate.
9. **Optional:** Select Delete to delete both the Published and the draft policies.
{#accl-edit-log-policy__steps_vbq_vvl_4sb}

*[\>]: and then