New Relic is a SaaS-based web and mobile application performance management provider for the cloud and the datacenter. They provide code-level diagnostics for dedicated infrastructures, the cloud, or hybrid environments and real time monitoring.
$0
No credit card required; 100 GB free ingest per month, 1 free full user + unlimited basic users, 8 days retention, 100 Synthetics Checks
ScienceLogic SL1
Score 8.6 out of 10
Enterprise companies (1,001+ employees)
ScienceLogic is a system and application monitoring and performance management platform. ScienceLogic collects and aggregates data across and IT ecosystems and contextualizes it for actionable insights with the SL1 product offering.
$7.50
per month per node
Pricing
New Relic
ScienceLogic SL1
Editions & Modules
Free (Forever)
$0
No credit card required; 100 GB free ingest per month, 1 free full user + unlimited basic users, 8 days retention, 100 Synthetics Checks
Telemetry Data Platform
$0.25
per month per extra GB data ingest (after first free 100GB per month)
Incident Intelligence
$0.50
per month per event (after first 1000 free events per month)
Standard
$99
per month per full user (after first free full user - unlimited free basic users)
Pro
Contact sales team
Enterprise
Contact sales team
No answers on this topic
Offerings
Pricing Offerings
New Relic
ScienceLogic SL1
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Required
Additional Details
—
ScienceLogic SL1 offers four tiers:
SL1 Advanced – Application Health, Automated Troubleshooting and Remediation Workflows
SL1 Base – Infrastructure Monitoring, Topology & Event Correlation
SL1 Premium – AI/ML-driven Analytics, Low-Code Automated Workflow Authoring
SL1 Standard – Infrastructure Monitoring – with Agents, Business Services, Incident Automation, CMDB Synchronization, Behavioral Correlation
To get pricing for each tier, please contact the vendor.
From a monitoring perspective, in my opinion, ScienceLogic SL1 meets if not exceeds in all areas. The two caveats are APM and Network Flow Analytics (NFA) where ScienceLogic SL1 does not have a native capability but does integrate well with the leading APM and NFA providers.
The coverage and ease for what we need is just better. Most of the other solutions are just point tools that don't bring many functions together or are missing pieces to be successful.
Contracting is easy and the cost is really competitive. It helps in tools consolidation and we receive all the benefits. Additionally, we are planning on using it to replace other tools in APM areas if we see good features in upcoming releases. ScienceLogic provides good …
Any web dev would find New Relic useful. The application performance monitoring and transaction tracing tools let you identify the root causes of a slow web site or application and give you the opportunity to fix any bottlenecks. I can't think of a scenario where New Relic is not appropriate - I use it on every web site I develop and manage.
I would have experienced a lot many scenarios and found using Science logic, It makes our life easier to understand everything for the devices that are getting monitored there. we integrated ScienceLogic SL1 to streamline our IT operations. We used its unified monitoring for a clear view of our hybrid IT environment, automating asset discovery which saved significant manual effort. The platform's AI-driven analytics improved our incident response, dependency mapping aided in informed decision-making during migrations, and its capacity planning tools optimized our resource utilization. Overall, SL1 transformed our IT processes, making them more proactive and efficient.
gives us an monitoring of all our underlying servers and also we can configure some alerts upon them like CPU and memory alerts.
Kubernetes cluster monitoring with new relic for EKS gives us and minute details of our cluster utilisation like node usage, pods memory request and limits
Network traceability for each and every request with response time analysis is great we can trace which component is responsible for generating response delay
log managements of the logs the infrastructure is generating we can view logs through there only
I would like to see sort of simulator inside the user interface, that way we can send requests directly from it to test some configuration instead of setting up a test environment in our end.
It would be nice if the data ingestion can be filtered by APM's. That way we can know which application is ingested most data.
It would be nice if we could ingest logs (apache, system logs, and other logs) and correlate them with the APM.
More freedom to create custom dashboards as on the previous versions we could do much more
The Performance TAB windows is too small and cannot be resized or maximized when looking at reports for "Overview", "File System" and any of those items.
There are not enough widgets o create stunning dashboard in AP2
The only issue that we have had with New Relic is that the price might be a little expensive for smaller companies. The amount of data you store in New Relic impacts the cost, and can get away from you if you don't work closely with the vendor. Overall though the application is top notch.
We migrated away from our 20-year-old homegrown solution and have no back-tracking capability. ScienceLogic is demonstrating new capabilities that we would not have been able to do on our own using our legacy system. We understand the capabilities of competitors based on our bake-off selection where ScienceLogic won on capabilities and future near-term potential (expandability, platform growth). We know that those competitors are not really close to where we have been able to push ScienceLogic (as a partner).
As an engineer, New Relic has been very quick and easy for me to pick up/install/use. It has been less easy for some of the less technical-minded folks in our organization and their UI still is inconsistent multiple years after refactoring their platform to be New Relic One.
Product is capable of monitoring different technologies like OS, MS Infra apps, cloud services, Databases, network etc... this can be a single solution for most of the technologies end to end monitoring
It is more flexible for customization and support is good
Science Logic SL1 provides the option of Distributed deployment where multiple instances of each appliance can be deployed to manage the load and availability. SL1 provides a High Availability feature for Database Servers and Data Collection. If one of the Data Collectors in the collector group fails, it will automatically redistribute the devices from the failed Data Collector among the other Data Collectors in the Collector Group. The high availability feature for the Database server ensures that SL1 performs failover automatically to another server without causing the outage to the application.
The performance is entirely dependent on the complexity of the environment/network being used to host the platform. Outside of those factors, the platform runs very efficiently and quickly out of the box. We have integrations with other platforms and neither seem to take a hit from our moderate API usage. Any issues with performance would be experienced by choices made in infrastructure or complexity of things built by the customer to display in the GUI (overly complicated and cluttered dashboards for example)
There are times I feel that the initial support is lacking. And in some cases the automated responses of not hearing anything are annoying if the reason why there has been no movement is because we are still waiting to hear back from NR support. So, i think they should loose the automation as it can seem disingenuous
So far, it's good as part of my overall experience, except for a couple of use cases. The support team is well knowledgeable, has technical sound, and is efficient. When support escalates to engineering, the issue gets stuck and takes months to resolve.
On our side (students), we had a number of teams who were provided the deep developer training. Of those students, the customized training provided a complete, 5 day training which enabled the deployed platform team to successfully deploy and mitigate user-experience issues for the vast majority of our end-users, including some of the teams who attended the developer training.
The knowledge kept pace with the class and sped up / slowed down (within the time constraints) as needed throughout the course.
This was developer to developer training and for those students who were developers the training worked well. For those who were just coders it probably worked less well as some of the topics still do not apply (a function of our course outline specification based on our knowing nothing).
Due to problems in sequencing we did the developer course BEFORE the admin course and realized that our requested ORDER was wrong.
The onsite admin course was much better received and led to deeper understanding of the developer course held a few weeks prior.
The training is excellent and I gained a clear understanding of each module. Most importantly, I could do it at my own pace to make sure that I understood each module. I also had the privilege to test what I have learned in our own test environment before I went on with the next module which gave me much more confidence in what I was doing.
It's better to start by implementing New Relic in one project and test everything. Try to follow best recommended practices and read all the official documentation. Everything seems well tested. Then, start by installing agents to the rest of your projects and keep a close look to all logs and metrics New Relic gives you.
As first time developers, getting to grips with powerpack development using SNMP, Powershell and Python etc, was not helped by poor and badly organised online documentation. In many cases, we had to look at existing powerpacks and try to work out what it was doing and why - not always with much success. Even after receiving expert level training, the development of some powerpacks would not have been possible without access to the SL1 support staff.
Science logic SL1 is so user friendly and it's really easy to navigate between function. I would recommend Sciene logic SL1 to all of them who are looking for really useful monitoring tool and expecting easy way of managing it.
Our deployment model is vastly different from product expectations. Our global / internal monitoring foot print is 8 production stacks in dual data centers with 50% collection capacity allocated to each data center with minimal numbers of collection groups. General Collection is our default collection group. Special Collection is for monitoring our ASA and other hardware that cannot be polled by a large number of IP addresses, so this collection group is usually 2 collectors). Because most of our stacks are in different physical data centers, we cannot use the provided HA solution. We have to use the DR solution (DRBD + CNAMEs). We routinely test power in our data centers (yearly). Because we have to use DR, we have a hand-touch to flip nodes and change the DNS CNAME half of the times when there is an outage (by design). When the outage is planned, we do this ahead of the outage so that we don't care that the Secondary has dropped away from the Primary. Hopefully, we'll be able to find a way to meet our constraints and improve our resiliency and reduce our hand-touch in future releases. For now, this works for us and our complexity. (I hear that the HA option is sweet. I just can't consume that.)