/// article

Open Source SysAdmin Resources

By lordfrancs3

Open Source SysAdmin Tools and Resources Linux system administration has changed significantly since this resource was first published in 2017. Traditional responsibilities such as server installation, DNS, web hosting, databases, backups, networking, and security remain important. Administrators today also work with containers, infrastructure as code, distributed storage, observability, GitOps, Kubernetes, identity systems, automation, and cloud infrastructure. The PinoyLinux Open Source SysAdmin Directory is a curated collection of open-source software for Linux administrators, DevOps engineers, infrastructure engineers, network administrators, security professionals, homelab users, and students. This directory is different from a simple collection of links. Each project is included because it performs a useful infrastructure role, remains relevant to system administration, has historical importance, or provides educational value. Where appropriate, entries explain: What the project does Where it is commonly used Who should consider it Its relative learning difficulty Whether the project remains active How it relates to other infrastructure tools Projects that have been renamed, replaced, archived, or discontinued may remain in a separate historical section. This helps administrators understand older documentation and inherited systems without presenting old software as a current recommendation. Last reviewed: September 2026 Maintained by PinoyLinux How to Use This Directory A system administrator rarely needs every tool listed here. Your choices depend on what you operate. A small Linux server may need only SSH, systemd, Nginx, Fail2Ban, Restic, and a monitoring system. A private cloud or service-provider environment may require automation, distributed storage, DNS infrastructure, metrics, centralized logging, container orchestration, secrets management, and network automation. Use the directory as a map of the open-source infrastructure ecosystem. The difficulty labels provide a rough indication of the knowledge normally required to operate a project effectively. Beginner: Suitable for administrators learning the technology. Intermediate: Requires a working understanding of Linux, networking, storage, applications, or automation. Advanced: Usually involves distributed systems, clustering, complex networking, security architecture, or significant operational planning. These labels describe the technology’s operational scope. They are not ratings of product quality. 1. Linux System Administration Linux administrators still spend much of their time inspecting services, managing storage, reviewing logs, configuring networks, checking resource usage, and troubleshooting operating systems. Command-line administration remains fundamental, but open-source management interfaces can make individual servers easier to inspect and operate. Cockpit Cockpit is a web-based administration interface for Linux servers. It provides a graphical view of common server functions while continuing to use the normal Linux services and system interfaces underneath. Administrators can inspect logs, manage services, view storage, configure networking, examine resource usage, and perform other system tasks through a browser. Cockpit is useful when you want a graphical management interface without replacing the standard Linux administration model. Best for: Individual Linux servers, small server fleets, training environments, administrators transitioning from GUI-based platforms Difficulty: Beginner to Intermediate Status: Active PinoyLinux note: Cockpit should complement command-line administration rather than replace learning Linux commands. Knowing what Cockpit is doing underneath the interface remains valuable when troubleshooting. systemd Tools systemd is the service and system manager used by many major Linux distributions. Although systemd itself is part of the operating system rather than a standalone management product, its tools are fundamental to modern Linux administration. Important commands include: systemctl for managing services and units. journalctl for reading system and service logs. systemd-analyze for examining boot behavior and unit timing. timedatectl for time configuration. hostnamectl for hostname and related system information. Administrators responsible for Ubuntu, Debian, Red Hat Enterprise Linux, Rocky Linux, AlmaLinux, Fedora, and many other distributions should understand systemd. Best for: Linux service management and troubleshooting Difficulty: Beginner to Intermediate 2. Configuration Management and Automation Manual server configuration becomes difficult to maintain once you operate more than a few machines. Configuration management tools allow administrators to describe tasks and system states in files that can be stored in version control, reviewed, reused, and applied consistently. Ansible Ansible is an open-source automation platform used for configuration management, software deployment, orchestration, provisioning, and routine administrative tasks. One of its major advantages is its agentless design. Linux systems can normally be managed through SSH without installing a permanent Ansible agent on every target server. Automation is written primarily in YAML files called playbooks. A playbook might: Install packages Create users Copy configuration files Configure Nginx Deploy applications Restart services Manage firewall rules Configure network devices Perform rolling updates Ansible can be useful even when managing only a few servers because it turns repeatable administrative procedures into code. Best for: Linux automation, configuration management, deployment, network automation, repetitive administrative tasks Difficulty: Beginner to Advanced Status: Active PinoyLinux note: Ansible is one of the first automation tools a Linux administrator should consider learning. You can start with small tasks and gradually move toward complete infrastructure deployment. Salt Salt, also known as Salt Project, is an open-source automation and configuration-management framework. Salt supports configuration management, remote command execution, infrastructure orchestration, and event-driven automation. Unlike Ansible’s common SSH-based model, Salt frequently uses a master and minion architecture in which managed systems run an agent that communicates with a central Salt master. Other deployment models are also available. Salt can be useful when administrators need fast remote execution across large groups of systems. Best for: Configuration management, remote execution, infrastructure automation Difficulty: Intermediate to Advanced Status: Active Choosing Between Automation Tools Do not choose an automation platform simply because it has the longest feature list. Consider: How many systems you manage Whether installing agents is acceptable Whether administrators already know Python or YAML How quickly configuration changes must propagate Whether network equipment must also be managed How easily automation can be stored and reviewed in Git Whether the project fits your existing deployment process For many Linux environments, Ansible provides a practical starting point because it can begin with simple SSH-based automation without requiring a new management agent on every server. 3. Infrastructure as Code Configuration management usually focuses on configuring systems that already exist. Infrastructure as Code, or IaC, focuses on defining and managing infrastructure itself through version-controlled configuration. Instead of manually creating a virtual machine, network, DNS record, storage resource, or cloud service, you describe the desired infrastructure in code. The IaC tool then determines what must be created, modified, or removed. OpenTofu OpenTofu is an open-source infrastructure-as-code tool maintained under the Linux Foundation. It allows administrators to define infrastructure using declarative configuration files. OpenTofu can manage resources through providers for cloud platforms, DNS providers, Kubernetes, virtualization platforms, SaaS services, and other systems with APIs. A typical workflow includes: Write the infrastructure configuration. Initialize the required providers. Generate a plan showing the proposed changes. Review the plan. Apply the configuration. Maintain infrastructure state so future changes can be calculated. OpenTofu originated from the open-source Terraform ecosystem and maintains compatibility with many Terraform workflows and configurations. Best for: Cloud infrastructure, virtual machines, networks, DNS, storage, repeatable infrastructure provisioning Difficulty: Intermediate Status: Active PinoyLinux note: Infrastructure state is critical. Treat state files as important operational data. Protect them, back them up, and control access carefully. Pulumi Pulumi is an open-source infrastructure-as-code platform that allows infrastructure to be defined using general-purpose programming languages. Supported approaches include languages such as Python, Go, TypeScript, JavaScript, .NET, Java, YAML, and HCL. This can appeal to developers and infrastructure engineers who prefer programming constructs over a dedicated configuration language. Pulumi can manage cloud infrastructure, Kubernetes resources, networking, storage, and many other services through its provider ecosystem. The core Pulumi IaC tooling is open source. Pulumi also provides optional commercial hosted services. Best for: Infrastructure teams that want to define infrastructure using familiar programming languages Difficulty: Intermediate to Advanced Status: Active Crossplane Crossplane is an open-source framework for building infrastructure control planes using Kubernetes concepts and APIs. Instead of running an IaC command that creates resources and exits, Crossplane uses Kubernetes-style reconciliation. Controllers continuously compare the desired configuration with the actual infrastructure. Crossplane can be used to build internal infrastructure APIs that provision cloud and platform resources through Kubernetes. This makes it particularly relevant to platform-engineering teams that already operate Kubernetes. Best for: Kubernetes-based infrastructure control planes, internal platforms, cloud resource management Difficulty: Advanced Status: Active PinoyLinux note: Crossplane is not usually the first IaC platform a new administrator should learn. Understanding Kubernetes controllers, reconciliation, custom resources, and cloud APIs makes the project considerably easier to understand. 4. Containers and Container Tools Containers package applications and their dependencies into isolated environments that can run consistently across supported systems. Modern container infrastructure consists of several layers. The command users type, the container engine, the runtime, image tools, registries, networking components, and orchestration system may all be separate projects. Understanding these layers helps when troubleshooting container environments. Podman Podman is a free and open-source container engine for managing containers, pods, and container images. Its command-line interface is familiar to administrators who have used Docker. Podman supports daemonless operation and can run containers as non-root users. It can pull images from OCI-compatible registries, build containers, manage pods, and work with Kubernetes-oriented workflows. Best for: Linux containers, development environments, server workloads, rootless containers Difficulty: Beginner to Intermediate Status: Active containerd containerd is an open-source container runtime that manages the container lifecycle on a host. Its responsibilities include: Image transfer Image storage Container execution Container supervision Low-level storage Container lifecycle management containerd is generally embedded inside larger container systems rather than used directly by ordinary users. For example, Kubernetes environments commonly interact with containerd through the Container Runtime Interface. Best for: Container platforms and Kubernetes worker nodes Difficulty: Advanced Status: Active PinoyLinux note: Podman and containerd should not be viewed as direct equivalents. Podman provides an administrator-facing container engine, while containerd normally functions as infrastructure underneath a higher-level platform. LXC LXC, or Linux Containers, provides operating-system-level virtualization using Linux kernel features such as namespaces and control groups. LXC is commonly associated with system containers. A system container behaves more like a lightweight Linux machine. It can contain an init system, multiple processes, users, services, and packages. This differs from the common application-container model, where a container usually packages a specific application or service. Best for: Linux system containers, isolated Linux environments, lightweight server instances Difficulty: Intermediate Application Containers vs. System Containers The distinction matters. An application container usually packages a specific application and its dependencies. A system container provides an environment resembling a complete Linux system while sharing the host kernel. Neither approach is universally better. They solve different problems. Application containers work well for packaging services and application components. System containers work well when you need an isolated Linux user space that behaves more like a conventional server. 5. Container Orchestration Running one or two containers on a server is straightforward. Operating containerized applications across many machines introduces additional problems: Scheduling Service discovery Health checking Networking Storage Scaling Configuration Secrets Application updates Node failures Container orchestration platforms address these problems. Kubernetes Kubernetes, commonly called K8s, is an open-source container orchestration platform. It manages the deployment, scaling, networking, and lifecycle of containerized applications across clusters of machines. Kubernetes introduces objects such as: Pods Deployments StatefulSets Services ConfigMaps Secrets PersistentVolumes Jobs DaemonSets Ingress resources Administrators interact with Kubernetes through its API, usually using tools such as kubectl, configuration manifests, Helm, GitOps platforms, operators, or other automation. Kubernetes is powerful, but it introduces a significant amount of infrastructure knowledge. Before running Kubernetes in production, administrators should understand Linux, containers, networking, DNS, storage, TLS, monitoring, and failure recovery. Best for: Containerized application platforms, multi-node clusters, cloud-native environments Difficulty: Advanced Status: Active PinoyLinux note: Do not deploy Kubernetes simply because it is popular. A few containers on a single server may be easier to operate with Podman, Docker-compatible tooling, or another simpler approach. K3s K3s is a lightweight Kubernetes distribution intended to reduce the operational footprint of a Kubernetes installation. It is commonly used for: Edge environments Development Laboratories Small clusters Resource-constrained systems Kubernetes learning Because K3s implements Kubernetes, administrators still need to understand Kubernetes concepts even though cluster installation and operation can be simpler. Best for: Smaller Kubernetes clusters, labs, edge deployments Difficulty: Intermediate to Advanced 6. Virtualization and Private Infrastructure Virtual machines remain fundamental to Linux infrastructure. Containers have changed how applications are packaged, but virtual machines remain useful when workloads require different operating systems, kernel isolation, legacy software, dedicated resource boundaries, or conventional server environments. KVM and QEMU KVM, or Kernel-based Virtual Machine, provides hardware-assisted virtualization through the Linux kernel. QEMU provides machine emulation and virtualization capabilities and is commonly used together with KVM. Together, KVM and QEMU form the virtualization foundation behind many Linux virtualization platforms. Administrators often interact with KVM through higher-level tools rather than operating QEMU directly. Best for: Linux virtualization, private clouds, server virtualization Difficulty: Intermediate to Advanced libvirt libvirt provides a common API and management layer for virtualization platforms. It is frequently used with KVM and QEMU and provides tools such as virsh for managing virtual machines, storage pools, virtual networks, and related resources. Many virtualization management applications build on libvirt rather than interacting directly with hypervisor components. Best for: Managing Linux virtualization programmatically or from the command line Difficulty: Intermediate Proxmox Virtual Environment Proxmox Virtual Environment, commonly called Proxmox VE, is an open-source server virtualization management platform based on Debian. It integrates: KVM virtual machines LXC containers Web-based management Cluster management High availability Software-defined storage integration Networking Backup and restore functions Proxmox VE can operate as a single virtualization server or as a multi-node cluster. Its source code is released under the GNU Affero General Public License version 3. Best for: Homelabs, business virtualization, private infrastructure, virtualization clusters Difficulty: Intermediate to Advanced Status: Active PinoyLinux note: Proxmox VE provides a convenient management layer, but administrators operating production clusters should still understand the underlying networking, KVM, storage, quorum, backup, and Linux concepts. Incus Incus is an open-source manager for system containers, application containers, and virtual machines. It provides a consistent command-line interface and REST API for managing both containers and VMs. Incus can manage: Linux system containers OCI application containers Virtual machines Storage pools Virtual networks Images Projects Multi-server clusters This makes Incus useful when administrators want container-style management while still supporting full virtual machines. Incus is a community-led project under the Linux Containers organization and is released under the Apache 2.0 license. Best for: Linux system containers, virtual machines, development environments, private infrastructure Difficulty: Intermediate to Advanced Status: Active 7. Web Servers, Reverse Proxies, and Load Balancers Web infrastructure involves much more than serving HTML files. Modern web servers and proxies frequently handle: HTTP and HTTPS TLS termination Reverse proxying Load balancing Static content Request routing Compression Caching Access logging Application gateways TCP and UDP proxying Different projects emphasize different parts of this workload. Nginx Nginx is an open-source HTTP server, reverse proxy, content cache, load balancer, TCP/UDP proxy, and mail proxy. It is commonly deployed in front of application servers where it handles client connections and forwards requests to backend services. Common uses include: Static websites PHP applications Reverse proxies API gateways TLS termination Load balancing Content caching Media delivery TCP and UDP proxying Nginx uses an event-based architecture and is widely deployed on Linux servers. Best for: Web hosting, reverse proxies, load balancing, application delivery, caching Difficulty: Beginner to Advanced Status: Active PinoyLinux note: Nginx starts simple but can become a major infrastructure component. Administrators should understand proxy headers, TLS configuration, request limits, timeouts, caching behavior, upstream health, and logging before using complex production configurations. Apache HTTP Server Apache HTTP Server, often called Apache or httpd, is one of the long-running open-source web server projects. It supports static content, dynamic modules, virtual hosts, authentication, reverse proxying, TLS, URL rewriting, and many other web-server functions. Apache remains common in traditional web-hosting environments and applications that rely on .htaccess files or Apache-specific modules. Best for: Traditional web hosting, PHP applications, applications requiring .htaccess, module-based server configurations Difficulty: Beginner to Advanced Status: Active Caddy Caddy is an open-source web server and reverse proxy with strong built-in HTTPS automation. For public domain names, Caddy can automatically obtain TLS certificates, renew them, configure HTTPS, and redirect HTTP requests to HTTPS. This makes Caddy attractive for administrators who want straightforward web and reverse-proxy configuration without building a separate certificate-management process. Best for: Websites, reverse proxies, development, small infrastructure, automatic HTTPS Difficulty: Beginner to Intermediate Status: Active HAProxy HAProxy is an open-source reverse proxy and load balancer for TCP and HTTP applications. It is often used when traffic must be distributed across multiple backend servers. Common uses include: HTTP load balancing TCP load balancing Backend health checking High-traffic application delivery Database proxying API traffic distribution HAProxy is particularly useful when load balancing is its primary responsibility. Best for: TCP and HTTP load balancing, reverse proxying, high-traffic services Difficulty: Intermediate to Advanced Status: Active Traefik Proxy Traefik Proxy is an open-source application proxy designed around modern service-discovery environments. It can discover routing information from platforms such as Kubernetes and container environments rather than relying exclusively on manually maintained static configuration. This makes Traefik particularly useful in environments where applications and endpoints change frequently. Best for: Containers, Kubernetes, dynamic service discovery, reverse proxying Difficulty: Intermediate Status: Active Envoy Envoy is an open-source edge and service proxy commonly associated with cloud-native applications, service meshes, API infrastructure, and distributed services. Envoy provides advanced traffic-management and observability capabilities and is frequently embedded in larger platforms. It is considerably more complex than what most administrators need for a basic website. Best for: Service meshes, distributed applications, cloud-native networking, advanced proxy infrastructure Difficulty: Advanced Status: Active Which Web Proxy Should You Use? These projects overlap, but they are not identical. Use the requirements of the environment to narrow the choice. Nginx is a strong general-purpose option for web serving, reverse proxying, caching, and application delivery. Apache HTTP Server remains important for traditional web applications and hosting environments. Caddy is attractive when simple configuration and automatic HTTPS are priorities. HAProxy focuses strongly on proxying and load balancing. Traefik fits container and Kubernetes environments where dynamic service discovery matters. Envoy is suited to more complex distributed application and service-mesh architectures. 8. DNS, DHCP, IPAM, and Network Infrastructure DNS is one of the most important services in any infrastructure environment. Administrators should distinguish between authoritative DNS servers and recursive resolvers. An authoritative DNS server provides answers for DNS zones it is responsible for. A recursive resolver performs DNS resolution on behalf of clients, querying other DNS servers and caching the results. Large environments may also require DHCP, IP address management, DNS traffic management, and infrastructure documentation. BIND 9 BIND 9 is a mature open-source DNS server maintained by Internet Systems Consortium. It can operate as an authoritative DNS server, recursive resolver, or both, although separating authoritative and recursive roles is common in larger environments. BIND supports major DNS capabilities including DNSSEC and encrypted DNS transports. Its long history means administrators will encounter BIND in many existing Linux and Unix environments. Best for: Authoritative DNS, recursive DNS, traditional enterprise DNS infrastructure Difficulty: Intermediate to Advanced Status: Active PowerDNS Authoritative Server PowerDNS Authoritative Server is an open-source authoritative DNS server. It is designed specifically to serve authoritative DNS data and supports multiple storage backends and management approaches. PowerDNS is particularly interesting when DNS needs to integrate with databases, APIs, automation, or custom control systems. Best for: Authoritative DNS hosting, DNS automation, hosting providers, programmable DNS infrastructure Difficulty: Intermediate to Advanced Status: Active PinoyLinux note: Keeping authoritative DNS and recursive DNS as separate services can make the architecture and security model easier to understand and control. Unbound Unbound is an open-source validating, recursive, caching DNS resolver maintained by NLnet Labs. It focuses on recursive DNS resolution rather than authoritative zone hosting. Unbound can be deployed as: A local resolver A network DNS resolver A validating DNSSEC resolver A caching layer in front of other DNS infrastructure Best for: Recursive DNS, local resolvers, caching DNS, DNSSEC validation Difficulty: Intermediate Status: Active Kea DHCP Kea is an open-source DHCP server developed by Internet Systems Consortium. It provides DHCPv4 and DHCPv6 services and includes API-oriented management capabilities. Kea is designed as a modern replacement for the older ISC DHCP server architecture. It can use database backends and can be deployed in high-availability configurations. Best for: DHCPv4, DHCPv6, centrally managed network address allocation Difficulty: Intermediate to Advanced Status: Active NetBox NetBox is an open-source network and infrastructure system of record. It combines capabilities commonly associated with: IP address management, or IPAM Data-center infrastructure management, or DCIM Device inventory Racks Cabling VLANs VRFs Circuits Virtual machines Clusters Sites Network prefixes and addresses NetBox is particularly useful when infrastructure automation needs a reliable record of what the network and infrastructure are intended to look like. It provides REST and GraphQL APIs and supports extensions through plugins and custom fields. Best for: IPAM, DCIM, network documentation, infrastructure inventory, network automation Difficulty: Intermediate to Advanced Status: Active PinoyLinux note: NetBox should be treated as a source of infrastructure intent rather than simply another inventory spreadsheet. Its value increases when automation reads infrastructure information directly from it. 9. Storage and Distributed Storage Storage is one of the areas where Linux administrators need to understand the difference between a filesystem, volume manager, object store, block-storage system, and distributed storage platform. A single server and a multi-node storage cluster have very different operational requirements. Ceph Ceph is an open-source distributed storage platform that provides object, block, and file storage from the same underlying cluster. Its main interfaces include: RADOS Gateway, or RGW, for object storage and S3-compatible access. RADOS Block Device, or RBD, for block storage commonly used by virtualization and cloud platforms. CephFS for POSIX-compatible distributed file storage. Ceph distributes data across multiple storage nodes and is designed for environments where storage must continue operating despite individual disk or server failures. It is commonly used with virtualization, private clouds, Kubernetes, object-storage services, and large storage environments. Best for: Distributed storage, virtualization clusters, private clouds, S3-compatible object storage Difficulty: Advanced Status: Active PinoyLinux note: Ceph should not be treated as a replacement for a simple RAID array. It introduces distributed-system concepts including quorum, replication, placement groups, failure domains, recovery, network design, and cluster health. Use it when the infrastructure actually requires distributed storage. 10. Monitoring and Metrics Monitoring tells administrators what their infrastructure is doing. A useful monitoring system should help answer questions such as: Is the server reachable? Is the application responding? How much CPU and memory are being consumed? Is storage approaching capacity? Are requests becoming slower? Did an error rate increase? Is a network device dropping packets? Did a service stop? When did the problem begin? Monitoring systems vary considerably in architecture and purpose. Prometheus Prometheus is an open-source monitoring and time-series metrics system. It collects numerical metrics from applications and infrastructure and stores them as time-series data. Prometheus includes its own query language, PromQL, which allows administrators to analyze and correlate metrics. It is widely used for: Application metrics Linux server metrics Kubernetes monitoring Service monitoring Alerting Infrastructure metrics Alerting rules can be evaluated by Prometheus and notifications can be routed through Alertmanager. Best for: Metrics, applications, Kubernetes, infrastructure monitoring Difficulty: Intermediate to Advanced Status: Active PinoyLinux note: Prometheus is a metrics system. It should not be treated as a general-purpose log database. Zabbix Zabbix is an open-source monitoring platform for servers, networks, applications, databases, services, and virtual machines. It includes monitoring, historical data collection, dashboards, alerting, and problem detection within one platform. Zabbix can monitor systems using agents, SNMP, network checks, APIs, and other collection methods. This makes it useful for environments that want broad infrastructure monitoring from a single system. Best for: Servers, network devices, applications, mixed infrastructure Difficulty: Intermediate to Advanced Status: Active LibreNMS LibreNMS is an open-source network-monitoring system with strong support for SNMP-managed infrastructure. It can automatically discover devices and monitor: Routers Switches Firewalls Servers Interfaces Network traffic Device health Routing information Hardware sensors LibreNMS includes alerting, APIs, distributed polling, and extensive network-device support. Best for: Network monitoring, switches, routers, SNMP infrastructure Difficulty: Intermediate Status: Active 11. Logs, Tracing, and Observability Metrics tell you that something changed. Logs often tell you what happened. Distributed traces can show how a request moved through several services. Modern observability systems therefore commonly work with three major telemetry signals: Metrics Logs Traces These systems are often used together rather than as competing products. Grafana Grafana is an open-source visualization and observability platform commonly used to build dashboards from multiple data sources. Grafana can query systems such as Prometheus and Loki and display information through dashboards, panels, tables, graphs, alerts, and other visualizations. Grafana does not replace every monitoring backend. Its primary role is often to provide the interface where data from those systems can be examined. Best for: Dashboards, metrics visualization, log exploration, observability interfaces Difficulty: Beginner to Advanced Loki Grafana Loki is an open-source log aggregation system. Unlike systems that build a full-text index for every part of every log message, Loki primarily indexes metadata labels associated with log streams. Logs can then be queried using LogQL and viewed through Grafana. Loki is often paired with Prometheus because the two systems use similar labeling concepts. Best for: Centralized Linux logs, application logs, Kubernetes logs Difficulty: Intermediate to Advanced Status: Active OpenTelemetry OpenTelemetry, often abbreviated as OTel, is an open-source framework for generating, collecting, processing, and exporting telemetry. It supports: Metrics Logs Traces OpenTelemetry is vendor-neutral and can send telemetry to many different storage and analysis systems. A key concept is that OpenTelemetry is not itself the observability database or visualization system. It provides common instrumentation, protocols, SDKs, APIs, and collection components that allow telemetry to move between applications and observability backends. Best for: Application instrumentation, telemetry collection, distributed tracing, multi-tool observability environments Difficulty: Intermediate to Advanced Status: Active PinoyLinux note: A common architecture might use OpenTelemetry to collect traces and other telemetry, Prometheus for metrics, Loki for logs, and Grafana for visualization. The exact components depend on the environment. More Categories Coming The PinoyLinux Open Source SysAdmin Directory also covers: Network and security monitoring Host security and hardening Identity and access management Secrets and certificate management Backups and disaster recovery Databases and caching VPN and secure networking Git hosting CI/CD and GitOps Mail servers Asset management and CMDB Server management platforms Troubleshooting and CLI utilities Documentation and diagramming Historical, renamed, and archived projects These sections follow the same editorial approach used above. Historical Acknowledgement An earlier version of this PinoyLinux resource page was based in part on the community-maintained Awesome Sysadmin project. The current PinoyLinux Open Source SysAdmin Directory has been independently researched, reorganized, rewritten, and expanded to reflect modern Linux and infrastructure administration. Awesome Sysadmin is distributed under the Creative Commons Attribution-ShareAlike 4.0 International license. About This Directory Technology changes continuously. Projects change maintainers, licensing models, names, development status, and technical direction. New projects appear while others reach end of life. PinoyLinux periodically reviews this directory to identify: New projects worth including Projects that have changed licensing Renamed projects Archived projects Broken links Projects that are no longer maintained New PinoyLinux tutorials that should be connected to directory entries If you maintain an open-source system-administration project that belongs in this directory, or notice information that needs correction, contact PinoyLinux with the project details and primary source documentation.

[object Object]