Can't Get IIS Log Group in CloudWatch Log Console. After creating Association

I try to analysis IIS logs using aws CloudWatch. I followed the procedure as below link
[ https://aws.amazon.com/blogs/mt/automate-iis-and-httperr-logs-to-amazon-cloudwatch-using-ec2-systems-manager/ ]

Steps followed:

Set up the configuration json file.

Configuration json file:

"IsEnabled": true, "EngineConfiguration": "PollInterval": "00:00:15", "Components": [ "Id": "SystemEventLog", "FullName": "AWS.EC2.Windows.CloudWatch.EventLog.EventLogInputComponent,AWS.EC2.Windows.CloudWatch", "Parameters": "LogName": "System", "Levels": "7" , "Id": "SecurityEventLog", "FullName": "AWS.EC2.Windows.CloudWatch.EventLog.EventLogInputComponent,AWS.EC2.Windows.CloudWatch", "Parameters": "LogName": "Security", "Levels": "7" , "Id": "ETW", "FullName": "AWS.EC2.Windows.CloudWatch.EventLog.EventLogInputComponent,AWS.EC2.Windows.CloudWatch", "Parameters": "LogName": "Microsoft-Windows-WinINet/Analytic", "Levels": "7" , "Id": "IISLogs", "FullName": "AWS.EC2.Windows.CloudWatch.CustomLog.CustomLogInputComponent,AWS.EC2.Windows.CloudWatch", "Parameters": "LogDirectoryPath": "C:\inetpub\logs\LogFiles\W3SVC1", "TimestampFormat": "yyyy-MM-dd HH:mm:ss", "Encoding": "UTF-8", "Filter": "", "CultureName": "en-US", "TimeZoneKind": "UTC", "LineCount": "3" , "Id": "HttpErr", "FullName": "AWS.EC2.Windows.CloudWatch.CustomLog.CustomLogInputComponent,AWS.EC2.Windows.CloudWatch", "Parameters": "LogDirectoryPath": "C:\Windows\System32\LogFiles\HTTPERR", "TimestampFormat": "yyyy-MM-dd HH:mm:ss", "Encoding": "UTF-8", "Filter": "", "CultureName": "en-US", "TimeZoneKind": "UTC", "LineCount": "3" , "Id": "CustomLogs", "FullName": "AWS.EC2.Windows.CloudWatch.CustomLog.CustomLogInputComponent,AWS.EC2.Windows.CloudWatch", "Parameters": "LogDirectoryPath": "C:\CustomLogs\", "TimestampFormat": "MM/dd/yyyy HH:mm:ss", "Encoding": "UTF-8", "Filter": "", "CultureName": "en-US", "TimeZoneKind": "Local" , "Id": "PerformanceCounter", "FullName": "AWS.EC2.Windows.CloudWatch.PerformanceCounterComponent.PerformanceCounterInputComponent,AWS.EC2.Windows.CloudWatch", "Parameters": "CategoryName": "Memory", "CounterName": "Available MBytes", "InstanceName": "", "MetricName": "Memory", "Unit": "Megabytes", "DimensionName": "", "DimensionValue": "" , "Id": "IISCloudWatchLogs", "FullName": "AWS.EC2.Windows.CloudWatch.CloudWatchLogsOutput,AWS.EC2.Windows.CloudWatch", "Parameters": "AccessKey": "---------------------------------", "SecretKey": "----------------------------------", "Region": "us-east-1a", "LogGroup": "RWEBAPP-SERVER", "LogStream": "used our instance id" , "Id": "HttpErrCloudWatchLogs", "FullName": "AWS.EC2.Windows.CloudWatch.CloudWatchLogsOutput,AWS.EC2.Windows.CloudWatch", "Parameters": "AccessKey": "-----------------------------------------", "SecretKey": "-----------------------------------------", "Region": "us-east-1a", "LogGroup": "RckWebServer", "LogStream": "used our instance id-httpErr" , "Id": "CloudWatch", "FullName": "AWS.EC2.Windows.CloudWatch.CloudWatch.CloudWatchOutputComponent,AWS.EC2.Windows.CloudWatch", "Parameters": "AccessKey": "------------------------------", "SecretKey": "------------------------------", "Region": "us-east-1a", "NameSpace": "Windows/Default" ], "Flows": "Flows": [ "IISLogs,IISCloudWatchLogs", "HttpErrLogs,HttpCloudWatchLogs" ]

Then, Configure integration with CloudWatch. Association was created successfully.

Can't see log group in cloudwatch log console..
4.Checked the error log in this file path [C:/ProgramData/Amazon/SSM/Logs]

Error log:

2018-11-12 11:20:06,055 [1] INFO [Framework] - Could not create component because configuration is missing HttpErrLogs and work flow based on this component will not start.
2018-11-12 11:20:06,077 [1] INFO [Framework] - Could not create component because configuration is missing HttpCloudWatchLogs and work flow based on this component will not start.
2018-11-12 11:20:06,077 [1] INFO [Framework] - Could not create component because configuration is missing HttpErrLogs and work flow based on this component will not start.
2018-11-12 11:20:06,077 [1] ERROR [Framework] - Workflow creation failed: Could not create component ID HttpErrLogs. Please verify the components in the workflow are defined in the configuration.
2018-11-12 11:20:06,077 [1] ERROR [Framework] - Could not initialize the CloudWatch plug-in with the provided configuration settings.
2018-11-12 11:20:06,077 [1] ERROR [Framework] - aws:cloudWatch plugin raised exception.
AWS.EC2.Windows.CloudWatch.CloudwatchConfigurationException: Could not initialize the CloudWatch plug-in with the provided configuration settings.
Workflow creation failed: Could not create component ID HttpErrLogs. Please verify the components in the workflow are defined in the configuration.

at AWS.EC2.Windows.CloudWatch.Host.Configure(String configuration)
at Amazon.EC2Services.Config.Plugins.CloudWatch.CloudWatchPlugin.Apply(PluginApplyContext applyContext, PluginArgs pluginArgs)
2018-11-12 11:20:06,102 [1] INFO [Framework] - aws:cloudWatch plugin configuration verified
2018-11-12 11:20:06,102 [1] INFO [aws:cloudWatch] - CloudWatch execution started.
2018-11-12 11:20:06,102 [1] INFO [aws:cloudWatch] - Starting the CloudWatch plug-in
2018-11-12 11:20:06,102 [1] ERROR [aws:cloudWatch] - Host not configured, no data will be uploaded to CloudWatch

asked Nov 13 '18 at 11:19

Karthik

add a comment |

Steps followed:

Set up the configuration json file.

Configuration json file:

Then, Configure integration with CloudWatch. Association was created successfully.

Can't see log group in cloudwatch log console..
4.Checked the error log in this file path [C:/ProgramData/Amazon/SSM/Logs]

Error log:

asked Nov 13 '18 at 11:19

Karthik

add a comment |

Steps followed:

Set up the configuration json file.

Configuration json file:

Then, Configure integration with CloudWatch. Association was created successfully.

Can't see log group in cloudwatch log console..
4.Checked the error log in this file path [C:/ProgramData/Amazon/SSM/Logs]

Error log:

asked Nov 13 '18 at 11:19

Karthik

Steps followed:

Set up the configuration json file.

Configuration json file:

Then, Configure integration with CloudWatch. Association was created successfully.

Can't see log group in cloudwatch log console..
4.Checked the error log in this file path [C:/ProgramData/Amazon/SSM/Logs]

Error log:

iis amazon-ec2 amazon-cloudwatch

asked Nov 13 '18 at 11:19

Karthik

asked Nov 13 '18 at 11:19

Karthik

asked Nov 13 '18 at 11:19

Karthik

asked Nov 13 '18 at 11:19

Karthik

asked Nov 13 '18 at 11:19

Karthik

add a comment |

1 Answer
1

active

oldest

votes

Your ID's dont match HttpErr:


 "Id": "HttpErr",
 "FullName": "AWS.EC2.Windows.CloudWatch.CustomLog.CustomLogInputComponent,AWS.EC2.Windows.CloudWatch",
 "Parameters": 
 "LogDirectoryPath": "C:\Windows\System32\LogFiles\HTTPERR",
 "TimestampFormat": "yyyy-MM-dd HH:mm:ss",
 "Encoding": "UTF-8",
 "Filter": "",
 "CultureName": "en-US",
 "TimeZoneKind": "UTC",
 "LineCount": "3"

But in your Flows your using HttpErrLogs

"Flows": 
 "Flows": [
 "IISLogs,IISCloudWatchLogs",
 "HttpErrLogs,HttpCloudWatchLogs"
 ]

answered Nov 14 '18 at 21:52

MisterSmith

948611

Created a new association with definitions as mentioned in the flows in json and restart the SSM Agent. There is no error in the log. But I can't get the log group in CloudWatch log console.

– Karthik
Nov 15 '18 at 13:45

Change "Region": "us-east-1a" to "Region": "us-east-1". us-east-1a is an availability zone not a region.

– MisterSmith
Nov 15 '18 at 17:28

Yeah. Got it. Now got the log group. Thank you for your response.

– Karthik
Nov 16 '18 at 9:28

add a comment |

Your Answer

StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53279900%2fcant-get-iis-log-group-in-cloudwatch-log-console-after-creating-association%23new-answer', 'question_page');

);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

Your ID's dont match HttpErr:


 "Id": "HttpErr",
 "FullName": "AWS.EC2.Windows.CloudWatch.CustomLog.CustomLogInputComponent,AWS.EC2.Windows.CloudWatch",
 "Parameters": 
 "LogDirectoryPath": "C:\Windows\System32\LogFiles\HTTPERR",
 "TimestampFormat": "yyyy-MM-dd HH:mm:ss",
 "Encoding": "UTF-8",
 "Filter": "",
 "CultureName": "en-US",
 "TimeZoneKind": "UTC",
 "LineCount": "3"

But in your Flows your using HttpErrLogs

"Flows": 
 "Flows": [
 "IISLogs,IISCloudWatchLogs",
 "HttpErrLogs,HttpCloudWatchLogs"
 ]

answered Nov 14 '18 at 21:52

MisterSmith

948611

Created a new association with definitions as mentioned in the flows in json and restart the SSM Agent. There is no error in the log. But I can't get the log group in CloudWatch log console.

– Karthik
Nov 15 '18 at 13:45

Change "Region": "us-east-1a" to "Region": "us-east-1". us-east-1a is an availability zone not a region.

– MisterSmith
Nov 15 '18 at 17:28

Yeah. Got it. Now got the log group. Thank you for your response.

– Karthik
Nov 16 '18 at 9:28

add a comment |

Your ID's dont match HttpErr:


 "Id": "HttpErr",
 "FullName": "AWS.EC2.Windows.CloudWatch.CustomLog.CustomLogInputComponent,AWS.EC2.Windows.CloudWatch",
 "Parameters": 
 "LogDirectoryPath": "C:\Windows\System32\LogFiles\HTTPERR",
 "TimestampFormat": "yyyy-MM-dd HH:mm:ss",
 "Encoding": "UTF-8",
 "Filter": "",
 "CultureName": "en-US",
 "TimeZoneKind": "UTC",
 "LineCount": "3"

But in your Flows your using HttpErrLogs

"Flows": 
 "Flows": [
 "IISLogs,IISCloudWatchLogs",
 "HttpErrLogs,HttpCloudWatchLogs"
 ]

answered Nov 14 '18 at 21:52

MisterSmith

948611

Created a new association with definitions as mentioned in the flows in json and restart the SSM Agent. There is no error in the log. But I can't get the log group in CloudWatch log console.

– Karthik
Nov 15 '18 at 13:45

Change "Region": "us-east-1a" to "Region": "us-east-1". us-east-1a is an availability zone not a region.

– MisterSmith
Nov 15 '18 at 17:28

Yeah. Got it. Now got the log group. Thank you for your response.

– Karthik
Nov 16 '18 at 9:28

add a comment |

Your ID's dont match HttpErr:


 "Id": "HttpErr",
 "FullName": "AWS.EC2.Windows.CloudWatch.CustomLog.CustomLogInputComponent,AWS.EC2.Windows.CloudWatch",
 "Parameters": 
 "LogDirectoryPath": "C:\Windows\System32\LogFiles\HTTPERR",
 "TimestampFormat": "yyyy-MM-dd HH:mm:ss",
 "Encoding": "UTF-8",
 "Filter": "",
 "CultureName": "en-US",
 "TimeZoneKind": "UTC",
 "LineCount": "3"

But in your Flows your using HttpErrLogs

"Flows": 
 "Flows": [
 "IISLogs,IISCloudWatchLogs",
 "HttpErrLogs,HttpCloudWatchLogs"
 ]

answered Nov 14 '18 at 21:52

MisterSmith

948611

Your ID's dont match HttpErr:


 "Id": "HttpErr",
 "FullName": "AWS.EC2.Windows.CloudWatch.CustomLog.CustomLogInputComponent,AWS.EC2.Windows.CloudWatch",
 "Parameters": 
 "LogDirectoryPath": "C:\Windows\System32\LogFiles\HTTPERR",
 "TimestampFormat": "yyyy-MM-dd HH:mm:ss",
 "Encoding": "UTF-8",
 "Filter": "",
 "CultureName": "en-US",
 "TimeZoneKind": "UTC",
 "LineCount": "3"

But in your Flows your using HttpErrLogs

"Flows": 
 "Flows": [
 "IISLogs,IISCloudWatchLogs",
 "HttpErrLogs,HttpCloudWatchLogs"
 ]

answered Nov 14 '18 at 21:52

MisterSmith

948611

answered Nov 14 '18 at 21:52

MisterSmith

948611

answered Nov 14 '18 at 21:52

MisterSmith

948611

answered Nov 14 '18 at 21:52

MisterSmith

948611

Created a new association with definitions as mentioned in the flows in json and restart the SSM Agent. There is no error in the log. But I can't get the log group in CloudWatch log console.

– Karthik
Nov 15 '18 at 13:45

Change "Region": "us-east-1a" to "Region": "us-east-1". us-east-1a is an availability zone not a region.

– MisterSmith
Nov 15 '18 at 17:28

Yeah. Got it. Now got the log group. Thank you for your response.

– Karthik
Nov 16 '18 at 9:28

add a comment |

Created a new association with definitions as mentioned in the flows in json and restart the SSM Agent. There is no error in the log. But I can't get the log group in CloudWatch log console.

– Karthik
Nov 15 '18 at 13:45

Change "Region": "us-east-1a" to "Region": "us-east-1". us-east-1a is an availability zone not a region.

– MisterSmith
Nov 15 '18 at 17:28

Yeah. Got it. Now got the log group. Thank you for your response.

– Karthik
Nov 16 '18 at 9:28

Created a new association with definitions as mentioned in the flows in json and restart the SSM Agent. There is no error in the log. But I can't get the log group in CloudWatch log console.

– Karthik
Nov 15 '18 at 13:45

Change "Region": "us-east-1a" to "Region": "us-east-1". us-east-1a is an availability zone not a region.

– MisterSmith
Nov 15 '18 at 17:28

Yeah. Got it. Now got the log group. Thank you for your response.

– Karthik
Nov 16 '18 at 9:28

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Odtnhj