We wanted to have a tool that has both APM and error monitoring stuff included in one.
I preferred to go to New Relic as the free version offers 100gb storage but have seen some "not good" comments about it compared to Datadog.
My teammates suggested AppSignal.
So which one should be a good option to give a try?
Tech Stach -> Ruby on Rails, Rails-react, Amazon EC2 machine.
Via acquisitions and internal product developments over the last year+, Splunk provides really differentiated APM and monitoring for microservices and AWS. I'd recommend giving it a peak if you haven't yet! For some validation, a recent Cloud Observability vendor report by GigaOm came out and ranked Splunk as the "top performer" in the space. Hope this helps in your search
Maurice - Datadog allows you to monitor microservices by unifying metrics, traces, and logs all in one place. Enabling you to visualize how services interact at a glance so you can quickly locate problems and begin troubleshooting. On top of that you can monitor complex dependencies, investigate possible points of failure, and set smart alerts for proactive monitoring. In my opinion Datadog offers the most comprehensive tool with the simplest UI.
Coming from a Ruby background, we've been users of New Relic for quite some time. When we adopted Elixir, the New Relic integration was young and missing essential features, so we gave AppSignal a try. It worked for quite some time, we even implemented a :telemetry reporter for AppSignal . But it was difficult to correlate data in two monitoring solutions, New Relic was undergoing a UI overhaul which made it difficult to use, and AppSignal was missing the flexibility we needed. We had some fans of Datadog, so we gave it a try and it worked out perfectly. Datadog works great with Ruby , Elixir , JavaScript , and has powerful features our engineers love to use (notebooks, dashboards, very flexible alerting). Cherry on top - thanks to the Datadog Terraform provider everything is written as code, allowing us to collaborate on our Datadog setup.
Hey there! We are looking at Datadog, Dynatrace, AppDynamics, and New Relic as options for our web application monitoring.
Current Environment: .NET Core Web app hosted on Microsoft IIS
Future Environment: Web app will be hosted on Microsoft Azure
Tech Stacks: IIS, RabbitMQ, Redis, Microsoft SQL Server
Requirement: Infra Monitoring, APM, Real - User Monitoring (User activity monitoring i.e., time spent on a page, most active page, etc.), Service Tracing, Root Cause Analysis, and Centralized Log Management.
Please advise on the above. Thanks!
I'm building, from scratch, a webapp. It's going to be a dashboard to check on our apps in New Relic and update the Apdex from the webapp. I have just chosen Next.js as our framework because we use React already, and after going through the tutorial, I just loved the latest changes they have implemented.
But we have to decide on a CSS framework for the UI. I'm partial to Bulma because I love that it's all about CSS (and you can use SCSS from the start), that it's rather lightweight and that it doesn't come with JavaScript clutter. One of the things I hate about Bootstrap is that you depend on jQuery to use the JavaScript part. My boss loves UIkIt, but when I've used it in the past, I didn't like it.
What do you think we should use? Maybe you have another suggestion?
I have used bulma in several projects. We could not customize with the websites very well. Also when we need "quick solutions" Bulma is not suitable (I mean basic animations, to-top buttons, transparent navbar solutions etc. For these solutions, you need extra js codes).
Everybody knows about Bootstrap (heavy but popular).
Now we start a new project with UI kit, I like it. Pros: It is fast and lightweight and imho it has very good UI. Cons: Small community. Documentation.
Check this link for kick-off. https://github.com/zzseba78/Kick-Off
Maybe it is helpful.
Been checking out Bulma, myself, and really dig it. I like that it's a great base level jumping off point. You can get a layout going with it, pretty quickly, and then customize as you want. It definitely sounds like it's the one you're leaning towards but a big factor would be who will be using it most? Your boss, yourself, others? Whichever you like best, you'll prob be most productive with but if in the end your boss says it has to be UIkit, then best to be open-minded and give it another shot. Sometimes you may not jive with new tools in your stack, at first, but then they can become tools you learn to love. Best to you in your decision! Take care & keep safe.
Hi Folks,
I am trying to evaluate Site24x7 against AppDynamics, Dynatrace, and New Relic. Has anyone used Site24X7? If so, what are your opinions on the tool? I know that the license costs are very low compared to other tools in the market. Other than that, are there any major issues anyone has encountered using the tool itself?
I am looking for network and .NET application monitoring.
gotcha. Instana can help with .net but not with Network. happy to chat more if you want. just let me know. otherwise good luck in your search. i know some of the other APM tools you mentioned do Network ;) cheers
I need to choose a monitoring tool for my project, but currently, my application doesn't have much load or many users. My application is not generating GBs of data. We don't want to send the user information to New Relic because it's a 3rd party tool. And we can deploy Kibana locally on our server. What should I use, Kibana or New Relic?
Kibana and ELK stack is way far better in enterprise solution. But if you are going to deploy something smal, it does't worth the configuration and maintenance of the ELK stack. You'll have lots of challenges every day. If you have a small team, I do not recommend on-promiss ELK. You can also consider ELK hosted services which are very easier to use, like logz.io
New Relic's value to me is the ability to see how end users perceive the application. Kibana is going to be limited to what is sent to it. The value to larger companies is paying New Relic to package up knowledge on what are typical trigger values. If you your scope is small, not a global website for example, and your key outage risks are local events then Kibana would be a low cost solution but you may be the sole provider of configuration logic.
