Source: thenewstack.io
Observability Is Shifting Left, Following Security and Ops
This is the second in a three-part series on “shift left observability.” A major trend sweeping our industry is to make common practices more “developer-friendly,” mostly by trying to meet developers where they are and integrating those practices into existing developer tools.
Shifting Left Security — In the world of application security, https://snyk.io/ has drastically changed the way it approaches supply chain security by continuously analyzing, detecting and offering automatic remediations for various third-party library vulnerabilities.
Existing https://lightrun.com/observability/observability-vs-monitoring/ tools focus mainly on operators, not developers, and with only a fraction of the https://www.developernation.net/developer-reports/dn21 practicing observability on a day-to-day basis, that’s becoming a real issue.
In the next article, we’re going to cover how to shift left observability in practice, and specifically how to apply it across the entire SDLC.
Shifting Left Security — In the world of application security, https://snyk.io/ has drastically changed the way it approaches supply chain security by continuously analyzing, detecting and offering automatic remediations for various third-party library vulnerabilities.
Existing https://lightrun.com/observability/observability-vs-monitoring/ tools focus mainly on operators, not developers, and with only a fraction of the https://www.developernation.net/developer-reports/dn21 practicing observability on a day-to-day basis, that’s becoming a real issue.
In the next article, we’re going to cover how to shift left observability in practice, and specifically how to apply it across the entire SDLC.
Related Articles
Community Partners
DevOps Careers