OverOps helps engineers at Moofwd, a fast-growing mobile communications platform for higher education, proactively prevent and resolve errors in pre-production and production to ensure reliable digital engagement between students and their universities.
Moofwd Mobile Solutions offers today’s universities a one-stop mobile communication solution to drive engagement across every phase of the student lifecycle, from recruiting prospective students and increasing retention, to keeping alumni connected beyond graduation. By leveraging the mobile devices students, faculty and staff already use every day, Moofwd provides a single sign-on solution including payments to access all campus systems and help keep everyone connected and engaged. Zubron, the company’s proprietary cloud-based Mobile Backend as a Service (MBaaS), allows Moofwd to integrate seamlessly with existing backend systems and ensure that colleges and universities can optimize the usage of their legacy systems while modernizing their cloud infrastructure.
As a platform that facilitates communication, application errors in our solution can mean the loss of the primary touchpoint between students and their universities. We compare it to your telephone system failing in the 1970s – if you lose that connection, you’ve lost touch with your customer.
For example, in the case of course enrollment, dates and deadlines are very specific and high demand classes with limited spots can be very competitive. If our application goes down while a student is in the middle of signing up for a course, not only does the student potentially lose the opportunity to join a particular class they need for their degree, but the university can also lose revenue.
Our portal is also vital in tracking student attendance and performance to ensure success and retention. If the application is failing to capture these things, the university loses the opportunity to take early corrective steps before the student fails or drops out.
Prior to OverOps, we had a variety of monitoring tools in place, but our logs still failed to catch critical issues and lacked the context we needed to track down and reproduce errors. Oftentimes, major bugs wouldn’t be caught and fixed until they were flagged to us by our users. We needed a way to identify, prioritize and resolve these issues early so we could be proactive in fixing the problem and alert our customers accordingly.
We selected OverOps because of its ability to capture 100% of errors and exceptions, and provide deeper data around the True Root Cause so we can resolve issues quickly. Much of our code comes from the support of third party developers, so it’s critical that we have a way to ensure code quality regardless of where it comes from. We also were drawn to OverOps for its ability to incorporate feedback loops into our lower-level environments and track defects and performance release-over-release so we can take a more proactive approach to overall application health and reliability.
We saw value almost instantly. During the initial OverOps workshop, within just a few hours we were all set up across our Dev, QA, UAT and production environments. The OverOps onboarding process was extensive and informative, and the services team was incredibly responsive and helpful throughout the implementation process.
We are using OverOps in both pre-production and production. From a pre-production standpoint, we are integrating OverOps with Jenkins and our build pipeline to serve as a code quality gate as we develop the newest version of our product. With this integration, our team is able to commit the code and automatically gain insight into the code quality and block poor quality code from going to production.
On the production side, our operations support team relies on OverOps to notify them anytime a critical exception occurs so we can determine the location and root cause of the problem – beyond just a stack trace – and proactively reach out to affected universities before students feel the impact. OverOps gives us the ability to monitor not only our own code, but all the API endpoints that our applications rely on, including those owned by our customers, and immediately know where the issue originates from.
OverOps integrates with and adds value to our Splunk and New Relic investments, providing a link to the OverOps True Root Cause directly within our APM and log management tools for deeper context and faster resolution.
We had an incident recently with one of our schools that was going through an enrollment period. The middleware engine that powers our Zubron app connects to our customers’ campus IT systems and their enterprise technology infrastructure. In this case, our middleware was trying to connect to this particular school’s web services but found that their system was completely down.
With OverOps, we received a notification directly to our email and were able to quickly locate the source of the problem and proactively tell our customer that one of their own databases was actually down so they could remedy the issue before it impacted enrollment.