Insight Into Entire Cloud Environment
Imprivata’s DevOps and development teams collaborate to maintain the company’s tooling and automation infrastructure, employing best practices to ensure maximum performance during peak production. The teams have long relied on Splunk Enterprise for alerting, dashboarding, reporting service level agreements and troubleshooting.
“We’re very fortunate that we’ve always had Splunk; our system logs, Amazon Web Services, firewall logs and security logs all go into Splunk,” says a manager on Imprivata’s cloud platform team.
Splunk is essential for visibility and stability in Imprivata’s operational environment, which uses both Docker and Kubernetes containerization and Python automation controls to monitor resources deployed in Amazon Web Services. Imprivata developers use Docker on their laptop devices, and instead of keeping logs locally, they send them into Splunk Cloud for easier analysis.
“Our highly distributed, cloud-native architecture involves many services and containers, many different moving pieces. You could look at a log file, but you’d never be able to figure out which one to start with. It would be impossible to tell what was going on without Splunk,” the manager says.
“At Imprivata, we gather all cloud infrastructure, application and on-premises appliance logs into a single location so that troubleshooting of the application, infrastructure and cloud system is done in a single place: Splunk,” he adds. “Splunk dashboards help the product management team and engineering managers determine service level agreements and start to measure them from the very beginning — ingraining a culture of measurement and shared understanding of the product from inception.”