Amazon CloudWatch vs GitLab

• 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

• Safeguards implemented are customizable and allow our organization to set our level of verification before merging.
• One of the smoothest and most well-organized version control software products on the market.
• Super widespread use so our use of GitLab is understandable and usable by the customer with little "translation" as to what we are doing and what they are doing.

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

• GitLab could improve some of the confusion around how permissions work (sometimes unclear why one user can do an action, but not another)
• GitLab should provide a way to rerun a merge pipeline, without rerunning the original Merge Request pipeline
• When jobs fail, it would be awesome if every user could see the information on the runner and the versions of the software it is running on (to better debug the issue)

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

• We are moving towards Gitlab only as our SCM & CI tool. So it would be an alternative to Jenkins. Saving our licensing cost there.
• We have also stopped using Confluence & using Gitlab for our documentation purposes. Reducing cost there as well.

Read full review