CBORD Explains: Why You Should Monitor Data Service

The CBORD Data Service is a component within the application architecture situated above the database and below the presentation layer (as in the web server). It is present in CBORD's web-based food systems, e.g., NetMenu®, Room Service Choice®, Room Service Concero®, CBORD C-StoreTM, and NetHIMSTM.

The data service pulls from the database, manipulates data, and then passes it to the presentation layer. This process also works in the reverse allowing for data input from the end-user.

Why monitor?

The easy answer: it's a mission-critical operation. The real answer: you want to be proactive, not reactive. But it involves understanding the system itself, its components, and its architecture. In the various level of this architecture, the data service represents a crucial piece—it implements business rules that by storing, retrieving, and manipulating data help you achieve your goals.

How can you be proactive?

It does not have to be expensive. There are incredibly effective, open source infrastructure monitoring options available—like Nagios®, ZenOSS, and Zabbix®—that with a bit of work can be directly integrated with CBORD's web-based applications to set up alerts, observe trends, and anticipate future failure scenarios. A simple example would be to gauge the trend of the amount of memory that the data service consumes. Another could be to set up an alert when X number of failed authentication attempts happen in a short amount of time.

We invite you to get in touch with us for documentation and advice on this topic. This should get you and your IT department started on implementing application-level monitoring with the goal of reacting faster to unexpected events and hopefully avoid downtime altogether.

Klaus Kiesenhofer is the Senior Director of Quality and Information Technology at CBORD. He oversees quality assurance, infrastructure IT, and datacenter operations.