Über Amazon CloudWatch

Observability of your AWS resources and applications on AWS and on-premises

Erfahre mehr über Amazon CloudWatch

Vorteile:

Nicht verfügbar

Nachteile:

Nicht verfügbar

Bewertungen zu Amazon CloudWatch

Durchschnittliche Bewertung

Benutzerfreundlichkeit
4,2
Kundenservice
4,0
Funktionen
4,3
Preis-Leistungs-Verhältnis
5,0

Weiterempfehlungsquote

9/10

Amazon CloudWatch hat eine Gesamtbewertung von 4,5 von 5 Sternen basierend auf 6 Nutzerbewertungen auf Capterra.

Nutzerbewertungen filtern (6)

Produktbewertung

Produktbewertung

Sortieren nach

Hast du Amazon CloudWatch bereits verwendet?

Teile deine Erfahrungen mit anderen Softwareinteressenten.

Nutzerbewertungen filtern (6)

Verifizierter Rezensent
Director, Internet Strategy in USA
Verifizierter Nutzer auf LinkedIn
Verlagswesen, 51-200 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

CloudWatch brings visibility to your AWS stack

5 vor 4 Wochen Neu

Kommentare: You don't have to use AWS for very long to have this happen: you've got instances and tasks and containers and all kinds of "machines", whether physical or virtual, running all over the place, and you want to figure out how to see what's going on internally with one of them. Maybe you just want a quick look at the Apache logs. In the "good old days" you'd just SSH into the instance. But with Docker and virtualization and everything, that's not so easily said and done anymore. Enter CloudWatch.
Think of it as a centralized logging store. When you start up containers and instances and tasks and such, you can ask AWS to automatically have whatever you are spinning up log its internals to CloudWatch. You can then jump into CW anytime you need to take a look at what's happening inside that box. Need Apache logs? They're right there. Even better, they are searchable using a good (but not great) interface. Also, CW will bring together the logs from separate ECS tasks into one log group, if you want. So if you have a handful of tasks running, you can search across all of them in one go and find the misbehaving one much more easily than SSH'ing into 6 instances trying to locate the culprit.
Extra bonus: with just a teeny bit of coding on your end you can actually have your application log items to CW directly. Use Lambda to monitor it, and push that to Slack, and you've got custom monitoring, built into your AWS stacks. CW is critical to doing AWS right.

Vorteile:

* One-stop shopping for visibility on all your instances (and tasks and sub-instances and whatever else that AWS makes it so easy to spin up but then so hard to keep track of later) * Easy to hook into Lambda (which can then call to Slack or some other service) so that you can get push notifications about whatever's happening

Nachteile:

* The search facility is not as good as it probably could be. If you have a line of output from a log, for instance, and you want to see where that line of output came from, and you do not know which log group it's from, you are out of luck. You can only search inside a log or log group, which means you have to know where the output came from to start with, but that might be exactly the issue you're trying to figure out in the first place: where is this output coming from. * AWS instances and tasks automatically start up with CW integration but that can quickly result in loads of orphaned CW log groups and such if you then do away with the instances but don't remember to go into CW and kill those as well.

Omer I.
Omer I.
Software Engineer in Japan
Verifizierter Nutzer auf LinkedIn
Informationstechnologie & -dienste, Selbstständig
Verwendete die Software für: Mehr als 1 Jahr
Herkunft der Bewertung
Quelle: GetApp

In Betracht gezogene Alternativen:

CloudWatch gives x-ray vision of AWS resource

4 letzten Monat Neu

Kommentare: Using CloudWatch is an indispensable tool to keep track of our logs, metrics, events, alerts, etc. We use its metrics to alert us when something is not right in our infrastructure. We also keep track of application logs coming from different resources to simplify finding and resolving bugs. We also use it to automate tasks we need to run at scheduled times.

Vorteile:

It is easy-to-use monitoring and observability service that readily works with AWS services.

Nachteile:

Accessing and searching log data can get more difficult as you start to have more log data and when logging data from multiple AWS resources if you don't use Log Insights.

Kevin B.
Software Engineer in USA
Finanzdienstleistungen, 1.001-5.000 Mitarbeiter
Verwendete die Software für: Mehr als 1 Jahr
Herkunft der Bewertung

Great Product and easy Laravel integration

4 vor 2 Monaten Neu

Kommentare: I have been pleased with Amazon Cloudwatch. It is used so widely that there is a large community of support around it. While I don't know that it is necessarily better than the alternatives, it is certainly easier in the case of those already using AWS

Vorteile:

Being part of AWS, its very easy to start using and will be cheaper than most options. There are easy Laravel packages for integrating use, and it is simple to allow options for logging groups.

Nachteile:

I only have two slight complaints with Cloudwatch. First, I wish querying multiple log groups was a little more intuitive. Second, the lack of creating nested log groups isn't great. Having many different environments throughout my development team, it is a bit annoying to have hundreds of log groups, even though splitting up the logs does help us immensely.

Darian P.
Darian P.
Team Lead of Internal Tools in USA
Verifizierter Nutzer auf LinkedIn
Versicherung, 201-500 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Review of Amazon Cloudwatch

4 vor 8 Monaten

Kommentare: Cloudwatch is used best when it is used with all the other AWS services. I wouldn't really say you use Cloudwatch by itself, it's always to check or report on another service. With that said, Cloudwatch really excels at monitoring once you put in the time to setup metrics. Otherwise, you sit on a wealth of potential data that ends up not being used.

Vorteile:

Cloudwatch is best used when we try to identify/debug our code. We check logs for our cloud functions through cloudwatch and due to it being realtime it allows us to quickly diagnose any issues. By making our functions verbose, our logs become clear to sort through as well. Cloudwatch also allows us to monitor our servers load. We have some automations to post on our channels when certain servers have too much load, low memory, or when too many error events have occurred in a short period. This has allowed us to resolve issues as fast as possible.

Nachteile:

I think the slowness can sometimes be a limiting factor. Opening several pages of logs at the same time will slow down the system. This happens to me because I usually am trying to find specific text that was output, but there is no search for data within the log files, just for the filenames of the log files (which in my case is not helpful).

Verifizierter Rezensent
Industry Principal Consultant in Kanada
Verifizierter Nutzer auf LinkedIn
Informationstechnologie & -dienste, 10.000+ Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Monitoring tool for all your critical AWS services

5 vor 3 Monaten

Kommentare: I am very pleased with the capabilities of AWS cloudwatch and would highly recommend it to all AWS customers

Vorteile:

Event threshold, automated monitoring, email notifications, coverage for most of the critical AWS services.

Nachteile:

Capability to use it for on-prem and other cloud services would be a great addition and make it a single source of truth.

Verifizierter Rezensent
Dispute Resolution Specialist in Kanada
Verifizierter Nutzer auf LinkedIn
Bankwesen, 10.000+ Mitarbeiter
Verwendete die Software für: 6-12 Monate
Herkunft der Bewertung

Must have for your cloud infrastructure and application management

5 vor 3 Monaten

Kommentare: Overall we are very happy with the cloudwatch monitoring tool and use it on daily basis to keep a check on our cloud infrastructure and applications.

Vorteile:

Cloud computing monitoring, automated events management, Threshold violation monitor, proactive monitoring, email notifications

Nachteile:

Supports most of the AWS services but missing a few newer services. Also we cannot monitor our on-premise HW with this.