<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tools on Lukas Manera</title><link>https://blog.xarc.dev/tags/tools/</link><description>Recent content in Tools on Lukas Manera</description><generator>Hugo</generator><language>en-us</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener"&gt;CC BY-NC 4.0&lt;/a&gt;</copyright><lastBuildDate>Mon, 06 Apr 2026 00:05:40 +0200</lastBuildDate><atom:link href="https://blog.xarc.dev/tags/tools/index.xml" rel="self" type="application/rss+xml"/><item><title>MATA: Monitoring Legacy PHP Applications</title><link>https://blog.xarc.dev/posts/2025/06/mata-monitoring-legacy-php-applications/</link><pubDate>Tue, 10 Jun 2025 10:00:00 +0200</pubDate><guid>https://blog.xarc.dev/posts/2025/06/mata-monitoring-legacy-php-applications/</guid><description>&lt;p&gt;Most monitoring platforms assume you control the environment.&lt;/p&gt;
&lt;p&gt;They assume you can install agents, open ports, run background services, provision a database, and standardize deployment across every machine you touch.&lt;/p&gt;
&lt;p&gt;That is not the reality I run into most often.&lt;/p&gt;
&lt;p&gt;A lot of the PHP systems I work with are older revenue-generating applications running on shared hosting, constrained VPS setups, or managed servers where &amp;ldquo;just install another service&amp;rdquo; is not a serious option. They are often business-critical, rarely refactored, and maintained with a pragmatic mindset: keep them running, keep them secure, and avoid unnecessary moving parts.&lt;/p&gt;</description></item></channel></rss>