Confirm Epic Availability in Production. 
Improve End User Experience.

The Goliath Application Availability Monitor for Epic is the only production-ready software that acts as an early warning system and lets you know before end users complain of logon failures or slowness.

How it works: Select your production implementation model – SaaS, on-premises, or hybrid. It can be deployed in minutes, even in complex environments. The Goliath Application Availability Monitor Module for Epic is a production-ready software that confirms application availability by exercising the whole application delivery infrastructure and executing the same logon sequence that users take during the logon process.

Slideshow: A Walkthrough of the Epic Application Availability Monitor.

This gives IT professionals visibility into the end users logon experience, directly from session launch. The availability monitor can be scheduled to run 24/7 and if your clinician or healthcare worker is going to experience a logon failure or slowness you will be alerted before they have an issue. Coupled with Goliath’s Performance Monitoring and Analytics Module for Epic makes this type of advanced warning better than real-time.

With each phase of the application launch process the Application Availability Monitor attempts, a screenshot is taken to provide visual evidence and objective proof of logon success or logon failure. This allows you to see the potential impact that typically elusive items like disclaimers, secondary authentication, and multiple launch sequences may have on the results of the Allscripts software login process. This allows healthcare IT administrators or the IT help desk to quickly gain context to go along with full-text logon sequencing results. As such, it’s much easier for IT to understand the intricacies of a particular logon issue without needing to: a) attempt to reproduce the problem manually, or b) wait for it to happen again (and when doctors/nurses are down, it’s very costly to act as a manual application performance monitor).

The Application Availability Monitor can be scheduled to run automatically and continuously, based on your preference, measuring the EHR module login success or failure across different locations and/or different types of users as needed. For example, it can run throughout the day so your EHR IT team can know immediately if/where there is a problem and at which stage of the process the problem occurs. Software launches can be scheduled to execute, for example, every 10-15 minutes so that IT can be alerted to problems before doctors or nurses feel the impact of a health record failing to load or taking far too long to do so. Many of our healthcare customers strategically have the Application Availability Monitor attempt logons overnight to get ahead of user login and application launch issues, with alerts reaching IT before end users reach their facilities in the morning.

Alert notifications of application login failure or login slowness can be sent immediately if a scheduled logon attempt fails at any time. These can be sent via email, SNMP, SYSLOG, or directly to your ticketing or enterprise monitoring solution.

Our Application Availability Monitor can be deployed however it’s needed. You can deploy it on-premises or in the cloud to identify individual user, hospital site, or geographically-sourced application availability issues. Because the software login attempts can be scheduled and remotely deployed, it can be strategically positioned at the hospital locations end users sign in from to provide objective evidence regarding logon success, logon failure, or logon slowness from the user’s login location. This way, you can diagnose whether login issues are hospital-specific, user-specific, or global in nature, providing the help desk with relevant data regarding availability and application performance if users need support.

We integrated a remediation engine directly into the Goliath Application Availability Monitor. The remediation engine is customizable; however, it comes with a large number of prebuilt rules aimed towards quick, automated resolution and prevention of further issues or complications. For example, a XenApp server could be set into maintenance mode to prevent any further failed logon attempts. Key dependencies on role servers could be checked to automate the investigation process. Or, a XenApp server could be checked to validate if it should be unavailable to mitigate false positives.

Unlike other technologies, the Goliath Application Availability Monitor has built-in logon scheduling functionality. We provide an easy to use, templated approach to configuring launch sequences. This gets you scheduled in minutes – not hours – without the need for custom scripting or recording sequences.

The Goliath Application Availability Monitor is fully integrated into the Goliath Performance Monitor. As a result, IT not only can identify application availability issues but also the root cause of the issue. Other technologies called “logon simulators” may be able to simply ‘identify’ a logon failure, but without full integration into an enterprise monitoring product, there is no way of identifying why the failure or slowness occurred. Therefore, these products can’t help you proactively troubleshoot an issue or prevent it in the future.

Since our Goliath system user attempts the logon process exactly as one of your end users would, our product truly exercises the entire application logon process from start to finish, testing the entire VDI delivery infrastructure as well. To achieve high-quality end user experiences, multiple elements of this infrastructure must successfully work in concert. One of the core problems of other applications is that they are monitored disparately. If they are gauged separately, they may look fine. It is only when executing the fully integrated launch process by multiple users – including remote access, XenApp or XenDesktop application/desktop availability, EHR application availability, and the Citrix delivery infrastructure – that you not only trigger issues but see contextual, objective evidence of where the root cause of your EHR module launch issues is located.

  • Press Releases
  • Privacy Policy
  • Reports
  • Dashboards
  • Sitemap
Goliath on LinkedIn Goliath on facebook Goliath on Twitter