Amazon CloudWatch

We use Amazon Cloudwatch to monitor the health of our infrastructure running on Amazon Web Services (AWS). Particularly the health of EC2 instances and RDS to ensure that our services are performing as expected. The service provides us with visibility and alerting helps us address problems quickly before they have an impact on customers.

• Cloudwatch provides similar functionality to other tools available. However, it is easily available within AWS and can be used with minimal setup.
• It is easy to let costs add up if using multiple custom metrics or more detailed metrics and retentions than necessary; we ensure that we retain the data in Cloudwatch for the minimum amount of time to be of value for Ops monitoring and then move to other tools such as Splunk for longer retention.
• Alerting within Cloudwatch allows us to react quickly when thresholds are unmet or exceeded.

Splunk IT Essentials, Splunk Cloud, Splunk IT Service Intelligence (ITSI) and Splunk On-Call

Splunk Cloud, Splunk Synthetic Monitoring, Splunk IT Service Intelligence (ITSI)

If you use any AWS service, CloudWatch is a must-have. Imagine having multiple services deployed & running on AWS. The services work interdependently. CloudWatch allows viewing logs of all those services in a central place. With CloudWatch Log Insights, you can make custom queries for your log across multiple streams. If you set up AWS Organizations, CloudWatch can help centralize logs from all accounts.

• We can trace errors, exceptions much easier, hence problems are resolved very quickly.
• We can trace errors and exceptions across multiple services, which helps to pin down the issue.
• Logs are collected & available for view with minimal delay, tightening the feedback loop.

AWS CloudFormation, AWS Certificate Manager, AWS CodeArtifact

We majorly use Amazon CloudWatch to track and get alerts on the metrics of RDS, Elasticache and other services of AWS in use. We do have it for logging Lamda runs in some cases, but not a significant requirement for us, as we use lambda with minimal logic and nothing complicated at all

• Helps in real-time alerting esp. for RDS and Elasticache which are critical resources
• Periodic analysis of metrics using dashboards makes it easier to monitor system's availability

Grafana, VictoriaMetrics Community, Prometheus and Elasticsearch

Amazon Cloud watch is primarily used for watching all the requests coming into any of the AWS services our organization is using. It can tracks all the requests, with the IP address and can help in monitoring the requests/ sec. Also helps to filter what requests need to be searched based on different criteria like Access Key, and IP address.

• Storing, archiving, filtering the logs so that we can focus on our business needs.
• Simplified access to lengthy log files and can view history of data.
• Simplified collaboration around log files.

• It is a monitoring and observability service built for DevOps engineers, developers, site reliability engineers (SREs), and IT managers.
• It provides you with data and actionable insights to monitor your applications, respond to system-wide performance changes, and optimize resource utilization.
• It can be used to detect anomalous behavior in your environments, set alarms, and visualize logs and metrics side by side.

Datadog

Datadog, Splunk Log Observer

• Trends and metric graphic, exports for reports.
• Alarms for critical alerting of any resources.
• Billing and cost alarms without using budgets to manage cost changes.

• Positive for alarms and alert notifications once configured/customized.
• Has upfront learning curve, and cost can increase as does the alarm activity and monitoring details you may require.
• Cost-effective for any size organization keeping with AWS and utilizing its native tools is a savings in long-term ROI.

SolarWinds Network Performance Monitor (NPM) and Zoho IT Management

SolarWinds Engineer's Toolset, Site24x7 CloudSpend, Sophos Cloud Optix