Amazon CloudWatch vs Micro Focus SiteScope

• It provides lot many out of the box dashboard to observe the health and usage of your cloud deployments. Few examples are CPU usage, Disk read/write, Network in/out etc.
• It is possible to stream CloudWatch log data to Amazon Elasticsearch to process them almost real time.
• If you have setup your code pipeline and wants to see the status, CloudWatch really helps. It can trigger lambda function when certain cloudWatch event happens and lambda can store the data to S3 or Athena which Quicksight can represent.

Read full review

• Alerts can be configured as per business requirement.
• It can take remedial action, when defined for a particular situation.
• Severity, priority of tickets which are created upon a trigger can be well defined.
• The teams which need to be alerted can be configured in the tool itself, in case of any event.

Read full review

• Memory metrics on EC2 are not available on CloudWatch. Depending on workloads if we need visibility on memory metrics we use Solarwinds Orion with the agent installed. For scalable workloads, this involves customization of images being used.
• Visualization out of the box. But this can easily be addressed with other solutions such as Grafana.
• By design, this is only used for AWS workloads so depending on your environment cannot be used as an all in one solution for your monitoring.

Read full review

• Sitescope is particularly used for infrastructure monitoring. Other kinds of monitors cannot be set using HP sitescope.
• Sitescope cannot have graphs like splunk which is why we have splunk as well which is an additional cost for the company.
• We can't have a direct regex operations on data inside HP sitescope. We need to have the logs placed as a single log and then do that.

Read full review

• We were able to set up log streaming, retention, and simple downtime alerts within a few hours, having no prior experience with CloudWatch, freeing up our engineers to focus on more important business goals.
• CloudWatch log groups have made it relatively easy to detect and diagnose issues in production by allowing us to aggregate logs across servers, correlate failures, isolate misbehaving servers, etc. Thanks to CloudWatch, we are generally able to identify, understand and mitigate most production fires within 10-15 minutes.
• Choosing CloudWatch to manage log aggregation has saved us quite a bit of time and money over the past year. Generally, 3rd-party log aggregation solutions tend to get quite expensive unless you self-host, in which case you typically need to spend a fair amount of time setting up, maintaining, and monitoring these services.

Read full review

• Sitescope does exactly what it was purchased for. It may take some time to set it up but once its set up it is a rock solid product.

Read full review