<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Monitoring on CST company website</title><link>https://cst-bg.net/tags/monitoring/</link><description>Recent content in Monitoring on CST company website</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 11:37:34 +0300</lastBuildDate><atom:link href="https://cst-bg.net/tags/monitoring/index.xml" rel="self" type="application/rss+xml"/><item><title>13 clues you are doing DevOps right</title><link>https://cst-bg.net/blog/doing-dev-ops-right/</link><pubDate>Wed, 06 May 2026 11:37:34 +0300</pubDate><guid>https://cst-bg.net/blog/doing-dev-ops-right/</guid><description>&lt;p&gt;Here are 13 best practices which I think are a good indicator for professional DevOps team.&lt;/p&gt;
&lt;h3 id="do-you-have-fully-automatic-deployments"&gt;Do you have fully automatic deployments?&lt;/h3&gt;
&lt;p&gt;Having a 100% automated deployment is an essential part of good DevOps practices. It enables a software team to quickly iterate, deploy often and have a good general trust in the running software. Deployments can be triggered by some event like commit or manually. It is good practice to also have automated rollback procedure, just in case something goes wrong.&lt;/p&gt;</description></item></channel></rss>