---
title: ACC Log Analytics \(ACC-L\) integration configuration fields
description: Description of the fields on the ACC Log Analytics \(ACC-L\) integration configuration forms for Health Log Analytics.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/health-log-analytics/il-connector-hla-accl-fields.html
release: australia
product: Health Log Analytics
classification: health-log-analytics
topic_type: reference
last_updated: "2026-03-12"
reading_time_minutes: 2
keywords: [ACC, Agent Client Collector, Log Analytics, data input, integration, configuration, field, description, ServiceNow, Health Log Analytics, HLA]
breadcrumb: [Integration configuration fields, Health Log Analytics reference, Health Log Analytics, ITOM AIOps, IT Operations Management]
---
# ACC Log Analytics \(ACC-L\) integration configuration fields
Description of the fields on the ACC Log Analytics \(ACC-L\) integration configuration forms for Health Log Analytics.
For the ACC Log Analytics \(ACC-L\) integration setup procedure, see [Set up an ACC Log Analytics integration for Health Log Analytics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/il-connector-hla-accl.md).
|
Field
|
Description
|
|---|
|
Transport
|
The protocol used to send the log data. This field is read-only.The ACC-L integration uses a ServiceNow Agent to send data.
|
|
Port
|
The port on the MID Server to which the ACC-L agent connects. This field is required.**Important:** This port can't be the same as the MID Web Server port.
|
|
Description
|
Option to add a brief description of the integration to help identify it.
|
|
ACC Listener
|
|
MID Server
|
The MID Server to which the logs stream. This field is required.**Note:**
- Only one ACC-L integration can be defined per MID Server.
You can only select MID Servers with AgentClientCollector capability that support basic authentication. MID Servers that support mTLS are not listed.
- The default maximum number of data inputs streaming logs to a single MID Server is 10.
You can modify this number in the MID Server properties. Exception: if 10 non-ACC-L integrations are already defined for a MID Server, you can still add one ACC-L integration, for a total of 11.
- When you submit the form, this field is set to read-only.
- **Important:** The configured MID Server can't be changed after the integration is activated.
|
|
MID Web Server port
|
Port used by the MID Server to receive data from ACC agents. This field is auto-populated and read-only when a MID Server has been configured. **Note:** The MID Web Server port must be reachable through your firewall.
|
|
Field
|
Description
|
|---|
|
Lookup hostnames
|
Option to perform DNS lookup to resolve IPs to hostnames.
|
|
Use SSL
|
Option to use SSL.
|
|
Client inactivity timeout \(seconds\)
|
The timeout, in seconds, to close an inactive channel.
|
|
Sub sample drop ratio
|
The ratio of logs to drop. The default value is -1: no logs are dropped.For example: If you want one out of every five logs to be dropped, change the value to 5.
|
|
Max length in bytes
|
The maximum length of log messages, in bytes.
|
|
Character encoding
|
The character encoding for this integration: UTF-8. This field is read-only.
|
|
Worker thread count
|
The number of threads that handle incoming data.
|
|
Sub sample receive ratio
|
The ratio of logs to receive. The default value is -1: no logs are received.For example: If you want one out of every five logs to be received, change the value to 5.
|
|
Default timezone
|
The default time zone of events. The system uses this default when the log does not specify a time zone.
|
|
Drop if queue is full
|
Option to discard logs if many processes are waiting in the queue to access the MID Server.
|
**Parent Topic:**[Integration configuration fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown)