---
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


---

# Set up additional ACC data inputs

# Set up additional ACC data inputs {#ariaid-title1}

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

Data inputs for streaming log messages to your ServiceNow
instance using the Agent Client Collector are created automatically as part
of the Agent Client Collector setup. Set up additional ACC data inputs
manually as needed using the Health Log Analytics data input setup
flow.

## Before you begin

* The Agent Client Collector Log Analytics application has a dependency on the following ServiceNow applications, available from the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home):
  * Health Log Analytics, Version 22.0.12 - December 2021 and later releases.
  * Agent Client Collector -Framework, Version 2.7.0 - December 2021 and later releases.
  {#accl-data-input-setup__ul_hnx_bjn_rqb}
* Verify that a MID Server is installed and configured. For more information, see [MID Server system requirements](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).
* The MID Server must be configured to work with the Agent Client Collector. For more information, see [Enable Agent Client Collector monitoring on the MID Server](https://servicenow-prod.fluidtopics.net/AT1P4nAEwMMFFW~n8utcDQ "Enable Agent Client Collector monitoring on the MID Server by configuring the Agent Client Collector framework (ACC-F) and Metric Intelligence extensions in a single action. Enabling Agent Client Collector monitoring also enables monitoring on agents connected to the MID Server.").
{#accl-data-input-setup__ul_zkp_qch_kqb}  
Important:  
Health Log Analytics does not support IPv6. To work with the application, configure the MID Server to IPv4.

Role required: evt_mgmt_admin

## About this task

It is important to configure an ACC data input for every MID Server to
which Agent Client Collectors can connect, even if no agent is currently connected
to it. An agent works with one MID Server at a time, but is connected
to a different MID Server when necessary to provide failover
protection.  
Important:  
As part of the standard Health Log Analytics data input setup, you can define JavaScript functions for mapping and preprocessing raw log data. The JavaScript function must be identical for all ACC data inputs, because agents will switch to a different ACC data input when the system connects them to a different MID Server to provide failover protection. The latest published JavaScript function is provided to all existing and future ACC data inputs and replaces the previous one. This feature is supported in the Health Log Analytics application, Version 22.0.12 - December 2021 and later, available from the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home).

## Procedure

1. Set up additional ACC data inputs manually using the Health Log Analytics data input setup flow.  
   For more information, see [Configure ACC data inputs manually](https://servicenow-prod.fluidtopics.net/hoAPWUYKorL~nYVw9Eh9vg "Agent Client Collector setup automatically creates an ACC data input for streaming log messages to your ServiceNow instance. You can set up additional ACC data inputs manually as needed.").
2. Identify and address log streaming issues to ensure that your data inputs are streaming data properly.  
   For more information, see [Ensure that the data input is streaming data](https://servicenow-prod.fluidtopics.net/oOfiw4LViA_6PhNwfUsPKQ "Make sure that your ACC data inputs are streaming data properly by identifying and resolving log streaming issues.").
3. Determine how Health Log Analytics handles raw log data that is streaming into your instance.  
   By default, every incoming log line is auto-mapped to the correct tag. If properties aren't discovered automatically, map the data input sources manually by defining a JavaScript function. For more information, see [Map the raw data](https://servicenow-prod.fluidtopics.net/ENjBmAW1AM2qvvmJSA_YiQ "Mapping raw log data that streams into your instance determines how the data is handled. Health Log Analytics automatically structures logs, creates metrics for anomaly detection, and presents alerts based on how your data is tagged.").
4. **Optional:** Modify raw log data and drop or break up log messages before they are processed.  
   Define a JavaScript function that modifies your raw log data before Health Log Analytics maps and structures it. For more information, see [Edit your raw log data before processing](https://servicenow-prod.fluidtopics.net/R8YQ8bBaQwl6UzzSdCocKA "You can modify raw log data and drop or break up log messages before they are processed in the MID Server, and therefore before Health Log Analytics maps and structures it. For example, you could prevent sensitive data from reaching the system by replacing user names and passwords with an asterisk (*).").
5. **Optional:** Refine the source type structure to make sure that Health Log Analytics extracts and classifies all properties correctly.  
   For more information, see [Refine the source type structure](https://servicenow-prod.fluidtopics.net/7xffVJXJtf_JlE08nlOH4w "Fine-tune how Health Log Analytics reads your inner log messages and detects anomalies by customizing the extracted properties in the source type structure.").