{"id":48089,"date":"2026-05-18T10:16:22","date_gmt":"2026-05-18T08:16:22","guid":{"rendered":"https:\/\/www.orisa.de\/server-monitoring"},"modified":"2026-09-04T09:31:57","modified_gmt":"2026-09-04T07:31:57","slug":"server-monitoring","status":"publish","type":"post","link":"https:\/\/www.orisa.de\/en\/server-monitoring","title":{"rendered":"If Systems could talk: How our Server Monitoring detects problems before customers do"},"content":{"rendered":"

CPQ and product configuration solutions are among those systems that simply have to work. Quotations are generated in real time, products are configured, prices are calculated, and integrations operate seamlessly in the background. When something goes wrong, sales teams and, ultimately, customers notice immediately.<\/p>\n

As part of the continuous development of our platform, we expanded it with a Server Monitoring feature during the mobile offer customer project. The goal was clear: move from reactive support to proactive platform operations.<\/p>\n

The starting point was a familiar scenario. A service stops responding, an application slows down, and the customer is the first to report the issue. From a technical perspective, this is simply an incident. From the customer\u2019s perspective, however, it can lead to a loss of confidence internally and damage the company\u2019s reputation externally. That is why our objective was straightforward: identify irregularities before they become visible to users.<\/span><\/p>\n

From reactive support to proactive operations<\/h3>\n

In a CPQ SaaS environment, multiple customers often share the same infrastructure in a multi-tenant setup, while each customer may run several applications and integrations simultaneously. This creates a complex system landscape where traditional \u201cserver up\/server down\u201d checks are no longer sufficient.<\/p>\n

Our monitoring solution therefore relies on custom-developed routines that run directly on the servers at regular intervals. These routines check critical system components, analyze resource consumption, and continuously provide status information to our administration team. In addition, we perform monthly vulnerability assessments using Greenbone to maintain visibility into the security posture of the entire system landscape.<\/span><\/p>\n

For customer environments such as mobile offer, our monitoring currently includes:<\/p>\n

    \n
  • Cyclical application availability checks every few minutes<\/li>\n
  • Minute-by-minute verification of critical services<\/li>\n
  • Continuous monitoring of CPU and memory utilization<\/li>\n
  • Monitoring of memory consumption for individual Tomcat instances<\/li>\n<\/ul>\n

    Any irregularities automatically trigger email alerts to our administration, service, and project teams. If a service fails, it is immediately investigated and restarted, often long before users notice that anything is wrong.<\/p>\n<\/div><\/div><\/div>

    Customized monitoring instead of a standard solution<\/h3>\n

    There are many professional monitoring tools available on the market. We deliberately chose a different approach by focusing on customization. Because our monitoring solution is developed in-house, we can tailor checks precisely to our platform, applications, and operational processes while continuously expanding its capabilities.<\/span><\/p>\n

    Today, application issues are often detected and resolved internally before customers become aware of them. As a result, response times are reduced, platform stability improves, and customer confidence grows.<\/span><\/p>\n

    What began as a project-specific feature has evolved into an integral part of our platform. With every enhancement, our server monitoring strengthens the stability, transparency, and reliability of the CREALIS\u00ae solution, helping ensure that our customers can rely on their CPQ environment every day.<\/span><\/p>\n<\/div><\/div><\/div><\/div><\/div>\n","protected":false},"excerpt":{"rendered":"

    System failures cost time, trust and revenue. Find out how our server monitoring for SaaS helps to identify problems at an early stage and keep our CREALIS platform running reliably and stably.<\/p>\n","protected":false},"author":11,"featured_media":48090,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wp_typography_post_enhancements_disabled":false,"footnotes":""},"categories":[210],"tags":[],"class_list":["post-48089","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wissen-en"],"_links":{"self":[{"href":"https:\/\/www.orisa.de\/en\/wp-json\/wp\/v2\/posts\/48089","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.orisa.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.orisa.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.orisa.de\/en\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/www.orisa.de\/en\/wp-json\/wp\/v2\/comments?post=48089"}],"version-history":[{"count":5,"href":"https:\/\/www.orisa.de\/en\/wp-json\/wp\/v2\/posts\/48089\/revisions"}],"predecessor-version":[{"id":48096,"href":"https:\/\/www.orisa.de\/en\/wp-json\/wp\/v2\/posts\/48089\/revisions\/48096"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.orisa.de\/en\/wp-json\/wp\/v2\/media\/48090"}],"wp:attachment":[{"href":"https:\/\/www.orisa.de\/en\/wp-json\/wp\/v2\/media?parent=48089"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.orisa.de\/en\/wp-json\/wp\/v2\/categories?post=48089"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.orisa.de\/en\/wp-json\/wp\/v2\/tags?post=48089"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}