{"id":6921,"date":"2024-11-19T15:20:59","date_gmt":"2024-11-19T20:20:59","guid":{"rendered":"https:\/\/www.exchangedefender.com\/blog\/?p=6921"},"modified":"2024-11-19T15:29:18","modified_gmt":"2024-11-19T20:29:18","slug":"upgrade-notice-login-service-enhancements-and-monitoring-improvements","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2024\/11\/upgrade-notice-login-service-enhancements-and-monitoring-improvements\/","title":{"rendered":"Upgrade Notice: Login Service Enhancements and Monitoring Improvements<\/strong>"},"content":{"rendered":"\n
<\/div>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Over the weekend, we designed, tested, and implemented new architectural solutions <\/strong>to address recent issues with the central login service for ExchangeDefender products. Additionally, we identified and began resolving a critical alerting issue that had prevented our NOC from receiving timely notifications about service outages.<\/p>\n\n\n\n

<\/div>\n\n\n\n

To expedite improvements<\/strong>, we deployed a web cluster originally planned for a later release. This new cluster introduces advanced high-availability features, including self-healing capabilities and integration with modern, distributed monitoring solutions to ensure consistent global accessibility.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Given the scope of this upgrade, we opted for a phased rollout using A\/B testing to ensure service reliability. Over the past three days, we\u2019ve gradually increased traffic to the new cluster, starting at 12%, while monitoring server and load balancer performance metrics. Currently, 20% of traffic is routed through the new cluster, with the remaining 80% handled by the legacy system. In the event of a failure in either cluster, the load balancer will dynamically shift all traffic to the active system, even if a customer was initially pinned to the affected cluster.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Performance Improvements<\/strong><\/h4>\n\n\n\n


The initial results have been highly encouraging, with noticeable performance gains. We\u2019ve observed a 5x improvement in P95 latency<\/strong> and a 3x improvement in P99 latency<\/strong> compared to the previous setup.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Next Steps<\/strong><\/h4>\n\n\n\n


Next weekend, we plan to implement the final phase of this upgrade, introducing automated transitions between data centers to address any performance or reliability issues proactively.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Addressing Notification System Failures<\/strong><\/h4>\n\n\n\n


During our investigation, we identified a failure point in our notification system. Alerts were being throttled or discarded by our SMS gateway, particularly during cascading outages triggered by login server downtime. We\u2019ve since refreshed our monitoring solution with modern analytics tools and implemented multiple alerting pipelines to prevent future disruptions. While we continue to work with our SMS gateway provider to resolve filtering issues, these changes significantly improve our ability to detect and respond to service issues.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Thank You for Your Patience<\/strong><\/h3>\n\n\n\n
<\/div>\n\n\n\n

We sincerely appreciate your understanding as we worked to diagnose and resolve these challenges. We recognize how frustrating the repeated service interruptions have been and want to assure you that we\u2019ve been actively addressing these issues with a focus on long-term reliability and minimal disruption.<\/p>\n\n\n\n

Thank you for your continued trust in ExchangeDefender.<\/p>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,1,46],"tags":[52,32],"class_list":["post-6921","post","type-post","status-publish","format-standard","hentry","category-exchangedefender","category-uncategorized","category-product-features","tag-email-security","tag-exchangedefender"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/6921","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=6921"}],"version-history":[{"count":6,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/6921\/revisions"}],"predecessor-version":[{"id":6928,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/6921\/revisions\/6928"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=6921"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=6921"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=6921"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}