Component configuration sections - Amazon CloudWatch
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Component configuration sections

A component configuration includes several major sections. Sections in a component configuration can be listed in any order.

  • alarmMetrics (optional)

    A list of metrics to monitor for the component. All component types can have an alarmMetrics section.

  • logs (optional)

    A list of logs to monitor for the component. Only EC2 instances can have a logs section.

  • processes (optional)

    A list of processes to monitor for the component. Only EC2 instances can have a processes section.

  • subComponents (optional)

    Nested instance and volume subComponent configuration for the component. The following types of components can have nested instances and a subComponents section: ELB, ASG, custom-grouped EC2 instances , and EC2 instances.

  • alarms (optional)

    A list of alarms to monitor for the component. All component types can have an alarm section.

  • windowsEvents (optional)

    A list of windows events to monitor for the component. Only Windows on EC2 instances have a windowsEvents section.

  • JMXPrometheusExporter (optional)

    JMXPrometheus Exporter configuration.

  • hanaPrometheusExporter (optional)

    SAP HANA Prometheus Exporter configuration.

  • haClusterPrometheusExporter (optional)

    HA Cluster Prometheus Exporter configuration.

  • netWeaverPrometheusExporter (optional)

    SAP NetWeaver Prometheus Exporter configuration.

  • sapAsePrometheusExporter (optional)

    SAP ASE Prometheus Exporter configuration.

The following example shows the syntax for the subComponents section fragment in JSON format.

[ { "subComponentType" : "AWS::EC2::Instance", "alarmMetrics" : [ list of alarm metrics ], "logs" : [ list of logs ], "processes": [ list of processes ], "windowsEvents" : [ list of windows events channels configurations ] }, { "subComponentType" : "AWS::EC2::Volume", "alarmMetrics" : [ list of alarm metrics ] } ]

Component configuration section properties

This section describes the properties of each component configuration section.

Metric

Defines a metric to be monitored for the component.

JSON

{ "alarmMetricName" : "monitoredMetricName", "monitor" : true/false }

Properties

Log

Defines a log to be monitored for the component.

JSON

{ "logGroupName" : "logGroupName", "logPath" : "logPath", "logType" : "logType", "encoding" : "encodingType", "monitor" : true/false }

Properties

  • logGroupName (required)

    The CloudWatch log group name to be associated to the monitored log. For the log group name constraints, see CreateLogGroup.

  • logPath (required for EC2 instance components; not required for components that do not use CloudWatch Agent, such as Amazon Lambda)

    The path of the logs to be monitored. The log path must be an absolute Windows system file path. For more information, see CloudWatch Agent Configuration File: Logs Section.

  • logType (required)

    The log type decides the log patterns against which Application Insights analyzes the log. The log type is selected from the following:

    • SQL_SERVER

    • MYSQL

    • MYSQL_SLOW_QUERY

    • POSTGRESQL

    • ORACLE_ALERT

    • ORACLE_LISTENER

    • IIS

    • APPLICATION

    • WINDOWS_EVENTS

    • WINDOWS_EVENTS_ACTIVE_DIRECTORY

    • WINDOWS_EVENTS_DNS

    • WINDOWS_EVENTS_IIS

    • WINDOWS_EVENTS_SHAREPOINT

    • SQL_SERVER_ALWAYSON_AVAILABILITY_GROUP

    • SQL_SERVER_FAILOVER_CLUSTER_INSTANCE

    • DEFAULT

    • CUSTOM

    • STEP_FUNCTION

    • API_GATEWAY_ACCESS

    • API_GATEWAY_EXECUTION

    • SAP_HANA_LOGS

    • SAP_HANA_TRACE

    • SAP_HANA_HIGH_AVAILABILITY

    • SAP_NETWEAVER_DEV_TRACE_LOGS

    • PACEMAKER_HIGH_AVAILABILITY

  • encoding (optional)

    The type of encoding of the logs to be monitored. The specified encoding should be included in the list of CloudWatch agent supported encodings. If not provided, CloudWatch Application Insights uses the default encoding of type utf-8, except for:

    • SQL_SERVER: utf-16 encoding

    • IIS: ascii encoding

  • monitor (optional)

    Boolean that indicates whether to monitor the logs. The default value is true.

Process

Defines a process to be monitored for the component.

JSON

{ "processName" : "monitoredProcessName", "alarmMetrics" : [ list of alarm metrics ] }

Properties

  • processName (required)

    The name of the process to be monitored for the component. The process name must not contain a process stem, such as sqlservr or sqlservr.exe.

  • alarmMetrics (required)

    A list of metrics to monitor for this process. To view process metrics supported by CloudWatch Application Insights, see Amazon Elastic Compute Cloud (EC2) .

JMX Prometheus Exporter

Defines the JMX Prometheus Exporter settings.

JSON

"JMXPrometheusExporter": { "jmxURL" : "JMX URL", "hostPort" : "The host and port", "prometheusPort" : "Target port to emit Prometheus metrics" }

Properties

  • jmxURL (optional)

    A complete JMX URL to connect to.

  • hostPort (optional)

    The host and port to connect to through remote JMX. Only one of jmxURL and hostPort can be specified.

  • prometheusPort (optional)

    The target port to send Prometheus metrics to. If not specified, the default port 9404 is used.

HANA Prometheus Exporter

Defines the HANA Prometheus Exporter settings.

JSON

"hanaPrometheusExporter": { "hanaSid": "SAP HANA SID", "hanaPort": "HANA database port", "hanaSecretName": "HANA secret name", "prometheusPort": "Target port to emit Prometheus metrics" }

Properties

  • hanaSid

    The three-character SAP system ID (SID) of the SAP HANA system.

  • hanaPort

    The HANA database port by which the exporter will query HANA metrics.

  • hanaSecretName

    The Amazon Secrets Manager secret that stores HANA monitoring user credentials. The HANA Prometheus exporter uses these credentials to connect to the database and query HANA metrics.

  • prometheusPort (optional)

    The target port to which Prometheus sends metrics. If not specified, the default port 9668 is used.

HA Cluster Prometheus Exporter

Defines the HA Cluster Prometheus Exporter settings.

JSON

"haClusterPrometheusExporter": { "prometheusPort": "Target port to emit Prometheus metrics" }

Properties

  • prometheusPort (optional)

    The target port to which Prometheus sends metrics. If not specified, the default port 9664 is used.

NetWeaver Prometheus Exporter

Defines the NetWeaver Prometheus Exporter settings.

JSON

"netWeaverPrometheusExporter": { "sapSid": "SAP NetWeaver SID", "instanceNumbers": [ "Array of instance Numbers of SAP NetWeaver system "], "prometheusPort": "Target port to emit Prometheus metrics" }

Properties

  • sapSid

    The 3 character SAP system ID (SID) of the SAP NetWeaver system.

  • instanceNumbers

    Array of the instance Numbers of SAP NetWeaver system.

    Example: "instanceNumbers": [ "00", "01"]

  • prometheusPort (optional)

    The target port to which to send Prometheus metrics. If not specified, the default port 9680 is used.

SAP ASE Prometheus Exporter

Defines the SAP ASE Prometheus Exporter settings.

JSON

"sapASEPrometheusExporter": { "sapAseSid": "SAP ASE SID", "sapAsePort": "SAP ASE database port", "sapAseSecretName": "SAP ASE secret name", "prometheusPort": "Target port to emit Prometheus metrics", "agreeToEnableASEMonitoring": true }

Properties

  • sapAseSid

    The three-character SAP system ID (SID) of the SAP ASE system.

  • sapAsePort

    The SAP ASE database port by which the exporter will query ASE metrics.

  • sapAseSecretName

    The Amazon Secrets Manager secret that stores ASE monitoring user credentials. The SAP ASE Prometheus exporter uses these credentials to connect to the database and query ASE metrics.

  • prometheusPort (optional)

    The target port to which Prometheus sends metrics. If not specified, the default port 9399 is used. If there is another ASE DB that is using the default port, then we use 9499.

Windows Events

Defines Windows Events to log.

JSON

{ "logGroupName" : "logGroupName", "eventName" : "eventName", "eventLevels" : ["ERROR","WARNING","CRITICAL","INFORMATION","VERBOSE"], "monitor" : true/false }

Properties

  • logGroupName (required)

    The CloudWatch log group name to be associated to the monitored log. For the log group name constraints, see CreateLogGroup.

  • eventName (required)

    The type of Windows Events to log. It is equivalent to the Windows Event log channel name. For example, System, Security, CustomEventName, etc. This field is required for each type of Windows event to log.

  • eventLevels (required)

    The levels of event to log. You must specify each level to log. Possible values include INFORMATION, WARNING, ERROR, CRITICAL, and VERBOSE. This field is required for each type of Windows Event to log.

  • monitor (optional)

    Boolean that indicates whether to monitor the logs. The default value is true.

Alarm

Defines a CloudWatch alarm to be monitored for the component.

JSON

{ "alarmName" : "monitoredAlarmName", "severity" : HIGH/MEDIUM/LOW }

Properties

  • alarmName (required)

    The name of the CloudWatch alarm to be monitored for the component.

  • severity (optional)

    Indicates the degree of outage when the alarm goes off.