Home / Companies / New Relic / Blog / Post Details
Content Deep Dive

How to use change tracking to measure performance velocity

Blog post from New Relic

Post Details
Company
Date Published
Author
Tirslen Pather, Senior Developer Relations Engineer
Word Count
2,555
Company Posts That Month
37
Language
English
Hacker News Points
-
Post removed?
No
Summary

Integrating observability into CI/CD pipelines is key for DevOps engineers, and New Relic's change tracking offers a way to visualize and validate deployments, enhancing the speed and accuracy of delivery. The blog post explores how to send change tracking events using either the New Relic CLI or the GraphQL API, with additional methods for implementing these markers through GitHub Actions, Jenkins, and Ansible. Change tracking provides insights into application changes and their impacts on related services, allowing for improved monitoring and troubleshooting. Prerequisites for deployment include a New Relic account and user key, with detailed steps provided for using both the New Relic CLI and GraphQL for creating deployment markers. The post also outlines integrating change tracking with popular CI/CD tools like GitHub Actions, Ansible, and Jenkins, emphasizing the importance of these markers in identifying and resolving deployment issues efficiently.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Observability 3 1,266 225 69 -10%
Secrets Management 3 1,233 99 56 +30%
Developer Experience 1 220 118 59 -13%
Use This Data

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.