<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Systemd-Services on Netdata</title><link>https://www.netdata.cloud/tags/systemd-services/</link><description>Recent content in Systemd-Services on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 21 Oct 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/systemd-services/index.xml" rel="self" type="application/rss+xml"/><item><title>How to monitor systemd service liveness</title><link>https://www.netdata.cloud/blog/systemd-service-liveness/</link><pubDate>Fri, 21 Oct 2022 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/systemd-service-liveness/</guid><description>&lt;p>The life of a sysadmin or SRE is often difficult, but occasionally very simple things can make a huge difference. Basic monitoring of your systemd services is one of those simple things, which we sometimes overlook. The simplest question one would want to know is if the thing that’s supposed to be running is actually running at all. If you use systemd services, you can guarantee an answer to that question within minutes using Netdata.&lt;/p></description></item></channel></rss>