GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.
N/A
Logz.io
Score 9.0 out of 10
Small Businesses (1-50 employees)
Logz.io in Boston offers their enterprise-grade log analytics application, oriented towards providing data security and eliminating the need for capacity management.
$0.84
per ingested GB 3 day of log retention
Pricing
GoCD
Logz.io
Editions & Modules
No answers on this topic
Log Management - Community
$0
1 day of log retention.
Log Management - Pro
$.92
per ingested GB. 7 days retention.
Distributed Tracing - Pro
$5
Per million spans.
Infrastructure Monitoring - Pro
$12
per month per 1000 time-series metrics.
Log Management - Enterprise
Custom
Cloud SIEM - Enterprise
from $1.49
per ingested GB. Price includes Logz.io Log Management
Previously, our team used Jenkins. However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.
Logz.io is an effective solution if your alerting needs are fairly straightforward and you don't need long-term retention of logs with easy access. If being able to maintain easy access to logs longer than this is necessary, another solution might be better. If you need a high degree of precision with alerting triggers and the ability to suppress alerts, you will need to combine Logz.io with an integration to get this or you might consider a different solution.
Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.
I initially struggled trying to ensure the correct data was returned in the Kibana search, but I found it overall easy to use. Some of the UI is not as seamless as I'd expect, like changing the environment completely resets your search criteria and filters, which is annoying since it's a common use case to search something in multiple environments
Their support team is the best in the world! They supported us in most of the critical times and helped to resolve the issue in real time. Also their email support is well maintained and never a mail is missed unanswered. Kudos to the support team of logz.io for maintaining professionalism.
GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to input the parameters.
Logz.io is more affordable, less work to maintain, and has more features. It was an easy choice. After my last team had to manage their own ELK stack, this was a no brainer. It helps us be focused on our core competencies.
Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date