Last week several of us had the pleasure of attending SplunkLive! in London. SplunkLive! events provide an opportunity for people to explore Splunk, to hear from partners, and to understand how their businesses can do more with Splunk, and we were proud to sponsor this year’s event in London.
The day started with a keynote and talks from Splunk customers, talking about situations where they’ve used Splunk to improve their businesses. In the afternoon, four breakout tracks provided talks focused on IT & App Development, Security, Advanced Tech and Advanced Value. Suitable for people new to Splunk or with more experience, these talks alone made SplunkLive! worth a visit.
As for us, we were busy at our stand, where we were showing our newly launched Open Banking App for Splunk. This gave us a great opportunity for talking to other Splunk users. It was great to talk to people at various stages of their Splunk journey, which allowed us to share our knowledge with rookie users and learn about use cases from other experienced Splunk users in different industries.
Throughout the day we ran a demonstration of our newly launched Open Banking App for Splunk. Andrew has been hard at work for the last few weeks modifying SimData to simulate an Open Banking API being accessed by a range of TPPs. On the day, a control panel on Andrew’s phone could be used to bring down various endpoints, showing our dashboards working in real-time.
With this data being generated, we were able to show how our app could be used to monitor activity on the API. As well as showing stats relating to activity by endpoint or by TPP, the dashboard can display warnings for endpoint failures, increased response times, and malformed API requests.
We had a great day down in London, meeting other Splunk users and showing off our new app. If you met us there, or if you would like to learn more about our Open Banking App or the solutions we can provide for you, please do get in touch. You can email us at email@example.com, or connect with us on Twitter or LinkedIn.