Presented by Sebastian Schoer, Senior IT & Business Consultant for MARVES GmbH at SplunkLive! Zurich:
Operational Area & Responsibility
ITSI Project
Data Analysing, Processing & Visualisation
Examples
Next Steps
2. Agenda
▶ Who am I? Operational Area and Responsibility
▶ ITSI project
▶ Data Analyzing, Processing and Visualization
▶ Screenshots
▶ Next Steps
3. Operational Area and Responsibility
▶ Banking Trainee
▶ Economics and Information Technology
▶ IT and Business Consultant
▶ Portfolio Management Application (TripleA)
▶ Financial Reporting and Trading
▶ Rescuing Shelter Dogs and Cats in Romania
4. Pre-Project Tasks
▶ Key Challenges:
▶ Who defines the KPI and what exactly is it?
▶ How to define a Service that should be visualized?
▶ Do I know the Application that I am working with?
▶ What kind of Data do we need to get started?
▶ Challenging aspect of a complex System Architecture…
▶ Is there any Documentation about –
▶ Modifications
▶ Interfaces
▶ Feeds
▶ Etc?
5. What? How to
visualize?
KYA – Know
Your Application
Architecture API
Changes
Pre-Project Tasks
Challenges
KPI Service Data Docu
9. 9
Ordering Service Downtime
• Order services are at the core of a Private Bank’s
business. Portfolio and relationship managers must
place orders for clients for different securities
• We built the whole ordering process in Splunk ITSI
to get full visibility over the process
• Now, when something is down we can see exactly
what is causing the problem in the whole chain
• Previously issues went directly through to our IT
Helpdesk, whereas now we are already aware of the
issue
11. 11
Financial Server Downtime
• We have 120 financial servers running
different functions in the portfolio management
team
• Previously when a financial server went down,
we had to call level 2 support to monitor it with
another application
• We began monitoring each server through ITSI
and are now able to tell level 2 support where
the problem is
• This streamlined the process and has reduced
downtime from minutes to seconds
13. 13
Job-Controlling for Daily Processing
• We use a tool called UC4 across the business
to automate processes overnight when no one
is working
• We built the most important processes into a
glass table that gave us full visibility over their
functions
• We can now review clearly what happened
overnight, what worked, what didn’t work and
what didn’t hit its SLA
• This ensures that our resources are being used
more efficiently and we don’t have issues at
7am every morning