Building a healthy productive engineering culture is hard and just deploying frequently with continuous deployment is not enough. I'm going to show you how you can use a carrot, not a stick, approach to take continuous deployment to the next level by celebrating team values with Sleuth.

Service alarms are going off and you are on the hook to restore stability, but you need to prevent any more changes to production while you dig further. You could "freeze" production by announcing it in the office, sending a message on Slack, or sending an email to the affected teams, but that may not be enough or may require extra work that would distract you from debugging and fixing the problem.

Today, we’re excited to announce you can now integrate LaunchDarkly with Sleuth, allowing you to track feature flags as a source of change in your DevOps stack. The Integration LaunchDarkly gives developers fine-grained control over which users see which features, and with our native LaunchDarkly integration you can now track the status and impact of feature flags relative to other source changes in your projects, such as code, issues, etc.

Software development teams are much larger than the engineers that write code. Writing and deploying code are often only the tip of the iceberg. A well oiled software team will often consist of: All of these people need to know something about what the software development lifecycle is producing and shipping, but the level of information can vary dramatically based on a team member's position. Sleuth was built to automatically generate information to satisfy each team member's needs.