What users are saying about
69 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
175 Ratings
69 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.3 out of 100

ScienceLogic SL1

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
175 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8 out of 100

Likelihood to Recommend

AppDynamics

As it pertains to monitoring database transactions, as our application relies heavily on SQL, AppDynamic's monitoring tool made an immediate impact on sorting which ones are slow. The business transactions that we can capture are limited in the sense that our application works where it can't be limited to 200, so we ended having to setup service endpoints to account for it.
No photo available

ScienceLogic SL1

Basic server monitoring is an easy win for the platform. Powerpacks make it easy to monitor different platforms with events predefined and included. However, the system does not do well with near real-time polling. For instance, if you were monitoring uplinks on switches, you'd be best to poll at 5 minutes or more. The system would struggle if you try to monitor every minute.
No photo available

Feature Rating Comparison

Application Performance Management

AppDynamics
8.6
ScienceLogic SL1
Application monitoring
AppDynamics
9.0
ScienceLogic SL1
Database monitoring
AppDynamics
8.9
ScienceLogic SL1
Threshold alerts
AppDynamics
9.2
ScienceLogic SL1
Predictive capabilities
AppDynamics
7.2
ScienceLogic SL1
Application performance management console
AppDynamics
8.9
ScienceLogic SL1
Collaboration tools
AppDynamics
8.3
ScienceLogic SL1

Pros

AppDynamics

  • Giving a network map of our application that shows where slowdowns are occurring and where network traffic is running into a bottleneck.
  • We are able to gather node-specific information that shows the number of sessions a web server or even Redis session statistics.
  • We use AppDynamics to give a holistic view of our application allowing us to quickly narrow in on problems.
Tyler Twitchell profile photo

ScienceLogic SL1

  • Graphing - Sciencelogic has highly configurable, high-quality graphs that make the display of mission-critical data very effective.
  • Customization - With a few exceptions, nearly everything in the system can be changed, modified, added or deleted to create your ideal monitoring environment.
  • "Power Packs" - The built-in packages provide a good level of out of the box functionality.
Britton Starr profile photo

Cons

AppDynamics

  • Price of the AppDynamics is high. But it has many valuable features. This makes it difficult for small businesses to enter.
  • Functionality is overkill for most small to midsize businesses (SMBs). When stacking up product units, it can get pricey for enterprises as well.
  • With fine granular configs and customizations available, it will also mean that it is very complicated and requires a certain amount of knowledge before we can make full use of all features in the product. Much careful thought and planning is required to get the most of it. Set-up will be longer. One recommendation is for features to be better documented.
No photo available

ScienceLogic SL1

  • The point in time nature of the data points can be misleading. The data would be more valuable in some cases if the 5 minute polling interval was an average value of the previous 5 minutes, not point in time when the collection happens.
  • Container and Kubernetes monitoring is poor. Granted we are a few months behind of upgrades, so haven't been able to try out the latest versions.
  • Snippet development within the platform is terrible. There really needs to be a way to source snippets from Git repositories, so code can be versioned and tested outside of the platform.
  • Testing snippets outside of the platform can be challenging. We would really like to have some mock test framework we could pull into our testing suite so unit testing complex snippets is easier.
David Louks profile photo

Likelihood to Renew

AppDynamics

No score
No answers yet
We are a reseller of appdynamics
No photo available

ScienceLogic SL1

ScienceLogic SL1 7.9
Based on 5 answers
We migrated away from our 20-year-old homegrown solution and have no back-tracking capability.
ScienceLogic is a Cisco Partner and we are supported in ensuring their success.
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).
John &quot;Frotz&quot; Fa'atuai profile photo

Usability

AppDynamics

No score
No answers yet
No answers on this topic

ScienceLogic SL1

ScienceLogic SL1 7.0
Based on 3 answers
The core functions are there.
The complexity is due to the complexity of the space.
The score is based on comfort (I no longer notice the legacy UI) and the promise that I see in the 8.12 Unified UI (a vast improvement).
It is also based on the fact that with 8.12, you can now do everything in the new UI but you still have the legacy UI as a fallback (which should now be unnecessary for new installations).
Further, the score is influenced by ScienceLogic being a Cisco Partner and while Cisco IT is a customer, we are also executing on internal expectations to make our partners successful by constructive (and sometimes pressured) criticism to better the platform.
John &quot;Frotz&quot; Fa'atuai profile photo

Reliability and Availability

AppDynamics

No score
No answers yet
No answers on this topic

ScienceLogic SL1

ScienceLogic SL1 7.3
Based on 1 answer
For us, monitoring needs to degrade gracefully. That means that, by design, you allow your monitoring system to begin giving you less and less information until an ultimate failure point. Our motto is Last-Down / First-Up and our deployment architecture reflects specific design choices to minimize being part of someone else's failure-mode.ScienceLogic SL1 at 8.12 provides a wealth of monitoring data. This comes at a cost as you scale up.Can you consume the wealth of monitoring data?Can you consume the wealth of warnings and errors that being to get generated as you scale up?There are challenges, most of which are due to our deployment design choices and scale.We are working with ScienceLogic to introduce Priority as a first-class data element. We've added this as a Custom Attribute for all of our CIs. We use this to distinguish between the failure of a development host vs the failure of our production website.The score represents the known opportunity for improvement that we see on our joint roadmaps.
John &quot;Frotz&quot; Fa'atuai profile photo

Performance

AppDynamics

No score
No answers yet
No answers on this topic

ScienceLogic SL1

ScienceLogic SL1 7.3
Based on 1 answer
Care should be taken when creating dashboards which present all of the collected data available to you.We have many routers at work.Almost all of them have 10K interfaces on each one.Creating dashboards which present many different views of many different, large routers can create undue database load. (We're actively discouraging their use as a long-running process because each dashboard widget gets its own database connection, not a shared database connection.) We will kill all long running queries in the database if they run longer than 30 minutes.The database schema design makes interesting trade-off decisions (optimizing for ease of write at the expense of complex / cross-device reads). The new GraphQL schema model looks promising, but we're still waiting for that to begin to appear in the SL1 core functionality.Given enough hardware and budget, you can go a long ways before you start pushing the boundaries of the platform architecture.Being conservative in what you monitor for the vast majority of your CIs allows you to retain compute capacity for dashboards, runbook engines and the like.Having large routers or vCenters will require an upscaling of your data collector sizings just to complete the Device Component Map data collection.
John &quot;Frotz&quot; Fa'atuai profile photo

Support

AppDynamics

AppDynamics 9.5
Based on 4 answers
AppDynamics has its own community site that includes forums and a knowledge base. On the forums, you can converse with other members of the community and ask technical questions as you have them. Though this forum isn’t filled with people there are active members for you to gain some valuable insights.
Eduin Zuloaga profile photo

ScienceLogic SL1

ScienceLogic SL1 6.1
Based on 4 answers
In some cases and depending on the support representative support is good, but in general, it requires customer management of the case vs. vendor management of the cases....like pulling teeth... time-consuming, etc, etc. Also want to comment that this applies to the Technical Support Group and the PSO Group at ScienceLogic. Support appears to be degrading over the past few years vs getting better and I suspect this is a result of structural changes in support group e.g. off-shoring/subcontract support. The roll-out of a new case management system and self-support tool made obtaining support much more difficult.
No photo available

In-Person Training

AppDynamics

No score
No answers yet
No answers on this topic

ScienceLogic SL1

ScienceLogic SL1 9.1
Based on 1 answer
On the Cisco IT 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 Cisco IT 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.
John &quot;Frotz&quot; Fa'atuai profile photo

Implementation

AppDynamics

No score
No answers yet
No answers on this topic

ScienceLogic SL1

ScienceLogic SL1 6.9
Based on 3 answers
Know your use case.
Know which inherent use case ScienceLogic approaches you with. (They still have a long history of Managed Service Provider that influences their thinking and they are learning to be self-aware and thoughtful about you rather than your deployment being just a templated deploy that they've done many times before.)

They are making progress, but your clear and persistent insistence on deployment according to your use case will help minimize problems.
John &quot;Frotz&quot; Fa'atuai profile photo

Alternatives Considered

AppDynamics

New Relic is only SaaS and keys off of AppDex scoring (i.e. industry baselines) and not on my application's baselines. Where most of our stuff is custom apps, going off of industry wasn't valuable to us. It was also cost prohibitive
No photo available

ScienceLogic SL1

ScienceLogic supports multiple vendor devices and it supports integration to multiple other applications. It gives the privilege to pull up the data from its database for customized reports. Automatically pulling up the device list from the CMDB helps in keeping the list of monitoring devices updated. Template feature to monitor the specific group of devices is very convenient to use.
Aditya Dev profile photo

Scalability

AppDynamics

No score
No answers yet
No answers on this topic

ScienceLogic SL1

ScienceLogic SL1 7.3
Based on 1 answer
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.)
John &quot;Frotz&quot; Fa'atuai profile photo

Return on Investment

AppDynamics

  • AppDynamics isn't cheap, but it definitely helps to ensure our applications and APIs are up and running without issue. The alerting is usually good but occasionally mixed, for example sometimes flagging a single error as a critical issue since the API is usually completely error free.
  • The cost saving in terms of trouble shooting and analyzing issues in production is fantastic - to know about issues before they are reported by customers enables you to be proactive in resolving them and ensuring maximum up time for our applications.
No photo available

ScienceLogic SL1

  • ScienceLogic allowed our Managed Service to implement Incident automation for the first time ever, which greatly increased our ability to accurately catch and triage issues.
  • As a diagnostic tool, it allows our Engineers to quickly verify their current status and identify trends, which increased our efficiency and effectiveness.
  • Increased the capabilities of our CMDB immensely, and allows our Solution Architects to quickly identify clients that may be in need of additional services.
  • Provided an avenue for additional lines of business, such as Monitoring as a Service (MaaS).
Tim Reaves profile photo

Pricing Details

AppDynamics

General

Free Trial
Yes
Free/Freemium Version
Yes
Premium Consulting/Integration Services
Entry-level set up fee?
No

AppDynamics Editions & Modules

Additional Pricing Details

ScienceLogic SL1

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Yes
Entry-level set up fee?
Required

ScienceLogic SL1 Editions & Modules

Edition
SL1 Infrastructure Health$01
SL1 Application Health$02
SL1 Service Health$03
SL1 Incident Automation$03
  1. per device
  2. per node
  3. per device
Additional Pricing Details

Rating Summary

Likelihood to Recommend

AppDynamics
8.8
ScienceLogic SL1
8.4

Likelihood to Renew

AppDynamics
ScienceLogic SL1
7.9

Usability

AppDynamics
ScienceLogic SL1
7.0

Reliability and Availability

AppDynamics
ScienceLogic SL1
7.3

Performance

AppDynamics
ScienceLogic SL1
7.3

Support

AppDynamics
9.5
ScienceLogic SL1
6.1

In-Person Training

AppDynamics
ScienceLogic SL1
9.1

Implementation

AppDynamics
ScienceLogic SL1
6.9

Scalability

AppDynamics
ScienceLogic SL1
7.3

Add comparison