2 years ago

https://dev.to/reubenwalker64 #why-you-should-use-codedriven-instead-of-infrastructuredriven-monitoring-tools-with-symfony Why you should use code-driven instead of infrastructure-driven monitoring tools with Symfony https://res.cloudinary.com/practicaldev/image/fetch/s--kyqJDnh---/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://symfonystation.com/sites/default/files/inline-images/code-monitoring-symfony-inspector.jpg This article will share why software developers should always prefer code-driven to infrastructure-driven monitoring tools. Understanding their different approaches will help you better organize your team, stay agile and fast during delivery times, and quickly identify issues before your customers are aware of them.

This is a perfect example for understanding the drawbacks infrastructure-driven monitoring tools can create for software developers.

The idea behind a code-driven monitoring tool is to create a monitoring environment specifically designed for software developers while avoiding any server or infrastructure configuration that they detest dealing with.