OS: Win 2012 R2 version 6.3 (Build 9600)
EC2Config version: 4.9.3429
SSM version: v2.3.542.0
CloudWatch Agent version: version 1.201929.0

Hello,

I recently installed CloudWatch Agent to be able to send EventViewer logs to CloudWatch Logs.
My problem is with two particular servers which both run the exact same versions (see above) as two other servers that are able to send logs to Cloudwatch Agents.

When I run the CloudWatch Agent wizard on the problematic servers I don't get a prompt to initialize "statsd" whereas on the two other servers I get that question in the wizard.

The actual error I encounter when trying to initiate the Agent is this;

Start configuration validation...
Invalid Json input schema.
Under path : /metrics/metrics_collected/statsd | Error : measurement is required
Under path : /metrics/metrics_collected | Error : Additional property statsd is not allowed
2019/05/27 07:22:51 I! AmazonCloudWatchAgent Version 1.201929.0.
Configuration validation first phase failed. Agent version: 1.201929.0. Verify the JSON input is only using features supported by this version.

The parameter store document I am trying to fetch is this;

{
	"logs": {
		"logs_collected": {
			"windows_events": {
				"collect_list": [{
					"event_format": "xml",
					"event_levels": ["WARNING", "ERROR", "CRITICAL"],
					"event_name": "Application",
					"log_group_name": "myloggroup",
					"log_stream_name": "{local_hostname}-Application"
				}, {
					"event_format": "xml",
					"event_levels": ["WARNING", "ERROR", "CRITICAL"],
					"event_name": "Security",
					"log_group_name": "myloggroup",
					"log_stream_name": "{local_hostname}-Security"
				}, {
					"event_format": "xml",
					"event_levels": ["WARNING", "ERROR", "CRITICAL"],
					"event_name": "Setup",
					"log_group_name": "myloggroup",
					"log_stream_name": "{local_hostname}-Setup"
				}, {
					"event_format": "xml",
					"event_levels": ["WARNING", "ERROR", "CRITICAL"],
					"event_name": "System",
					"log_group_name": "myloggroup",
					"log_stream_name": "{local_hostname}-System"
				}]
			}
		}
	},
	"metrics": {
		"namespace": "MyNamespace/Monitoring",
		"metrics_collected": {
			"Processor": {
				"metrics_collection_interval": 300,
				"measurement": ["% Processor Time"],
				"resources": ["*"]
			},
			"LogicalDisk": {
				"metrics_collection_interval": 1200,
				"measurement": ["% Free Space"],
				"resources": ["*"]
			},
			"Memory": {
				"metrics_collection_interval": 300,
				"measurement": ["% Committed Bytes In Use"],
				"resources": ["*"]
			},
			"statsd": {
				"metrics_aggregation_interval": 60,
				"metrics_collection_interval": 10,
				"service_address": ":8125"
			}
		}
	}
}

The exact same SSM parameter successfully runs on the other two servers that have identical versions of EC2Config, SSM and Cloudwatch Agent (as well as the exact same build of the OS).

What am I missing?

Grateful for your input - TheSwede86