This is a great question! I'd go with options A and D. Using CloudWatch Logs seems like the most straightforward way to get the operating system and application logs in a single place. The CloudWatch Logs agent makes it easy to set up.
I'm leaning towards options A and C. Sending the logs to Kinesis and then inserting them into CloudSearch or Redshift could provide more flexibility for analysis down the line. But I'd need to do some more research on the pros and cons of each approach.
I think the key here is to use a combination of AWS services to achieve the desired outcome. Options A and D look like the best fit, as they allow us to centralize the logs in a single place using CloudWatch Logs.
Hmm, I'm a bit confused about the difference between using CloudWatch Logs and Kinesis/Redshift. Option C seems interesting, but I'm not sure if that's the most efficient approach for this use case.
This seems like a straightforward question. I'd go with options A and D - using CloudWatch Logs to centralize the logs from both the operating system and the applications.
I feel pretty confident about this one. Checking the recommended software release, known issues, and running the necessary checks should cover the bases before applying any updates.
I'm confident the answer is C. The customer needs to modify hypervisor networking, and HPE OneView for VMware vCenter Server is designed to enable host profile functionality and simplify those types of changes.
D) Using AWS CloudFormation, create a CloudWatch Logs LogGroup. Because the CloudWatch log agent automatically sends all operating system logs, you only have to configure the application logs for sending off-machine
A) Using AWS CloudFormation, create a CloudWatch Logs LogGroup and send the operating system and application logs of interest using the CloudWatch Logs Agent
D) Using AWS CloudFormation, create a CloudWatch Logs LogGroup. Because the CloudWatch log agent automatically sends all operating system logs, you only have to configure the application logs for sending off-machine
A) Using AWS CloudFormation, create a CloudWatch Logs LogGroup and send the operating system and application logs of interest using the CloudWatch Logs Agent
That's a good point, but I still think having the flexibility to send events to Amazon Kinesis and insert them into Amazon CloudSearch or Redshift with option C could provide more analytic tools for our teams.
The CloudWatch Logs solution in option A seems like the most straightforward way to consolidate the logs. Sending the logs to a single LogGroup makes sense.
I disagree, I believe option D is more efficient as it automatically sends all operating system logs and only requires configuration for application logs.
I think option A is the best choice because it allows us to send both operating system and application logs to a single place using CloudWatch Logs Agent.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Chana
3 months agoTiara
3 months agoMarci
3 months agoFelice
4 months agoLavina
4 months agoLuisa
4 months agoMohammad
4 months agoSuzan
4 months agoAlida
5 months agoRosina
5 months agoLinn
5 months agoNatalie
5 months agoMichell
5 months agoBuck
5 months agoAdell
5 months agoBernardine
5 months agoBeata
5 months agoLatanya
9 months agoRoosevelt
9 months agoAbraham
9 months agoMicaela
8 months agoWynell
8 months agoKing
8 months agoRessie
8 months agoBillye
9 months agoTori
8 months agoDalene
8 months agoHui
9 months agoSherell
10 months agoMonroe
9 months agoTruman
9 months agoAlecia
9 months agoArlene
10 months agoKati
10 months agoDaisy
10 months agoShaniqua
10 months agoFreeman
11 months agoFelix
9 months agoWillard
9 months agoMeaghan
9 months agoAnnice
9 months agoCarol
11 months agoShaniqua
11 months ago