Skip to content
Data input configuration fields › Health Log Analytics reference › Health Log Analytics › ITOM AIOps › IT Operations Management
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Amazon CloudWatch data input configuration fields

Description of the fields on the Amazon CloudWatch data input configuration form.

Basic configuration

FieldDescription
NameName of the new data input. This field is required.
DescriptionDescription of the data input.
Execute onOption to select whether to use a specific MID Server or a MID Server cluster. This field is required.
MID

(Only when the Execute on field is set to Specific MID Server)

MID Server to which log data from Amazon CloudWatch is pulled. Note:

  • You can select only MID Servers 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.
  • If log ingestion is not enabled for the selected MID Server, Health Log Analytics enables it automatically.

This field is required.

MID Server Cluster

(Only when Execute on is set to Specific MID Server cluster.)

The MID Server cluster to which the log data is pulled. This field is required.The data input runs on a single MID Server in the cluster until that MID Server fails. The system then moves all the data input tasks to the next available MID Server in the cluster according to the configured order.

Note:

  • Health Log Analytics supports only failover MID Server clusters. In these clusters, multiple MID Servers are grouped together for failover protection. When selecting a cluster from the data input or integration form, the MID Server clusters list displays only failover clusters.
  • The MID Server cluster must include only MID Servers that support basic authentication. mTLS is not supported for log ingestion.
  • Log ingestion must be enabled for each MID Server in the cluster. If log ingestion is not enabled for the active MID Server, Health Log Analytics enables it automatically.
  • The default maximum number of data inputs or integrations streaming logs to a single MID Server is 10. A cluster passes capacity validation if it contains at least one MID Server with fewer than 10 data inputs or integrations running on it, even when that MID Server is down.

For more information about MID Server clusters, see Configure a MID Server cluster.

Service instance

The service instance to which to bind the log data.Note: If no relevant service instance exists, Create an service instance and add CIs to it. Set the status of the new service instance to Operational.

This field is required.

The following fields show read-only information:

FieldDescription
StatusStatus of the data input.
TransportProtocol used to stream the log data.This data input uses Amazon CloudWatch to stream log data to your instance.
Sources countThe number of log sources this data input has created.
Disabled sinceThe time when the data input stopped or failed.
Last log timeThe time when the last log streamed in the data input.
Error messageThe streaming error.This field is populated automatically. It displays only when a streaming error has occurred.
FieldDescriptionExample
From

The date and time to start reading the data. Data older than this date and time is not read.Note: Setting this value to a past date might require the system to read large amounts of data, causing congestion.

This field is required.

Now -1 week
Group Name\(s\)The log groups to search. If multiple log groups must be searched, specify the groups in a comma-separated list. To fetch log data from all groups, use an asterisk \(\*\) as a wildcard character.This field is required.hla-cw-loggroup1,hla-cw-loggroup2
PrefixName prefix for the Amazon CloudWatch log streams to read from. The data input reads only from log streams with this name prefix.Note: Only a single log stream prefix per data item is supported. For multiple prefixes, create multiple data inputs.hla-cw
Filter pattern

Pattern by which to filter incoming events. Various types of filter patterns are supported. For example:

  • A pattern for fetching log events that contain a single term.
  • A pattern for fetching log events that contain multiple terms.
  • A pattern for fetching log events that include a term and exclude another.

Note: Filter patterns are case sensitive.

For more information, see https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/FilterAndPatternSyntax.html

- Pattern for fetching log events that contain a single term, "STATUS\_CODE": "STATUS\_CODE" - Pattern for fetching log events that contain multiple terms, “STATUS\_CODE” and “200”: “STATUS\_CODE 200” - Pattern for fetching log events that include a term, “STATUS\_CODE,” and exclude another term, “200”: “STATUS\_CODE” – “200”
FieldDescription
AWS credentialsField that refers to the AWS Credentials list \(aws\_credentials.list\). The list contains the AWS access and secret access keys.
AWS regionThe AWS region where the Amazon CloudWatch cluster runs, for example, us-west-1. For a list of AWS regions, see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html\#concepts-regions This field is required.

Advanced configuration

FieldDescriptionDefault value
Connection timeoutThe number of milliseconds to wait before timing out the AWS connection attempt.1000
Batch sizeThe maximum number of logs retrieved per query.2500
Socket timeoutThe number of milliseconds to wait before timing out a data transfer over an established connection.10000
Default timezoneThe default timezone if the log date and time doesn't include timezone information.GMT
Sub sample drop ratioThe number of logs to batch together, out of which one will be discarded. This setting is used to reduce the number of fetched logs.-1
Sub sample receive ratioThe number of logs to batch together, out of which all but one will be discarded. This setting is used to decrease the number of received logs.-1
Max length in bytesThe maximum length of log messages, in bytes.32766
Sleep intervalThe interval, in seconds, to wait before querying again after a query has returned no logs.60
Polling intervalThe interval, in seconds, to wait before polling for new logs.0
Drop if queue is fullOption to discard logs if there is a load on the MID Server.False

Parent Topic:Data input configuration fields