Instrumenting CI Pipelines

In a recent Test in Production Meetup, New Relic Developer Advocate Clay Smith discussed instrumenting CI pipelines using the three pillar approach of monitoring - metrics, tracing, and logging. He observed a single run of a build with multiple steps kicked off by a code commit to explore what tracing looks like within a CI pipeline. Smith applied observability concepts to AWS CodePipeline while building Docker images and shared his findings on how these ideas can be used in understanding the work done by systems. The talk highlighted the importance of connecting production performance traces with build artifacts, such as git commit hashes or version numbers, for better visibility into complex pipelines and deploy strategies.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.