Split builds on feature flags to create the platform for controlled rollouts, so any team can target customers and roll out or revert new features without a deployment—or touching code.
Librato allows your team to collect, store, and visualize any metric across all levels of your application stack. Integrate Split data into Librato to monitor and measure the performance impact of Split changes. Our integration lets you bring Split’s audit log data (metadata including environment, split name, definition, the Split user who initiated the change, and a link back to the Split interface) into Librato to complement the information you’re already collecting from across your IT infrastructure.
Here’s a few of the things you can do by combining Librato and Split.
See feature changes in context. Integrating Split with Librato places Split audit logs alongside the information you’re monitoring from across your IT infrastructure so you can see what’s happening and troubleshoot faster.
Correlate feature impact with application performance. Librato tells you when things go wrong. Data from Split can help you understand why. Bring an additional layer of insight into Librato by overlaying Split’s rollout changes, correlating when a code change or feature rollout aligns with a shift in performance or other key metrics.
Creating a connection between Librato and Split is easy: create an API token in Librato and provide that API token and the user information for the individual who created it to Split to complete the connection.