r/SysAdminBlogs • • 6h ago

Grafana Loki – A Practical Guide to Centralized Log Management

6 Upvotes

Hi everyone,

I've been exploring centralized logging and Grafana Loki, particularly how it can help Linux administrators and DevOps teams troubleshoot issues across multiple servers and applications.

One thing I find interesting about Loki is that it doesn't index the full content of every log line like traditional logging systems. Instead, it indexes labels, which makes its approach to log storage and querying quite different.

In this guide, I've covered:

  • How Grafana Loki works
  • Loki architecture and its key components
  • How labels and log streams are used
  • Troubleshooting when logs aren't appearing in Grafana
  • Investigating slow log queries
  • Understanding high memory usage and label cardinality
  • When Loki makes sense compared with traditional logging solutions

I tried to keep it useful for people who are learning Loki as well as administrators looking to understand how it fits into their monitoring and troubleshooting stack.

I'd appreciate feedback, especially from anyone using Loki in production. How are you managing centralized logging today? Are you using Loki, ELK, or another solution?

Full guide:
https://datadevblog.com/grafana-loki-tutorial-guide/?utm_source=reddit&utm_medium=social&utm_campaign=grafana_loki&utm_content=post

Thanks for sharing your experience!


r/SysAdminBlogs • • 11h ago

I made free escape rooms for Microsoft admins: fix a broken tenant before the clock runs out

6 Upvotes

After the Learn post a few days ago, I wanted to try something less like studying and more like the actual job.

So I made escape rooms. Each one is a made-up Contoso tenant that's broken in one specific way. You get simulated sign-in logs, audit logs and settings, and a timer. You have to find the cause, fix it without making things worse, and then prove it works.

The bit I like most: shortcuts cost you. Delete the Conditional Access policy that's locking everyone out, or exclude someone from MFA to stop the prompts, and it works, but it logs a security incident against your score. Just like real life, the quick fix is usually the wrong one.

The five rooms so far, easiest first:

  • Nothing Enrols: new laptops join Entra but never enrol in Intune
  • The Expired Secret: the HR sync dies overnight with an AADSTS error
  • Locked Out: a Conditional Access policy locks out everyone, admins included
  • MFA Storm: the finance director approved a 3am MFA prompt, and the attacker is already in
  • Mail Is Down: a domain move leaves MX, SPF and DKIM pointing the wrong way

Each room ends with a debrief: what happened, how you'd fix it for real, and links to the Microsoft Learn docs. It's free, with no sign-up and no ads, and your times stay in your browser.

I'm adding 5 new rooms every week. If you've got a real outage story that would make a good room, tell me and I'll turn it into one (anonymised, obviously).

azureblog.co.uk/play


r/SysAdminBlogs • • 1d ago

On-Prem Enterprise Vault v14.5.2 - licensing question

Thumbnail reddit.com
1 Upvotes

r/SysAdminBlogs • • 1d ago

Logon Duration vs. Analyze Logon Duration: different numbers, different measurements

2 Upvotes

Someone in the ControlUp Community asked why Logon Duration in the console wasn’t matching the Analyze Logon Duration script. Fair question. You’re looking at the same logon, so you’d expect the numbers to match.

The two methods measure different parts of the logon process. The console is a good place to start looking for slow logons, and the script helps dig into the details.

In this case, there was another problem. Auditing had been disabled while troubleshooting disk I/O, and the script needs that auditing to produce useful results. So before spending too much time comparing the numbers, check that the data it needs is actually being collected.

We’ve all chased one problem and accidentally created another. This was one of those.

A few other useful things came up this week:

  • Scoutbees alert storms: A connectivity issue can make a bunch of checks fail at once. Requiring 2 or 3 consecutive failures instead of 1 can help cut down the noise. You can also adjust repeat notifications so the next notification comes when things return to normal. A maintenance window can stop alerts while you work on the issue.
  • Windows patch dashboards: Check the field you’re using. OS Patch gives you the feature release, such as 23H2 or 24H2. OS Version gives you the full build, such as 10.0.26100.xxxx. If you’re tracking monthly cumulative updates, OS Version is usually the useful one. Otherwise, you might install the updates and then wonder why your dashboard hasn’t changed.
  • Local Runner is in tech preview: It lets a workflow run an action on a ControlUp-managed device and call an internal API from inside your network, without exposing that API externally.

For transparency, I work at ControlUp and run the community. Sharing these here because the logon troubleshooting issue in particular seemed useful for anyone who runs into it.

When someone reports a slow logon, what do you check first? And if you’ve built a Windows patch compliance dashboard, which field are you using?


r/SysAdminBlogs • • 2d ago

Linux OOM Killer Troubleshooting – Why Applications Suddenly Disappear Without Any Error Logs

3 Upvotes

I recently worked on a Linux production troubleshooting scenario that I think many Linux administrators and Production Support Engineers can relate to.

Imagine a Java application suddenly stops running on a Linux server.

  • The process disappears.
  • No stack trace is generated.
  • Application logs show no shutdown message.
  • Logs simply stop at a particular timestamp.

One possibility is that the Linux OOM (Out of Memory) Killer terminated the process.

I put together a practical troubleshooting walkthrough covering:

  • How to identify OOM events using dmesg and journalctl.
  • How to identify the process terminated by the kernel.
  • How to correlate kernel logs with application timestamps.
  • How to investigate memory pressure and possible root causes.
  • Common troubleshooting mistakes.
  • How to approach the scenario during Linux/SRE interviews.

The focus is not just on running commands, but understanding what the outputs tell you and how to build a proper RCA.

Read the complete walkthrough:
https://datadevblog.com/linux-oom-killer-application-exits-no-logs/?utm_source=reddit&utm_medium=social&utm_campaign=Linux_OOM_Killer&utm_content=post

I'd appreciate feedback from fellow sysadmins and Linux engineers.

What would you investigate first when an application suddenly disappears without leaving any error logs?


r/SysAdminBlogs • • 2d ago

I got tired of merging 3 CSVs to answer “how many mailboxes are still on-prem?”, so I built a read-only PowerShell GUI for hybrid AD + Exchange + M365

3 Upvotes

I'm a sysadmin in a hybrid environment (Exchange 2019 + AD + Microsoft 365) and every time someone asked "how many mailboxes are still on-prem, how big are they, who has MFA, which licenses are wasted?" I ended up exporting three CSVs from three consoles and merging them in Excel by hand.

So I built HybridScope: one window, three sources, one merged view per user.

What it does

  • Pulls users from Active Directory, mailboxes from Exchange on-prem (Get-Mailbox, Get-MailboxStatistics, Get-RemoteMailbox) and licenses / sign-ins / OneDrive / MFA from Microsoft Graph
  • Tells you where each mailbox really lives (ON-PREM / 365 / NO MAILBOX) based on Exchange and Graph provisionedPlans, not on mailbox size
  • Real MFA status: registered methods, default method, legacy per-user state
  • RVTools-style tabs: Overview per OU, Users, Mailboxes on-prem / 365, OneDrive, MFA, Tenant licenses, an "Attention" list (on-prem mailboxes to migrate, licensed users without MFA, licenses on disabled accounts, inactive accounts, sync problems)
  • User card: double-click anyone to see AD, mailbox, OneDrive, MFA, licenses and their groups and roles in one window: AD groups (direct, nested, primary) and Entra groups (M365, security, distribution, dynamic) plus Entra roles
  • Sync check (new in 1.5): compares AD and Entra the way Entra Connect actually links them (source anchor → ImmutableId) and tells you what's broken or about to break before the next sync:

    • ImmutableId that no longer matches the AD anchor (the classic "deleted and recreated the AD account")
    • AD accounts that will soft-match a cloud account on first sync, or conflict with one that already has another ImmutableId
    • cloud accounts with a leftover ImmutableId, synced accounts that no longer exist in AD
    • provisioning errors, UPNs that fell back to onmicrosoft.com, duplicate anchors, and a warning if the last sync cycle is too old
  • 5 infrastructure modes with one click: Full Cloud / Full Hybrid / Hybrid (365 + AD) / On-Prem (Exchange + AD) / AD only
  • Export to formatted XLSX (ImportExcel) or CSV, all tabs or just the filtered current tab, and open saved reports back in the GUI (Ctrl+O or drag & drop) without connecting to anything
  • Command line too: -Auto for scheduled reports with certificate auth + history tracking, -Only MFA|Licenses|Sync|... for a single dataset, -PassThru to get objects in the pipeline
  • English / Italian UI

Some implementation details you might find interesting

  • Windows PowerShell 5.1, single .ps1, WPF built from XAML
  • All the heavy lifting runs in a persistent background runspace, so the UI never freezes; log lines come back through a ConcurrentQueue polled by a DispatcherTimer. There's a Stop button (BeginStop() on the running pipeline)
  • Only Microsoft.Graph.Authentication is needed: everything goes through Invoke-MgGraphRequest with manual paging, no giant SDK install
  • Exchange via implicit remoting (Import-PSSession, Kerberos), works from non-domain-joined PCs with explicit credentials
  • The sync check rebuilds the anchor the same way Entra Connect does (ms-DS-ConsistencyGuid, falling back to objectGUID, base64) and pairs users by anchor first, names only as a fallback. If most accounts don't match it assumes a custom source anchor (e.g. employeeID) and skips those checks instead of flagging everyone
  • Nested AD groups come from a single LDAP_MATCHING_RULE_IN_CHAIN query instead of walking memberOf recursively
  • Read-only: it never writes anything to AD, Exchange or the tenant

Repo: https://github.com/Thonno/hybridscope (MIT)

Screenshots are in the README (sensitive data blurred).

Full disclosure: I wrote it with a lot of help from an AI assistant and tested it on our own environment, so I'm sure there are edge cases I haven't hit yet. Feedback, issues and PRs are very welcome, especially from people with different setups (multiple forests, custom source anchors, Cloud Sync instead of Entra Connect, big tenants, cloud-only).


r/SysAdminBlogs • • 2d ago

Microsoft Teams Phone Implementation Guide for Large Companies. 6 Insider-Tips for 2026 w Visuals!

Thumbnail
youtu.be
3 Upvotes

r/SysAdminBlogs • • 2d ago

MemberOf Is Back in Entra ID - But Not for Free

10 Upvotes

Two weeks after the old memberOf stopped working, Microsoft released MemberOf Next. Same syntax, but it needs an Entra ID Governance license for every user in the group, plus the admins who manage them. And it only updates twice a day.

It also added a Group priority setting to all dynamic groups. On existing groups it’s empty, and their properties won’t save until you set it.

https://lazyadmin.nl/office-365/entra-memberof-next/


r/SysAdminBlogs • • 2d ago

Manufacturer Updates (Dell/HP)

Thumbnail reddit.com
1 Upvotes

r/SysAdminBlogs • • 3d ago

SAML signing cert expires in three weeks and I don't trust our app list

0 Upvotes

Our SAML signing cert expires December 9. We've got about 140 apps in Okta and I'm still not sure which ones are going to have problems when we rotate it.

Last time we did this, payroll went down for a morning. Turns out someone had uploaded the metadata manually years ago and the app was still using the old cert. While SSO was broken, the payroll team just used a local login none of us knew was still enabled. Only found out afterwards.

That's what worries me more than the cert rotation itself. We know which apps are in Okta, but not necessarily how they're handling authentication on their side.

Radiant Logic and Orchid were both mentioned when we started asking around. Haven't really dug into either, and I'm not even sure they'd help with this particular mess. We're probably doing this manually anyway.

For those who've done a big SAML cert rotation, how did you catch the apps with old metadata or local login paths before the cutover?


r/SysAdminBlogs • • 3d ago

geekondoor

Thumbnail
youtube.com
1 Upvotes

r/SysAdminBlogs • • 3d ago

Terraform Modules: 5 practices that make infrastructure code easier to maintain

2 Upvotes

When working with Terraform in real infrastructure environments, writing working configuration is only one part of the job.

The bigger challenge is keeping infrastructure code reusable, maintainable, consistent, and easy for other engineers to understand.

For example, imagine multiple engineers managing VPCs, EC2 instances, and storage resources across different environments.

Without proper module design and version management, configurations can become difficult to maintain and changes can introduce unexpected issues.

Here are five practices worth following when building Terraform modules:

1. Keep modules small and focused

Separate networking, compute, and storage responsibilities instead of building one oversized module.

2. Use descriptive variable names

Avoid unclear names like v1 or x. Use meaningful names such as instance_type and ami_id.

3. Document modules properly

Include a README with usage examples, input variables, outputs, and requirements.

4. Use Git version control

Track module changes, maintain stable releases, and make rollbacks easier.

5. Manage access to shared modules

Use private repositories, access controls, and branch protection to manage infrastructure code securely.

I recently put together a practical guide covering these five Terraform module practices, with examples.

Full article:
https://datadevblog.com/terraform-modules-best-practices/

Discussion question:

For those managing Terraform in production, what causes the biggest maintenance problems in your modules?

Is it poor module design, version management, documentation, or something else?

Would love to hear your experiences.


r/SysAdminBlogs • • 4d ago

How I Added 250GB of Storage to a Linux VPS for €4/Month Using S3 and ext4

Post image
0 Upvotes

I recently ran into a shortage of disk space on my VPS. I currently rent a VPS for €7 a month with this configuration: 4 vCPUs, 8 GB of RAM, and a 120 GB NVMe drive. It has 50 GB of free space left. But I need to run a Docker container whose image is 76 GB. I could upgrade my current VPS to get a 240 GB disk, but that would cost €30 a month. That’s steep. I noticed that my hosting provider offers 250 GB of S3 storage for just €4 a month, accessible over its internal network. So I started wondering how I could turn it into a filesystem and have Docker store files there.

First, I tried rclone. It lets you create a FUSE filesystem from your S3 storage. To speed things up, you can cache frequently used files on a local SSD using the --vfs-cache-max-size flag. Unfortunately, Docker uses overlay2, which requires filesystem operations that rclone mount does not guarantee: atomic renames, correct chmod and chown behavior, hard links, and extended attributes. In short, a full POSIX filesystem is needed.

And I found a solution: s3backer. It has 600+ stars on GitHub and provides a full-fledged ext4 filesystem. I set a 20 GB cache on my local SSD using the --blockCacheSize option, mounted it at /mnt/s3, and reconfigured Docker to store images, containers, and volumes there. As a result, the most frequently used files are cached locally instead of being pulled over the network from S3. What do you think? Expanding my virtual machine’s disk space by 250 GB for €4 a month? Pretty great, if you ask me!

By the way, here’s a summary table of the available options:

SolutionHow it worksProsCons
s3backer + ext4S3 as a block deviceFull POSIX filesystem, Docker compatibility, cachingComplex setup, latency, risk of filesystem corruption
rclone mountFUSE over S3Simple setup, local cache, support for multiple cloud providersIncomplete POSIX compatibility, some operations are unsupported
s3fsFUSE over S3Simple mounting, familiar file operationsSlow metadata operations, POSIX limitations
JuiceFSDistributed filesystem on top of S3POSIX, caching, high performanceRequires separate metadata storage
S3QLFilesystem on top of S3POSIX, compression, deduplication, encryptionExtra overhead, complex recovery

Of course, s3backer is far from the only way to turn S3 into a filesystem. There are at least two other interesting projects: JuiceFS and S3QL. Both run on top of S3, support POSIX operations and local caching, but they seemed like overkill for my use case.

JuiceFS is a fairly powerful distributed filesystem. It supports multiple servers working concurrently, caching, POSIX, and much more. But there’s a catch: in addition to S3 itself, it requires a separate metadata store. This could be Redis, PostgreSQL, MySQL, or even a local SQLite database. The last option doesn’t require a separate service, but you still have to keep the metadata database safe and back it up. Overall, it’s an interesting solution, especially if you have a server cluster. But I only have one VPS, and I didn’t want to set up extra infrastructure just to store Docker images.

S3QL is another interesting option. It supports POSIX, local caching, compression, deduplication, and encryption. It doesn’t need a separate database server: metadata is stored in SQLite and synchronized with the object store. But these extra features come at the cost of added complexity. Deduplication requires computing hashes, compression uses CPU time, and recovering the filesystem after a failure may require checking and restoring metadata with specialized tools. These aren’t critical drawbacks, but I didn’t see any particular advantages for my use case, either.

The key difference lies in the approach: JuiceFS and S3QL implement filesystems themselves using FUSE, while s3backer provides virtual block storage on top of which you can create a standard ext4 filesystem. As a result, Docker works with the familiar Linux filesystem, and s3backer translates block operations into requests to S3. No separate metadata databases, no deduplication, and no extra layers of file management.

Of course, this setup has its downsides too. Random reads and writes can be heavily affected by S3 latency, and losing the connection to the storage can bring the containers to a halt. A serious failure could also corrupt the filesystem. So I wouldn’t use this setup for critical databases. But for storing large Docker images that are downloaded once and then mostly read, it seemed perfectly reasonable-especially when S3 is available over the hosting provider’s local network. In short, I wanted an extra 250 GB for €4 a month without building a distributed storage system. From that perspective, s3backer seemed like the best fit.


r/SysAdminBlogs • • 4d ago

We're building a supercomputer

Thumbnail
golem.de
3 Upvotes

r/SysAdminBlogs • • 4d ago

Every service desk demo this quarter was AI, so we built a test from our own queue

1 Upvotes

Four service desk demos in six weeks and every one led with AI. We're about 3,500 people across three regions, so leadership wants a number before anything gets budget.

The one with the boldest claim was Atera's Robin, pitched as an AI technician that resolves up to 92% of tier 1 and complex tier 2 incidents. What sets it apart from the others is that it runs the fix itself, checks the result, and closes the ticket with notes on what it did. Hardware still comes back to us, and the approval rules for what it can touch are ours to write.

So we picked three categories from last quarter, password lockouts, print queues, and VPN client errors, and set one rule. A ticket only counts as resolved if no tech touched it and it wasn't reopened. That's the test every vendor gets on our data.


r/SysAdminBlogs • • 4d ago

A Linux time travel tool

Thumbnail
github.com
2 Upvotes

About a month ago I asked here if a tool to see ps, ss or lsof output at a past moment was worth building:

https://www.reddit.com/r/linuxadmin/comments/1wyhwfe/is_a_linux_time_travel_tool_worth_building/

I got some fair pushback (sar, atop, below, Prometheus, zabbix) and a few people who were curious. I looked at all of them. They cover a lot, but none of them could tell me which process had which connections open, or what lsof showed for a process at 02:45 last night. So I built it, mostly to find out if it could be done without hurting the server.

I wanted to name it "command line time travel" but then a though about the consequences of such a name and It's called clifr instead (command line flight recorder) and has two parts:

  • clifrd runs as a service and records processes, process starts and exits (through eBPF, so a process that lives 5 ms still shows up), TCP connections with the process that owns them, files held open, mounts, kernel messages and the usual system counters. It keeps 72 hours in /var/lib/clifr, 2 GB max.
  • clifr rebuilds the output of the normal commands for a past moment or a time range. It doesn't run the command, it rebuilds the output from the recording:

clifr --at "02:45" "ps aux"

clifr --since "02:00" --until "03:00" "ss -tanp dst10.0.4.21and dport = :5432"

clifr --since "1 hour ago" events # starts, exits, OOM kills, mounts

clifr diff --at "14:00" --at "14:20" "ss -ltnp"

There are about 40 commands so far: ps, top, pidstat, lsof, ss, netstat, free, vmstat, iostat, mpstat, df, ip, dmesg, systemctl list-units, lsblk, and more and all are 100% accurate.

The first thing people asked last time was the cost, so here are the numbers:

  ┌───────────┬─────────────────────┬─────────────────────────┬─────────────────────────┐
  │           │    Quiet server     │ Mixed load (4-day soak) │ Busy server (benchmark) │
  ├───────────┼─────────────────────┼─────────────────────────┼─────────────────────────┤
  │ CPU       │ 0.35% of one core   │ 0.5-0.6% of one core    │ 1.9% of one core        │
  ├───────────┼─────────────────────┼─────────────────────────┼─────────────────────────┤
  │ RAM       │ ~90 MiB             │ ~80-120 MiB             │ ~290 MiB (335 max)      │
  ├───────────┼─────────────────────┼─────────────────────────┼─────────────────────────┤ 
  │ Disk kept │ ~20 MiB/day         │ ~100 MiB/day            │ ~4 GiB/day              │
  ├───────────┼─────────────────────┼─────────────────────────┼─────────────────────────┤
  │ Network   │ none, no ports open │ none                    │ none                    │
  └───────────┴─────────────────────┴─────────────────────────┴─────────────────────────┘

Disk use depends heavily on how busy the server is.

clifr is not a monitoring tool and has no alerts. It's not a security audit tool either: it doesn't record file reads or writes, and root can stop it. It's for the "what was going on at 02:45" question, after the fact.

Status: it's a prototype, version 0.1.0. It hasn't run on a real production server yet (a friend starts one this week), and all the load has been synthetic. AGPL-3.0, no telemetry, nothing leaves the box.

So if you have a test or dev box (RHEL 8/9, Rocky, Alma), I'd really appreciate it if you tried it and told me what breaks or what looks wrong. The most useful thing for me is comparing what clifr shows with what you know was really happening.

I appreciate all your comments even if they are harsh


r/SysAdminBlogs • • 4d ago

Global Secure Access - Device Access is here!

Thumbnail
blog.sonnes.cloud
6 Upvotes

Another Global Secure Access update - Device Access is here!

Bringing pre-logon connectivity back to Windows devices using device identity instead of user identity like we know from the old days!

Think on password changes, first-time sign-ins, domain controller connectivity, Group Policy processing and on-premises device management - all before a user signs in to Windows!

I've been following and testing this feature since its earlier preview in June 2026, and it's great to finally see it reach Public Preview at Microsoft Ignite.

In my latest blog post, I cover a lot - check it out!

#Microsoft #EntraID #GlobalSecureAccess #GSA #ZeroTrust #MSecurity #MSIgnite #MVP #MVPBuzz


r/SysAdminBlogs • • 4d ago

Microsoft vs. Facebook outages: how do you test whether your recovery path is independent?

1 Upvotes

Microsoft’s November 13 incident report describes a network change that exposed a fault from an earlier capacity upgrade. In Facebook’s 2021 outage, a backbone failure led to the withdrawal of routes to its authoritative DNS servers, and engineers had trouble accessing recovery systems. Different failures, same question about shared dependencies.

If your primary network became unreachable, could you still resolve the names you need, authenticate, reach your management tools, and roll back the change? For those of you who’ve tested this end to end, what dependency surprised you?

I wrote up the comparison here: https://lippi.hu/microsoft-vs-facebook-leallas-en


r/SysAdminBlogs • • 4d ago

Entra Privilege Identity Management (PIM) - Role activation and more now possible at MyAccess

Thumbnail
blog.sonnes.cloud
11 Upvotes

From a feature request to Microsoft Ignite announcement – almost a year in the making!

Back in November 2025, I sent a feature suggestion directly to the Microsoft Entra engineering team: Why not bring Privileged Identity Management (PIM) role activation into the My Access portal?

An idea partly inspired by my findings around the hidden PIM URLs and undocumented UI experiences:

https://blog.sonnes.cloud/the-hidden-microsoft-entra-pim-urls-microsoft-never-documented-even-when-restrict-access-to-microsoft-entra-admin-center-is-enabled/

Fast forward almost a year… and here we are! 😎

I've had the opportunity to participate in the Private Preview, test the capabilities, share feedback and work closely with the team. Now it's officially announced in the Microsoft Ignite 2026 Book of News!

In my latest blog post, I share the story, hands-on testing, technical findings and a complete walkthrough, covering:
> PIM activation for Entra ID, Azure RBAC and Groups
> Just-in-Time (JIT) privileged access
> Remote Resource Access, Azure Bastion and Cloud Shell
> Requirements, limitations and findings not previously covered!

It's incredibly rewarding to see an idea evolve into an actual Microsoft product capability.

Sometimes, it's worth sending that email. You never know where it might lead! 😉

#Microsoft #EntraID #PIM #IdentitySecurity #MSIgnite #MicrosoftMVP #MVPBuzz #Community


r/SysAdminBlogs • • 4d ago

Docker bypasses UFW: why it happens and how to fix it for good

2 Upvotes

UFW was set to allow only SSH, and a container published on 8080 was still reachable from the Internet. If you run Docker on a server with UFW, some of your containers may be more exposed than you think, so I went through the whole thing on a clean server.

What I found:

  • The DOCKER-USER rule with --dport 8080 that many guides show does nothing. DNAT has already rewritten the port to the container's port by the time the packet gets there. You need to match the original port with conntrack instead (the exact rule is in the post).
  • Rules added with the iptables command are gone after a reboot. Putting them in /etc/ufw/after.rules keeps them.
  • On the default bridge, IPv6 goes through docker-proxy, so UFW does apply there.
  • For anything that doesn't need to be public, binding to 127.0.0.1:8080:80 is still the simplest fix.

Full write-up with every command and output: https://staunch.sh/blog/docker-ufw-debian-13/


r/SysAdminBlogs • • 4d ago

GitHub Backup Tool - update 1.4.0.1 is out

Thumbnail
blog.sonnes.cloud
2 Upvotes

No failure email doesn’t mean your backup is succeeded! 😅

I discovered my GitHub backup was failing without sending an email notification, as if a fun error from a GitHub org. im in

That got me to update mt GitHub Backup Tool to 1.4.0.1, bringing the following fixes:

> Repository owner filtering with -owner
> Discovery and branch enumeration that respect your filters
> Better error logging and a fix for missing failure emails when configured
and more...

And this is a strong reminder to check your backups - and test your restores!

Read more in my blog post here with why and the fix, and update your tool also - everyone has already downloaded my tool here from my GitHub over 29k times - a HUGE thanks you all! ❤️

#Microsoft #GitHub #Backup #OpenSource #CSharp #MVP #MVPBuzz #Community


r/SysAdminBlogs • • 4d ago

Logon Duration vs. Analyze Logon Duration: different numbers, different measurements

Thumbnail reddit.com
1 Upvotes

r/SysAdminBlogs • • 5d ago

Automating network discovery and remediation, what's your stack..

1 Upvotes

Trying to automate device discovery across a few sites and have scripts fire automatically when alerts hit. Some go Ansible plus NetBox, others use RMM platforms like Atera or NinjaOne that cover discovery and scripting. Leaning toward a platform, not sure yet how much of it works on our Linux boxes.