On a regular basis we offer technical round-tables to highlight the best parts of Ping, its technology and its products.
The most recent edition featured Beau Christensen, one of our PingConnect Site Reliability Engineers. Beau has been working for the last two years on improving the operation and reliability of PingConnect, our federation service. He used his roundtable time to discuss Splunk and its network log monitoring tool, which has proven to be an invaluable member of Beau's team. Beau took time out to tell round-table attendees about what Splunk is and how PingConnect uses it.
Beau calls Splunk “Google for log files”. Besides a lightening-fast query engine for all things text, Splunk includes indexers to support the query engine, and forwarders to collect files from endpoints. Beau uses Splunk to index such operational text items as audit log files, configuration files, and output from script execution.
If you’d like to learn more, we’ve made the video from the round-table available in our training center: TRT4: Using Splunk to Monitor SSO. It’s about 45 minutes long and includes valuable Q&A from attendees.
So what is the 411 on PingConnect? It is our compelling federation service targeted at enterprises that don’t want to run our flagship PingFederate themselves. PingConnect was initially offered to support IDP federation for small / medium sized businesses that want to access an Internet SP, usually for SaaS or partner access. PingConnect is now in beta with an offering for SaaS providers who want to be SAML SPs, but again, don’t want to run PingFederate in-house. After all, they’re SaaS providers and are happy to out-source whatever isn’t their core competencies to other SaaS providers.
Thus, PingConnect is a 24/7, mission critical piece of infrastructure that demands perfect uptime. We have a crack team of cloudsters who are experts in highly available, scalable hardware, software and operations. One gem in their arsenal is the Splunk tool. Check it out.