RTView TIBCO & Kafka Middleware Monitoring & Personal Lines Insurer Success Story Proactive visibility into your middleware-based applications and services is one of the most effective ways you can ensure uptime. Learn how one of the largest personal lines insurers in the U.S. has used RTView to “shine a light into a dark room” for TIBCO and Kafka environments. And learn how RTView is constantly evolving to provide consolidated visibility across the latest technologies deployed on-premise, hybrid, and cloud environments.
4. Five Messaging Components in a fully integrated solution, provided in one single package
TIBCO FTL
The highest performing,
low-latency enterprise
and cloud-ready
messaging solution
TIBCO
Enterprise
Message Service
The industry leading JMS-based
solution for store and forward
messaging services
TIBCO eFTL
TIBCO
®
Messaging to
web and mobile-based
devices with HTML5 and
websockets
TIBCO Messaging -
Apache Kafka
Distribution
Secure, reliable, open
source, real-time
streaming data pipelines
TIBCO Messaging -
Eclipse Mosquito
Distribution
Connect to IoT devices using
MQTT to any TIBCO
®
Messaging
components
TIBCO® Messaging
4
7. Public Information
RTView - A Flashlight in a Dark Room
One of the largest personal lines insurer in the U.S.’s
usage of RTView improved TIBCO EMS issue identification
and reduced outages
SL Case Study 7
8. Public Information
Company and Background
• One of the largest personal lines insurance companies in the
United States
• Big TIBCO footprint: more than 5000 applications running on
TIBCO
• Integration environment is mainly TIBCO EMS, TIBCO
BusinessWorks, and Kafka. Moving to BW Container Edition for
some use cases.
SL Case Study 8
9. Public Information
Challenge
• TIBCO EMS is critical to operations and is the central point to all
enterprise transactions. Message traffic of 150 billion
messages/month
• If there is an issue with EMS, it causes a major impact on all
parts of the business.
• Time to recover from a Severity 1 outage used was 3 days to get
back up and running. Another month of cleaning up.
• Conservative cost of a Severity 1 outage to the business is
$4,000,000 including lost revenue
SL Case Study 9
10. Public Information
Challenge
• August 8th – 10th 2017, the Company experienced a Sev1 outage on
several key customer facing applications
• During the event EMS queues backed up and overall EMS
performance was impacted
• No true root cause was identified even after months of
investigation from both internal and external resources
• Investigation was painstakingly manual and very speculative
• Unrelated impacts to EMS infrastructure experienced months later
were inaccurately tied to this event
The Day We Found Out We Can’t See What’s Going On!
SL Case Study 1
11. Public Information
Solution: The Day We Turned the Lights On!
• October 10th 2017, the Company licensed a version of RTView available to
them through TIBCO
• With this limited license, they were able to view their most critical EMS
servers
• Within days, they saw value in understanding how queues were being
leveraged
• Significant network outages began to occur on Dec. 31,2017 that impacted
EMS infrastructure
• These sporadic issues occurred over several months in 2018 - RTView
provided staff with an immediate view of critical segments
• This information allowed the support teams to focus on where the actual
issues were
SL Case Study 11
12. Public Information
Results
• Reduced Severity 1 incidents due to performance and throughput issues
from an average of 2 per year to 0 since implementing RTView
• Cost of a Severity 1 incident estimated by Company conservatively at
$4,000,000 US$
• Reduced annual trouble tickets by over 90% from 30,000 to 400
• Improved MTTR (Mean time to Repair)
• Assuming a $300,000 licensing cost for the software and $60,000 for
annual support, breakeven could be as low as 15 days
SL Case Study 12
13. Public Information
The Future Continues to be Bright!
• October 11th 2018, the Company extended the limited RTView
license from TIBCO and approved usage of RTView Enterprise
Edition licensed from SL
• They now monitor all production EMS instances
• It is currently being leveraged for Apache Kafka as well
“RTView continues to be a beacon for our support staff to proactively
identify issues before they are impactful”
SL Case Study 13
25. Design and Publish Real-Time Custom
Dashboards
With Information Targeted for Specific Users
RTView Cloud
25
26. Relevant, Timely, Actionable Information
Custom Dashboards
Rapid Low–Code Development
Getting the Right information to the Right People at the Right Time.
Managed Service In the Cloud
Share Information with users
RTView Cloud Provides Users with:
26
We are seeing a lot of innovation here this week. AND in order to take advantage of a new technology you need to be able to monitor it.
One of our customers, a large US airline company, told us last month:
“The first thing management asks when we want to adopt a new technology is ‘how are you going to monitor it?’ If you don’t have monitoring for that, it’s a showstopper. “
So monitoring is becoming more important, not less at the same time that architectures are becoming more elastic and dynamic.
Here’s a Pattern we see repeated when RTView Introduced
But … outages happen to other people !
RTView – so they could centralize monitoring and alerting for all TIBCO middleware across all environments, adding additional technologies as well. In the future, they will add the service model capability to monitor those applications.
Which is a good segue to the next section!
Turnkey monitoring and alerting: pre-built displays and pre-configured alerts
TIBCO RTView Version 7 was recently announced in May. Available on your TIBCO download site
New html 5 UI
New alert detail and vastly improved usability
New Component Overview displays to see the most important key metrics, alerts, and historical trends for each monitored technology
Turnkey monitoring and alerting: pre-built displays and pre-configured alerts
Why is it becoming so much more difficult to monitor applications?
Well, modern applications are built on a variety of technologies including messaging middleware, brokers, Java, Tomcat, containers, and databases. Usually from a variety of different vendors.
Too many alerts. How to see in context ?
What components affect what services ?
So the common approach of using a different monitoring console for each technology just doesn’t work anymore.
What you want is a non-intrusive way to monitor the applications and services but one that provides deep visibility into the supporting middleware which is often a Blackbox to monitor.
Traditional monitoring tools, including APM, have very limited capability to look into these systems. For example, you can’t see inside TIBCO BusinessWorks with APM tools which only monitor at the level of the JVM. And you can’t look into your JMS queues without injecting code which requires re-writing and re-compiling your applications.
Why you need Enterprise Edition
See all technologies combined into single console. Non-intrusive monitoring with no agents. Here are some example views:
20 Applications -- EMS and BW Components organized by App
Component Utilization scaled to “Normal” -- Analytics on Key Metrics
At a glance see any areas where trouble might be brewing.
Proactive Centralized Alerting
End-To-End Views
Supports Large Environments
Real Application Visibility to predict infrastructure at risk within an application or service
See the health of all infrastructure components in the context of your application. Identify stress points over time for each component with this history heatmap.
Understand how a component problem can affect other components upstream and downstream.
2 different types of alerts
Service-based alerting is available in SL’s RTView Enterprise. Its great because it can really cut down on alert overload and fatigue. It enables app support teams to only get the alerts they care about and to prioritize alerts on business criticality of the service.
Component-based alerts are grouped by technology for an TIBCO support team or operations user.
RTView Enterprise also includes access to RTView Cloud.
RTView Cloud uses a hybrid architecture to enable you to create custom dashboards and views to share with your internal audiences.
This self-service capability enables your internal users to get the right information to the right people at the right time. No programming is required and your data remains securely behind your firewall.
RTView real-time data collection, analysis, and visualization
RTView Cloud -> sharing the information
Empower Users with Self-Service Tools
Organization Model with Multiple Users
Share Information – Custom - Flexible
Interactive Simple interface
Highly flexible deployment options