Operations | Monitoring | ITSM | DevOps | Cloud

Sending custom metrics to Datadog allows you to monitor important data specific to your business and applications, such as latency, dollars per customer, items bought, or trips taken. And tags are key to being able to slice and dice these custom metrics to quickly find the information you need. But collecting enough custom metrics to have complete visibility can be cost prohibitive. For example, you might run microservices instrumented across thousands of containers.

DevOps-oriented engineers live at the intersection of IT operations and software development – understanding much of what it takes to maintain IT infrastructure while also being able to write code and deploy new services. DevOps-minded teams not only create services – but they also maintain them. A DevOps structure forces teams to take accountability for their applications and infrastructure instead of allowing developers to throw code over the proverbial wall to IT operations.

Continuous integration (CI) makes the cycle from design to code to building artifacts seamless and consistent. Continuous delivery (CD) makes delivery of that artifact to an environment the same every time. But, what about the actual environment the artifact is running in? Is it the same every time? That’s a hard thing to guarantee — unless you take advantage of an Infrastructure-as-Code (IaC) approach. This post explains how to use Infrastructure-as-Code to improve CI/CD.