BigPanda is designed to enable enterprise IT to intelligently automate and scale service operations to meet the complex demands of the modern datacenter. The vendor says their algorithmic service operations platform turns IT noise from fragmented clouds, teams, applications and monitoring tools into actionable insights to speed the resolution of IT incidents. Customers include Intel, Workday, News Corp, Macy’s and Cisco.
N/A
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
BigPanda
ScienceLogic SL1
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
BigPanda
ScienceLogic SL1
Free Trial
No
No
Free/Freemium Version
No
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.
ScienceLogic SL1 services are effective and to move large amounts of data across other Cloud platforms and its services Automation through ScienceLogic SL1 is very effective and the creation of the report is very easy and quick. The analytics are accurate and the impacts on the …
If the organization has a proper CMDB asset record then BigPanda features can be utilized to their true potential as it has alert correlation capability. The alert can be redirected to the proper support team using the auto-share feature. This wouldn't be the case where asset records are not updated and the Operations have to manually assign the alerts to support groups.
For the last ten years, ScienceLogic SL1 has been my go-to recommendation for monitoring platforms. Its ease of learning curve and its out-of-the-box capabilities provide a majority accurate representation of alerting expectations with their eagerness to offer customizable solutions for one-off needs.
Cisco ACI Monitoring has some challenges with Rest APIs as we are facing some issue with the endpoint alerting which we don't have a way to properly snooze.
Alerts or KPIs needs to be flexible so it can adept easily while we migrate form any other tool in the market.
Tool should provide Flexibility locally in the configuration so that we don't have to alter the Global settings until/unless thing is required on a Global span.
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).
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)
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.
I've not been too involved with this portion. SL1 fails to find all the devices to be monitored and has actually taken a very long time. I'm very unsure if this is an SL1 problem or the single individual our company has implemented to the product. My company began implementing this product 10 months ago, and it has just recently been added to production and utilized by the NOC.
TrueSight didn't provide many customization options. The features provided were primitive as compared to BigPanda. TrueSight was being used just for alert visibility and assignment to a proper support group from a single console. Although Moogsoft had similar features as compared to BigPanda, the user administration and ease of use were a bit complicated. BigPanda provides a much simpler user interface.
Agentless monitoring is the best part of ScienceLogic SL1 monitoring, which is asked for by all the customers. UI is good and easy to handle. Port status from ScienceLogic SL1 collectors is easy even with bulk servers. The overall product is good for basic INFRA monitoring. Managing customer requirements is also achievable.
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.)
after all of our production devices are onboarded to SL1, we will be able to bring network monitoring in-house instead of it being outsourced as it is now
I am Engineer/SL1 user only, therefore I cannot comment on ROI or similar numbers
