Dynatrace is an APM scaled for enterprises with cloud, on-premise, and hybrid application and SaaS monitoring. Dynatrace uses AI-supported algorithms to provide continual APM self-learning and predictive alerts for proactive issue resolution.
$0
per synthetic request
GitLab
Score 8.7 out of 10
N/A
GitLab DevSecOps platform enables software innovation by aiming to empower development, security, and operations teams to build better software, faster. With GitLab, teams can create, deliver, and manage code quickly and continuously instead of managing disparate tools and scripts. GitLab helps teams across the complete DevSecOps lifecycle, from developing, securing, and deploying software. Differentiators, as described by Gitlab:
Simplicity: With GitLab, DevSecOps can…
$0
per month per user
Pricing
Dynatrace
GitLab
Editions & Modules
Synthetic Monitoring
$0.001
per synthetic request
Kubernetes Platform Monitoring
$0.002
per hour for any size pod
Real User Monitoring
$0.00225
per session
Application Security
$0.018
per hour for 8 GIB host
Infrastructure Monitoring
$0.04
per hour for any size host
Full-Stack Monitoring
$0.08
per hour for 8 GIB host
GitLab Essential
$0
per month per user
GitLab Premium
$29
per month per user
GitLab Ultimate
$99
per month per user
Offerings
Pricing Offerings
Dynatrace
GitLab
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
Dynatrace
GitLab
Considered Both Products
Dynatrace
Verified User
Anonymous
Chose Dynatrace
Single Agent deployment AI analysis that provides insight discovery and pure path Able to analyst performance data quickly and next hop.
New relic was mostly like readonly dashboard and restricted how we slice and dice the data presented to us. Ability to drill down was seriously limited.
Dynatrace UI seems better compared to splunk also DT gives better flexibility in terms of plans and costs. For logging monitoring we are using splunk and splunk is better for that purpose. But hosts and server monitoring and alerting perspective Dynatrace is better. Dynatrace …
Dynatrace gives the overall picture of the application usage and performance by default with minimal configurations whereas in Datadog a lot of manual intervention is required to analyze the application performance and troubleshooting the issues. Dynatrace is user-friendly when …
Dynatrace has three key points: ease of deployment, ease of access and a very low learning curve. Also the info provided by the DT agents are easy to understand and relate to root cause. Also the user interface is very simple and can be configured/shared to provide the data to …
We selected Dynatrace because it is much more modern and depends on AI, on auto-discovery, and other features, making it really a next-gen monitoring solution. It is not easy to on-board to Dynatrace, as it has an extremely steep learning curve. It is also possible that other …
Some of these tools we use alongside Dynatrace, and others we chose Dynatrace over. Since Ruby is not a Dynatrace supported language, we use New Relic to monitor those applications. We are an AWS shop so naturally, we use CloudWatch metrics for things like auto-scaling where it …
I have used a plethora of Application Performance Management (APM) tools, all have their niche. Dynatrace provides the best-in-class experience for support, operations, and platform engineering teams. In addition, access for my Enterprise Development teams has been critical. …
BMC was only a basic APM with not much detail or drilling into the issue. It only showed there was a problem with the host. Before Dynatrace, to troubleshoot an issue we had to log into different consoles for different applications and review logs. Now with a quick visual and a …
The Dynatrace product was much more feature-rich than New Relic. We went through multiple proofs of concepts with each vendor using our actual system. We found that both did some things the same but in other areas, the Dynatrace product was much better. There was a black box …
Dynatrace is much more expensive than Pingdom, but it does a better job of doing synthetic monitors and the credential store is much better. When it comes to availability it does a better job of creating of synthetic monitors and it can create a credential store which is a big …
I have not evaluated any other monitoring products. Our company has evaluated other products that have not stacked up against Dynatrace. Dynatrace has deeper monitoring than others and provides excellent alerting capabilities. Dynatrace was selected for those features as well …
Dynatrace provides the best insights into our environment from end to end. It provides user sessions throughout the application so, we can see exactly what users are doing and potentially not only fix problems but provide improvements before any issues arise. There is no …
As mentioned earlier, the features like chart visualization sets it apart from the others. Other than that, GitLab is open source while other are not and comparatively more secure that its other counterparts. Also, GitLab supports adding other types of attachments which is not …
When i was using the other platform, Some time i face down time, But GitLabs its not happening for single time. GitLab is having easy user interference as compared to other platforms. Pull Request, Code review, Issue tracking, Merging, Access control and User Roles is having a …
GitLab is miles ahead of the competition. In so many words, having a simple UI with robust security and the ability to conduct Git actions takes the cake. The competitions like to say they can do these things easily but their products are more confusing and hard to use.
GitLab allows a self-hosted version that is easy to setup and configure. It is also open-source as compared to GitHub. The integrated CI/CD tools is a plus, since we do not have to worry about those tools, unlike Github. The All-in-one solution of GitLab made sense for our …
Gitlab offers the best support for CI/CD pipelines and the highest degree of customisation for workflows, permissions, and integrations. The integration of BitBucket with JIRA is better than GitLab but CI/CD features are limited in comparison. GitLab's built-in Container …
Gitlab provides basic functionality like any other git tool. Some features of push and pull requests , clone and merge is handled equally well. It lacks in AI features which are there in GitHub and setup processes are difficult. Cost difference is the only concern while …
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution.
GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" …
It's much simpler than the competitors. The one important feature Gitlab stand out is the CI/CD pipeline. GitHub required integration with external CI tools but Gitlab has this feature built-in. Compare to Jenkins and Teamcity, It's easy to use without any additional Plugins. …
Gitlab seems more cutting-edge than GitHub; however, its AI tools are not yet as mature as those of CoPilot. It feels like the next-generation product, so as we selected a tool for our startup, we decided to invest in the disruptor in the space. While there are fewer …
i have more exoerence in GitLab rather than bitbucket . As personally , it is good for me to understand how things is going on. i have used personally and also in organisation . It is great for developer to see there 3 months ago code and also can come up with new solution to …
Because with Visual Studio code, it was very easy for us to install GitLab in it and have easy access through the terminal and due to GitLab, it was easy to implement codes regarding API and AWS services to make our software better. Gitlens and all features help to check the …
GitLab provides a far superior platform due to it's great integration and CI/CD focus. And while in the beginning the UI might look a bit overwhelming with use you will find it way more useful than it's competitors. The variables and settings also make way more sense and it's …
My feedback may not be important here because when I joined the company they already had GitLab and we still use it due to the ability to do CI/CD Integration, deployments, debugging, code owners approval, and Jira integration. So far we have not had any major blocker that has …
Github is more open-source first and enterprise-first second in their approach. The reverse is true for GitLab. Both are exceptional products and it highly depends on the specific needs of an org
GitLab has a open-source community and great documentation that provides support resources and community contributions. AWS CodeCommit is used for integration with other AWS services in the AWS ecosystem and also have a low community and support compared to GitLab hence …
It was a management decision to use GitLab over other tools. It integrates well with RBAC using Terraform. Runners are easy to setup. Almost all the features the organization used before are available in GitLab.
For small projects or companies that do work on a few only code repositories selecting one of the git code hosting services like GitLab, GitHub, Bitbicket etc does not make a big difference.
But, if you are on a code development company that handles too many repositories and …
Software delivery is the key objective and GitLab made it much easier to hit the group quickly. It worked well with automation, and integrations with other SDLC tools used in the Organization and it is really easy to use. It's widely adopted and has the power to deliver what we …
GitLab's online IDE and code modification is much better compared to Stash. While pricier than Bitbucket, Gitlab also provides CI CD configuration better than BB.
Dynatrace is well suited to a number of tasks. It is important to determine who the end users are and gather good information to tailor their experience accordingly. For instance, business/marketing should not have access to some of the more technical data, and business metrics can be a distraction for IT operations personnel.
It is well-suited for any project that needs VCS. It's an excellent choice for teams that might be remote or have to collaborate across teams. Plenty of features allow for async working. With its dashboards and reporting features, it is also suitable for nontechnical PMs or stakeholders. It allows for very bespoke customization and can most often do much more than you need it to.
We loved Dynatrace's ability to show the data flow - from the front end points through the back end points straight to the database and various API's. It was advanced in its data visualization. This is useful for debugging - showing when/where the errors are. It can even enable non-technical individuals in the corporation to help debug
Dynatrace has some great highly customizable integration options as well as monitoring. You can configure your layout & integration options to create custom monitoring alerts for your applications performance. Further you can increase the extensibility of using a REST API on your architecture.
Some advanced dev-ops systems are utilizing Kubernetes/docker aswell as Node.JS - Dynatrace was able to log and help understand all of our dev-ops needs. It gave us native alerts based off of deviations from the baseline that we set during initial configuration. These metrics are priceless.
Dynatrace does not monitor easily on a C-based application.
The way DPGR is addressed by Dynatrace is not very complete, and not clear. One thing is to mask the IP and request attributes but is not enough, the replay session feature is great but raises serious questions about user tracking.
We have got tremendous support and response from the dynatrace support team as well as the larger community. We still have issues like the lack of role based administration, but we are told that it may be coming in a future release. The team is very supportive and has assisted us in several tough situations.
I really feel the platform has matured quite faster than others, and it is always at the top of its game compared to the different vendors like GitHub, Azure pipelines, CircleCI, Travis, Jenkins. Since it provides, agents, CI/CD, repository hosting, Secrets management, user management, and Single Sign on; among other features
Dynatrace is great to use once you understand how to use it correctly and get used to the layout of it. While I do not actively use it every day, whenever I do use it, I do have to get refamiliarized with it. However, once you have your dashboards setup correctly with the data that you want to see when you first login to Dynatrace, it's amazing.
I find it easy to use, I haven't had to do the integration work, so that's why it is a 9/10, cause I can't speak to how easy that part was or the initial set up, but day to day use is great!
I've never had experienced outages from GItlab itself, but regarding the code I have deployed to Gitlab, the history helps a lot to trace the cause of the issue or performing a rollback to go back to a working version
GItlab reponsiveness is amazing, has never left me IDLE. I've never had issues even with complex projects. I have not experienced any issues when integrating it with agents for example or SSO
I wish I could have given the ten points but based on my experience in past I am reducing by two points as the penalty. But I am sure that it will have improved in the past few months. They need some improvement on ticket handling. Overall I appreciate some of the support folks who responded quickly and also were ready to jump on the Webex and get the problem understood to fix it.
At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when GitHub was acquired by Microsoft
Like I mentioned earlier, Dynatrace is a great tool but comes with a heavy price tag. On the other hand, Foglight offers a slightly lower level of expertise in application monitoring but fulfils almost all the requirements you would commonly have. The only major feature lacking in Foglight is the predictive monitoring feature. If you are an SME struggling with budgets, then predictive monitoring is something you can certainly live without.
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution. GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" in GitLab while you have to do clickops in GitHub to achieve the same. No overview of code in branches is a minus when we tried to figure out what our colleagues are trying to merge as it looked off.