<?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 Lukas Manera</title><link>https://blog.xarc.dev/tags/monitoring/</link><description>Recent content in Monitoring 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>Fri, 01 May 2026 20:44:06 +0200</lastBuildDate><atom:link href="https://blog.xarc.dev/tags/monitoring/index.xml" rel="self" type="application/rss+xml"/><item><title>Hardening Legacy PHP in Constrained Environments</title><link>https://blog.xarc.dev/posts/2026/04/hardening-legacy-php-in-constrained-environments/</link><pubDate>Sun, 05 Apr 2026 12:00:00 +0200</pubDate><guid>https://blog.xarc.dev/posts/2026/04/hardening-legacy-php-in-constrained-environments/</guid><description>&lt;p&gt;The moment you realize that the roughest codebase you’ve seen is also one of the most valuable systems you’ve touched, things start to look a little different.&lt;/p&gt;
&lt;p&gt;“Just modernize it” is not a security strategy if the main thing that matters is keeping core business processes running in a system that drives major revenue.&lt;/p&gt;
&lt;p&gt;If you get called into an old PHP application, it can feel a bit like arriving at a crash site. After the initial shock, instead of judging, you start to think like an emergency responder: assess the scene, stabilize what matters most, and reduce the risk without making the situation worse.&lt;/p&gt;</description></item><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><item><title>MATA</title><link>https://blog.xarc.dev/showcase/matash/</link><pubDate>Wed, 02 Apr 2025 00:00:00 +0000</pubDate><guid>https://blog.xarc.dev/showcase/matash/</guid><description>&lt;p&gt;&lt;strong&gt;MATA&lt;/strong&gt; is a lightweight monitoring dashboard for PHP-heavy environments where full observability stacks are impractical.&lt;/p&gt;
&lt;div class="showcase-overview"&gt;
 &lt;div class="showcase-overview__grid"&gt;&lt;section class="showcase-overview__card showcase-overview__card--stack"&gt;
 &lt;h3&gt;Stack&lt;/h3&gt;
 &lt;div class="showcase-overview__tags"&gt;&lt;a class="showcase-overview__badge-wrap" href="https://www.php.net/" target="_blank" rel="noopener" title="PHP"&gt;
 &lt;img
 class="showcase-overview__badge"
 src="https://img.shields.io/badge/PHP-777BB4?style=flat-square&amp;amp;logo=php&amp;amp;logoColor=white"
 alt="PHP badge"
 loading="lazy"&gt;
 &lt;/a&gt;&lt;a class="showcase-overview__badge-wrap" href="https://htmx.org/" target="_blank" rel="noopener" title="htmx"&gt;
 &lt;img
 class="showcase-overview__badge"
 src="https://img.shields.io/badge/htmx-3366CC?style=flat-square&amp;amp;logo=htmx&amp;amp;logoColor=white"
 alt="htmx badge"
 loading="lazy"&gt;
 &lt;/a&gt;&lt;a class="showcase-overview__badge-wrap" href="https://mariadb.org/" target="_blank" rel="noopener" title="MariaDB"&gt;
 &lt;img
 class="showcase-overview__badge"
 src="https://img.shields.io/badge/MariaDB-003545?style=flat-square&amp;amp;logo=mariadb&amp;amp;logoColor=white"
 alt="MariaDB badge"
 loading="lazy"&gt;
 &lt;/a&gt;&lt;a class="showcase-overview__badge-wrap" href="https://bulma.io/" target="_blank" rel="noopener" title="Bulma"&gt;
 &lt;img
 class="showcase-overview__badge"
 src="https://img.shields.io/badge/Bulma-00D1B2?style=flat-square&amp;amp;logo=bulma&amp;amp;logoColor=white"
 alt="Bulma badge"
 loading="lazy"&gt;
 &lt;/a&gt;&lt;a class="showcase-overview__badge-wrap" href="https://www.openpolicyagent.org/" target="_blank" rel="noopener" title="OPA"&gt;
 &lt;img
 class="showcase-overview__badge"
 src="https://img.shields.io/badge/OPA-7C3AED?style=flat-square&amp;amp;logo=openpolicyagent&amp;amp;logoColor=white"
 alt="OPA badge"
 loading="lazy"&gt;
 &lt;/a&gt;&lt;a class="showcase-overview__badge-wrap" href="https://taskfile.dev/" target="_blank" rel="noopener" title="Taskfile"&gt;
 &lt;img
 class="showcase-overview__badge"
 src="https://img.shields.io/badge/Taskfile-0F766E?style=flat-square&amp;amp;logo=task&amp;amp;logoColor=white"
 alt="Taskfile badge"
 loading="lazy"&gt;
 &lt;/a&gt;&lt;/div&gt;
 &lt;/section&gt;&lt;section class="showcase-overview__card showcase-overview__card--screenshot"&gt;
 &lt;h3&gt;Screenshot&lt;/h3&gt;
 &lt;a class="showcase-overview__media" href="https://blog.xarc.dev/img/showcase/mata-screenshot.webp" target="_blank" rel="noopener"&gt;
 &lt;img src="https://blog.xarc.dev/img/showcase/mata-screenshot.webp" alt="MATA dashboard screenshot" loading="lazy"&gt;
 &lt;/a&gt;
 &lt;/section&gt;&lt;section class="showcase-overview__card"&gt;
 &lt;h3&gt;Why I built it&lt;/h3&gt;
 &lt;div class="showcase-overview__copy"&gt;I wanted monitoring that still works on shared hosting, constrained VPSes, and legacy PHP environments where you cannot install agents or extra services. Existing stacks were usually heavier than the problem called for.&lt;/div&gt;
 &lt;/section&gt;&lt;section class="showcase-overview__card"&gt;
 &lt;h3&gt;Tradeoffs&lt;/h3&gt;
 &lt;div class="showcase-overview__copy"&gt;It is intentionally not a full observability platform. The design stays small and deployable through read-only PHP nodes and pull-based collection, which fits small server fleets well but is not meant for large-scale or Kubernetes-style monitoring.&lt;/div&gt;
 &lt;/section&gt;&lt;section class="showcase-overview__card"&gt;
 &lt;h3&gt;Notes&lt;/h3&gt;
 &lt;div class="showcase-overview__copy"&gt;The useful part is combining uptime checks, PHP logs, server metrics, Composer inventory, and alerts in one place. OPA handles alarm decisions cleanly, Taskfile became part of the day-to-day workflow for setup, deploys, and user management, and optional Docker support keeps deployment flexible.&lt;/div&gt;
 &lt;/section&gt;&lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="status"&gt;Status&lt;/h2&gt;
&lt;p&gt;Released. Demo available at &lt;a href="https://demo.mata.sh"&gt;demo.mata.sh&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>