mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

339K
active users

#logs

7 posts6 participants3 posts today

A few reasons why we say that is a great solution for log management:

⚙️ Easy to configure and manage.
💾 Production setup doesn’t need -compatible storage.
🆙 Doesn’t break already existing configs in new releases, so the upgrade path is very simple.
📝 Supports high-cardinality fields such as user_id, trace_id and ip, out of the box.
📚 Provides fast full-text search over plaintext .

Looking at the #logs is quite entertaining sometimes: repeated #ssh #scan from 92.255.85.0/24 well, #whois? Some provider with .hk and legal address Hong Kong something.
Traceroute? 50 ms from Amsterdam, 1.8 ms from Moscow. All hops are RU providers. Am I getting something wrong or it's a bit sus?

UPD
second-from-the-top source in the list is actually the same, just a different AS
AS57523 AS59425
Going to ask the upstream to ban the whole range.
#security #bots

Разбираем Pino: как работает самый быстрый логер для Node.js

Pino — один из самых быстрых логгеров для Node.js, но как он устроен внутри? В этой статье мы углубимся в низкоуровневые механизмы: разберём, как работают транспорты, чем отличается multistream от pipeline, и как настроить логирование без потери производительности. Вы узнаете, как использовать child loggers, маскировать данные с redact и избегать типичных проблем. Этот материал для тех, кто хочет понять Pino на фундаментальном уровне и применять его с максимальной эффективностью.

habr.com/ru/articles/894646/

ХабрРазбираем Pino: как работает самый быстрый логер для Node.jsЛоготип Pino Логи там, логи здесь... Логи — везде. Каждое современное приложение нуждается в логировании. В каждом языке есть свои фреймворки и библиотеки для сбора логов...

is the best alternative to (and ):
✅ Zero-config & schemaless ⚡
🔄 No breaking changes with upgrades 🔧
🔍 Supports high-cardinality fields out of the box 🎯
💾 Uses less RAM & disk space than Loki & Elasticsearch 📉
⚡ Executes queries faster than Loki ⚙️
📜 Better query language for logs than Loki
Read more in the latest blog post by our Co-founder - Aliaksandr Valialkin

itnext.io/why-victorialogs-is-

ITNEXT · Why VictoriaLogs is a better alternative to Grafana Loki?By Aliaksandr Valialkin

howard's being brilliant again and there's a new release of a great #macOS tool for #logs called #LogUI.

> Although my log browser Ulbow gives much better access, for many it’s still a daunting task. I’ve now switched almost entirely to using my new lightweight log browser, LogUI, and here explain how you can use it. Although it’s currently an early release with limited features, you should find it ideal for getting started.

\o/
#householdIT #syslog #infosec eclecticlight.co/2025/03/14/br

The Eclectic Light Company · Browse your Mac’s log with LogUIGet started browsing your Mac’s log using this lightweight and friendly utility. A walkthrough looking at what happened when I launched an app.

Guide to Interpreting Security Incident #Announcements:

"extremely sophisticated attack" : The attackers put more time into the attack than we spent designing our defences.

"no evidence customer #data was accessed" : We lack audit records and the logs have been rotated out.

"due to a misconfiguration issue" : We deployed with default #insecure settings.

"possible for only a short window" : We didn't dig too deep to determine how far back the bug existed.

"crafted invalid request data" : We forgot to add input #validation.

"supplementary fix" : We didn't understand the problem as well as we thought, so our previous fix was insufficient.

"may have been exploited" : We're positive they got away with data, but they deleted our #logs.

"multiple threat actors" : Everyone was in our systems before we noticed.

"most customers are unaffected" : There are corner cases that aren't as #vulnerable.

"error in a third-party component" : We forgot to update our dependencies.

"could lead to remote code execution" : You're #p0wned.

"malicious activity has been observed" : The issue has already appeared in the press.

"review equipment inventory to verify if devices require other mitigations" : You need to buy new stuff.

"remotely exploited to allow authentication bypass" : We forgot to require #login for this function.

"not aware of any exploits in the wild" : The attackers aren't bragging on darkweb fora yet.