Goliath Performance Monitor is an IT infrastructure monitoring platform from Goliath Technologies in Conshohocken, Pennsylvania.
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
Goliath Performance Monitor
ScienceLogic SL1
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Goliath Performance Monitor
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.
GPM is well suited to environments where there is a high volume of Citrix traffic coupled with a lot of different hardware infrastructure endpoints. Large scale multi-user operations where performance issue detection and resolution are key are the primary areas where GPM excels. Use of the GPM product is less appropriate when trying to monitor response times in a JVM application environment.
Appropriate if you are setting up a monitoring suite in new Infrastructure Environment. Definitely NOT suited for Migration Projects. ScienceLogic SL1 cannot cater to a lot of monitoring requirements which already would have been configured in old monitoring suite. Plus, limited support for customizations and having to go to "Feature Requests" route makes in extremely complicated.
GPM does exceptionally well at gathering and presenting deep metrics from our Citrix servers and storing them in the GPM database server. This is a vital strength for any system monitoring tool and allows administrators to address almost any system related performance question.
The MonitorIT front end console does a great job of providing graphical views the summarize data from a multitude of locations. This is particularly important in that it allows administrators to focus in on the reasons for performance issues in a proactive manner before hearing from the end users, especially given the large volumes of detailed data captured by the system
The MonitorIT product is also very adept at gathering metrics across the processing continuum, providing metrics for system resources, service availability and end-to-end user activity. This is a great strength of the system and allows us to develop Tableau visualizations in addition to the extensive reports and dashboarding capabilities of the GPM product.
From a purely personal level I would like to see MonitorIT be able to consume data from our clinical/operational databases instead of relying only on taking data in via the agent, log files and scripted sysoutput.
I think some improvements are possible in the area of custom monitoring of file systems, especially for the detection of missing file scenarios and file volume/rates. GPM only monitors traditional file system metrics like I/O, availability and space utilization, but custom scripting is possible within the design of the system.
Improvements in documenting the data model of the GPM database schema would also be very useful to advanced users of the system especially when additional external reporting tools are used to extend the GPM usefulness
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 to create stunning dashboard in AP2
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).
We use ScienceLogic SL1 in our organization to serve effective monitoring solutions to our external customers. Our customers depend upon us for critical events/alerts related to their IT infrastructure gears and using SL1, we're able to provide them with a proactive monitoring solution that resolves an issue before an impact is noticed by the customer. There are very few monitoring solutions that can cater to a variety of Cloud platforms like Public Cloud (AWS, Azure) and private cloud simultaneously and SL1 addresses this business problem very well
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.
When I joined our company, I did not know about the in person training at firts. Logging onto the SL University, I realised that there were different sessions being held at different times throughout the year. The training itself was good, but being in a different time zone, made it difficult to attend, but the sessions that I attended was great!
There are a lot of educational materials and courses on the SL1 training site (Litmos university). However the recording quality is sometimes not very good - screen resolution is low. There is a lack of professional rather than user-oriented documents and there are mistakes in documentation and education is not well structured.
Love to use Science logic tool as our first monitoring tool to provide services to the customer. Auto restart feature in Sl1 will allow us to get event when those crucial services has not started after server reboots and also minimize the P1's that we have as a result of that.
We eventually settled on GPM because of its very obvious strength and depth with Citrix monitoring. Our entire clinical system is deployed over a Citrix infrastructure so it was essential to choose a system whose key focus was Citrix monitoring. GPM's functionality is unrivaled when it comes to Citrix monitoring which is immediately apparent when one witnesses the deep internals of the Citrix platform being collected and reported on, in close to real-time.
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.)
GPM has had a decent positive ROI particularly in terms of identifying systemic issues and prevention of system downtimes or resource depletion etc. The GPM product shines a spotlight on configuration and design flaws and as a result makes the systems more stable and responsive, saving us time and effort in diagnosing and reporting on system problems. unfortunately these are quite intangible but nevertheless invaluable business objectives for us, but we can say that downtimes and slowness events have dropped consistently year on year since we deployed GPM.
Our overall objectives with the GPM project was to deploy a system that could be deployed centrally in our Corp datacenter while monitoring devices and users out in the facilities across the East, Central and West geographic regions. The cost of the endpoint agents was quite modest and provided great functionality at this price point. In this respect our business objectives are well satisfied and the system has been a complete success.
An important aspect of our business objective was to have a monitoring system that didn't require constant maintenance and babysitting, and as such the GPM system has worked out fantastically in that we only use 1-2 staff resources to monitor all the systems mentioned earlier in this review.
Once a powerpack is developed and configured for a device for one customer, it is easy to deploy the same powerpack on a second customer estate and configure specifically for that customer without having to reinvent the powerpack. This saves time and therefore money.
Once the customer estate tuning is complete, the Operations team have come trust the alerts. This is especially true when transient or self-correcting alerts are automatically cleared without ops team involvement, but a record is still available for audit and debugging purposes. This saves time and therefore money.
When setup correctly, it provides good visibility into applications, devices and whole customer estates. This saves time and therefore money when issues arise.
