---
title: "Artem Senenko (@slima4) | Hashnode"
description: "uptimepage. Read the latest articles by Artem Senenko on Hashnode."
url: "https://hashnode.com/@slima4"
---

@slima4

# Artem Senenko

@slima4 · Cyprus · Joined June 2026

uptimepage

### [Two rejected series stalled all my metrics](https://uptimepage.hashnode.dev/two-rejected-series-stalled-all-my-metrics?utm_source=hashnode&utm_medium=feed)

TL;DR. Three alerts fired while production was healthy. My metrics account had gone over its active series limit, because a rate limit plugin in Caddy publishes 13 series for every client address. The

10 min read · [uptimepage.hashnode.dev](https://uptimepage.hashnode.dev/two-rejected-series-stalled-all-my-metrics?utm_source=hashnode&utm_medium=feed)

[Nov 12](https://hashnode.com/posts/two-rejected-series-stalled-all-my-metrics/6af5fa210d3424f7c8464ed8)

### ["Unable to verify the first certificate": when Node's --use-system-ca hint won't help"](https://uptimepage.hashnode.dev/unable-to-verify-the-first-certificate-when-node-s-use-system-ca-hint-won-t-help?utm_source=hashnode&utm_medium=feed)

TL;DR. Node's "unable to verify the first certificate" error now ends with a hint to try --use-system-ca. The flag helps when a root CA is missing and installed in the system store. It cannot help whe

7 min read · [uptimepage.hashnode.dev](https://uptimepage.hashnode.dev/unable-to-verify-the-first-certificate-when-node-s-use-system-ca-hint-won-t-help?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/unable-to-verify-the-first-certificate-when-node-s-use-system-ca-hint-won-t-help/6aeb659d9498c6c028589f33) [Nov 4](https://hashnode.com/posts/unable-to-verify-the-first-certificate-when-node-s-use-system-ca-hint-won-t-help/6aeb659d9498c6c028589f33)

### [How to get alerted when someone changes your DNS records](https://uptimepage.hashnode.dev/how-to-get-alerted-when-someone-changes-your-dns-records?utm_source=hashnode&utm_medium=feed)

TL;DR. Most DNS changes do not take your site down. A new MX record or an edited SPF record usually still resolves, so your uptime checks stay green. To catch these changes, list every record a name s

9 min read · [uptimepage.hashnode.dev](https://uptimepage.hashnode.dev/how-to-get-alerted-when-someone-changes-your-dns-records?utm_source=hashnode&utm_medium=feed)

[Oct 23](https://hashnode.com/posts/how-to-get-alerted-when-someone-changes-your-dns-records/6adac3a96e63683ebd2c01f8)

### [Google says on-call needs eight engineers. You have three.](https://uptimepage.hashnode.dev/google-says-on-call-needs-eight-engineers-you-have-three?utm_source=hashnode&utm_medium=feed)

TL;DR. Google's SRE book works out that a 24/7 on-call rotation needs at least eight engineers. A team of two or three cannot reach that number, so it has to change what the number is built from: whic

11 min read · [uptimepage.hashnode.dev](https://uptimepage.hashnode.dev/google-says-on-call-needs-eight-engineers-you-have-three?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/google-says-on-call-needs-eight-engineers-you-have-three/6ac506efcd05898c8013da5a) [Oct 6](https://hashnode.com/posts/google-says-on-call-needs-eight-engineers-you-have-three/6ac506efcd05898c8013da5a)

### [Uncle Bob's uml-viewer on Rust: 35 dependency cycles down to 3](https://uptimepage.hashnode.dev/uncle-bob-s-uml-viewer-on-rust-35-dependency-cycles-down-to-3?utm_source=hashnode&utm_medium=feed)

TL;DR. Uncle Bob released uml-viewer, a clickable architecture diagram that draws Dependency Rule violations in red and is meant to be driven together with a coding agent. It only parses Clojure, so I

15 min read · [uptimepage.hashnode.dev](https://uptimepage.hashnode.dev/uncle-bob-s-uml-viewer-on-rust-35-dependency-cycles-down-to-3?utm_source=hashnode&utm_medium=feed)

[Sep 22](https://hashnode.com/posts/uncle-bob-s-uml-viewer-on-rust-35-dependency-cycles-down-to-3/6ab22b7ee2eda70568963992)
