Daily Worklog: 2026-02-13

Overview

Date: 2026-02-13 (Friday)

Location: Remote

Focus: Spanish Tutor Session, SIEM Gap Analysis, Xianming Ding Linux Request

Spanish Homework: Ciudad vs. Campo

Tarea: Opinión Verbal - Ventajas y Desventajas de Vivir en la Ciudad frente al Campo

Nivel: DELE C2

Instrucciones: Dar una opinión verbal estructurada con introducción, cuerpo y conclusión. Usar conectores, preposiciones, locuciones y conjunciones ricas del español.

Introducción

Buenas tardes. Hoy me gustaría compartir mi perspectiva sobre un tema que ha generado un intenso debate a lo largo de la historia: las ventajas y desventajas de residir en un entorno urbano frente a un ambiente rural.

Cabe destacar que esta cuestión no admite una respuesta universal, dado que las preferencias individuales, las circunstancias personales y las prioridades vitales desempeñan un papel determinante en la elección del lugar de residencia.

Dicho esto, me propongo analizar ambas opciones con el fin de ofrecer una visión equilibrada que permita a cada oyente sacar sus propias conclusiones.

Cuerpo

Ventajas de la Vida Urbana

En primer lugar, la ciudad ofrece una innegable accesibilidad a servicios esenciales. Por un lado, los centros médicos, las instituciones educativas de prestigio y las oportunidades laborales se encuentran a mano, lo cual facilita enormemente la vida cotidiana.

Asimismo, el transporte público suele ser más eficiente y variado, lo que permite desplazarse sin necesidad de depender de un vehículo propio.

Por otra parte, la oferta cultural resulta incomparable: museos, teatros, conciertos y exposiciones están al alcance de quienes habitan en las urbes. De igual modo, la diversidad gastronómica y el acceso a productos internacionales constituyen atractivos significativos.

No obstante, sería un error pasar por alto las desventajas inherentes a la vida citadina. El estrés derivado del ruido constante, la contaminación atmosférica y la congestión vehicular pueden mermar considerablemente la calidad de vida. Además, el coste de la vivienda suele ser prohibitivo, lo cual obliga a muchas familias a vivir en espacios reducidos.

Ventajas de la Vida Rural

En contraposición, el campo ofrece una calidad de vida que difícilmente puede equipararse con la urbana en lo que respecta a la tranquilidad y el contacto con la naturaleza.

Ante todo, el ritmo de vida pausado permite disfrutar de momentos de sosiego que escasean en las grandes ciudades. Por añadidura, el aire puro, los espacios abiertos y la ausencia de contaminación acústica contribuyen a un bienestar físico y mental notablemente superior.

Desde el punto de vista económico, el coste de vida tiende a ser más asequible: las viviendas son más amplias y los productos locales resultan más frescos y económicos.

Sin embargo, conviene señalar que la vida rural no está exenta de inconvenientes. La escasez de servicios médicos especializados, las limitadas oportunidades educativas y profesionales, así como la distancia con respecto a centros urbanos pueden representar obstáculos significativos, sobre todo para quienes tienen hijos o necesitan atención médica frecuente.

A esto se suma el aislamiento social que puede experimentarse en comunidades pequeñas, donde las opciones de ocio y las redes de apoyo son más restringidas.

Conclusión

En definitiva, tanto la ciudad como el campo ofrecen ventajas y desventajas que deben sopesarse cuidadosamente en función de las necesidades y prioridades de cada individuo.

A mi juicio, no existe una opción intrínsecamente superior a la otra; más bien, se trata de encontrar el equilibrio adecuado que se ajuste a nuestro estilo de vida y aspiraciones.

Personalmente, considero que la solución ideal podría residir en un modelo híbrido: vivir en una zona semiurbana o en las afueras de una ciudad mediana, donde se pueda disfrutar de lo mejor de ambos mundos sin renunciar completamente a ninguno de los beneficios.

Para concluir, me gustaría enfatizar que la decisión final ha de tomarse teniendo en cuenta no solo factores prácticos, sino también nuestras necesidades emocionales y espirituales, puesto que el lugar donde vivimos incide directamente en nuestra felicidad y bienestar general.

Muchas gracias por su atención.

Conectores y Locuciones Utilizados

Tipo Español Traducción

Introducción

Cabe destacar que

It’s worth noting that

Causa

Dado que / Puesto que

Given that / Since

Transición

Dicho esto

That said

Finalidad

Con el fin de

In order to

Orden

En primer lugar / Asimismo / De igual modo

First / Likewise / Similarly

Contraste

Por un lado…​ Por otra parte

On one hand…​ On the other

Disponibilidad

Se encuentran a mano / Están al alcance de

Are at hand / Within reach of

Consecuencia

Lo que permite / Lo cual obliga

Which allows / Which forces

Concesión

No obstante / Sin embargo

Nevertheless / However

Advertencia

Sería un error pasar por alto

It would be a mistake to overlook

Contraposición

En contraposición

In contrast

Énfasis

Ante todo

Above all

Adición

Por añadidura / A esto se suma

Furthermore / To this we add

Perspectiva

Desde el punto de vista

From the point of view

Limitación

No está exenta de

Is not free from

Relación espacial

Con respecto a

With respect to

Condición

Sobre todo

Especially

Conclusión

En definitiva / Para concluir

In short / To conclude

Opinión

A mi juicio / Personalmente

In my opinion / Personally

Comparación

Más bien

Rather

Conformidad

Que se ajuste a

That fits

Modo

Sin renunciar a

Without giving up

Consideración

Teniendo en cuenta / Sino también

Taking into account / But also

Vocabulario Avanzado

Palabra/Expresión Significado

Mermar

To diminish, reduce

Prohibitivo

Prohibitive (very expensive)

Equipararse

To be equated with

Sosiego

Tranquility, peace

Escasear

To be scarce

Sopesar

To weigh (consider carefully)

Intrínsecamente

Intrinsically

Incidir

To affect, impact

Session: domus-captures Build Fixes

Issue

Multiple worklogs had build errors/warnings:

  • Unescaped attributes - References like {ad-dc-ip} were being interpreted as attribute substitutions instead of literal text

  • Pipe characters in tables - grep -E 'error|warn' broke table parsing because | is the cell delimiter

Resolution

Pattern Fix

Cross-component xrefs

Convert to plain text: \`infra-ops::runbooks/file.adoc\` - Description

Attribute references

Escape with backslash: \\{attribute\\} renders as {attribute}

Pipe in tables

Escape: error\|warn renders as error|warn

Files Fixed

  • WRKLOG-2026-02-09.adoc - Converted xref to plain text

  • WRKLOG-2026-02-11.adoc - Escaped {ISE_PAN_FQDN} and research device attributes

  • WRKLOG-2026-02-12.adoc - Escaped attribute references, converted xrefs

  • REF-2026-02-grep-patterns.adoc - Escaped pipe in grep example

Verification

# Build aggregator - all components
cd ~/atelier/_bibliotheca/domus-docs && make 2>&1 | grep -iE "(ERROR|WARN)"
# Result: ZERO errors/warnings

# Check Cloudflare Pages deployment status
CLOUDFLARE_ACCOUNT_ID="7f6981e005108a7a90b03ec3ff4b5197" \
  wrangler pages deployment list --project-name=domus-docs | head -5

Antora Version Standardization

Fixed version inconsistency across all domus-* components:

# Before: Some repos had version: ~ (unversioned)
# After: All repos have version: '2026'

# Fixed repos:
# - domus-captures
# - domus-automation-ops
# - domus-identity-ops (quoted for YAML consistency)

Session: D2 Diagrams & SVG Migration

Overview

Migrated captures-hierarchy diagram from PNG to SVG and updated D2 source to reflect current Antora structure. Documented pattern matching techniques used throughout.

Pattern Matching Techniques Used

grep - Finding Files and Content

# Find function in shell config
grep -C 5 "domus-push" ~/.zshrc

# Search for pattern across files
grep -r "captures-hierarchy" docs/

# Find files containing pattern (files only)
grep -l "pattern" *.adoc

# Regex pattern with extended grep
grep -E "push.*remote|for.*remote" ~/.zshrc

Glob - File Pattern Matching

# Find all D2 files
ls docs/modules/ROOT/examples/diagrams/*.d2

# Find all domus-* directories
ls -d ~/atelier/_bibliotheca/domus-*/

# Match specific file patterns
ls **/captures-hierarchy.*

awk - Field Extraction

# Extract specific columns
awk '{print $1, $3}' file.txt

# Filter by pattern and print
awk '/error/ {print $0}' logfile

# Custom delimiter
awk -F':' '{print $1}' /etc/passwd

sed - Stream Editing

# Preview replacement (non-destructive)
sed -n 's/old/new/gp' file

# In-place replacement
sed -i 's/png/svg/g' index.adoc

# View specific line range
sed -n '10,20p' file.txt

D2 Diagram Updates

Key Learning: D2 Only Supports SVG Output

Kroki returns 400 error for PNG format with D2:

# WRONG - D2 doesn't support PNG
[d2,diagram-name,png]

# CORRECT - Use SVG
[d2,diagram-name,svg]

Rendering D2 with CLI

# Render D2 to SVG with dark theme (200 = dark)
d2 --theme 200 source.d2 output.svg

Catppuccin Mocha Color Palette for Dark Themes

# Bright colors that pop against dark backgrounds
style.fill: "#74c7ec"   # Sapphire - primary elements
style.fill: "#94e2d5"   # Teal - secondary elements
style.fill: "#f5c2e7"   # Pink - highlights
style.fill: "#f9e2af"   # Yellow - connections
style.fill: "#a6e3a1"   # Green - success states
style.fill: "#fab387"   # Peach - warnings
style.fill: "#cba6f7"   # Mauve - root/important
style.font-color: "#11111b"  # Crust - text on light fills
style.font-color: "#cdd6f4"  # Text - text on dark fills

captures-hierarchy.d2 Migration

Before (Outdated PNG)

  • Old structure showing 03_Captures/ layout

  • PNG format (632KB)

  • Pixelated on retina displays

After (Current SVG)

  • Reflects actual Antora module structure

  • SVG format (62KB) - 10x smaller

  • Scales perfectly at any resolution

  • Editable source in examples/diagrams/

File Locations

Source:  docs/modules/ROOT/examples/diagrams/captures-hierarchy.d2
Output:  docs/modules/ROOT/images/diagrams/captures-hierarchy.svg

Commands Used

# Render SVG
d2 --theme 200 examples/diagrams/captures-hierarchy.d2 images/diagrams/captures-hierarchy.svg

# Update reference in index.adoc
sed -i 's/captures-hierarchy.png/captures-hierarchy.svg/g' pages/index.adoc

# Clean old files
rm images/diagrams/captures-hierarchy.png
rm images/diagrams/captures-hierarchy.d2  # duplicate in wrong location

SVG Benefits Over PNG

Attribute PNG SVG

File size

632KB

62KB (10x smaller)

Scaling

Pixelates

Perfect at any size

Retina display

Blurry

Crystal clear

Editable

No (binary)

Yes (XML text)

Dark theme

Fixed colors

CSS customizable

domus-push Function Audit

Discovered 8 repos missing from domus-push function:

Missing:
- domus-antora-ui
- domus-gabriel-docs
- domus-ise-windows
- domus-linux-ops
- domus-math
- domus-musica
- domus-python
- domus-siem-ops

Cloudflare API Token Permissions Fix

Issue

netapi cloudflare pages deployments returned 403 Forbidden:

HTTPError: 403 Client Error: Forbidden for url:
https://api.cloudflare.com/client/v4/accounts/.../pages/projects/domus-docs/deployments

Root Cause

CF_API_TOKEN was missing Pages permission. Original permissions:

  • Access: Apps and Policies:Edit

  • Cache Purge:Purge

  • Cloudflare Pages: MISSING

Resolution

  1. Go to dash.cloudflare.com/profile/api-tokens

  2. Edit token

  3. Add: Account → Cloudflare Pages → Read

  4. Save

Verification

# Quick API test
curl -s -H "Authorization: Bearer $CF_API_TOKEN" \
  "https://api.cloudflare.com/client/v4/accounts/<account-id>/pages/projects" | jq '.success'
# Returns: true

# Full deployment list
netapi cloudflare pages deployments domus-docs -n 5

# Get full IDs (table truncates)
netapi cloudflare pages deployments domus-docs -n 5 --json | jq '.[].id'

Token Permissions Reference

Permission Scope Required For

Zone:Cache Purge:Edit

All zones

netapi cloudflare purge

Zone:DNS:Edit

All zones

netapi cloudflare dns

Account:Access:Edit

Account

netapi cloudflare access

Account:Cloudflare Pages:Read

Account

netapi cloudflare pages deployments

Cloudflare netapi-docs Enhancement

Added deployment status documentation to cloudflare-commands.adoc:

  • Example output for pages deployments

  • Status value definitions (success, active, failure, idle, canceled)

  • Single deployment query with JSON schema

  • CI/CD polling script for automation

  • Troubleshooting section for common failures

Session: domus-linux-ops Comprehensive Documentation

Overview

Filled 14 stub pages in domus-linux-ops with production-grade documentation. Goal: documentation quality that exceeds RHEL and Arch wikis to help the community.

Pages Completed (14 Total)

Page Lines Coverage

nmcli.adoc

~900

NetworkManager CLI - profiles, wifi, VPN, troubleshooting

ss-ip.adoc

~850

Socket/IP diagnostics - ss, ip, routing tables

journald.adoc

~800

Journal logging - queries, filtering, persistence

lvm.adoc

~900

Logical Volume Manager - creation, expansion, snapshots

luks.adoc

~850

LUKS encryption - cryptsetup, keyfiles, recovery

firewalld.adoc

~900

RHEL firewall - zones, rich rules, direct rules

podman.adoc

~950

Container runtime - pods, systemd integration, rootless

timers.adoc

~800

systemd timers - oncalendar, persistent, transient

auditd.adoc

1,154

Linux auditing - rules, ausearch, CIS/PCI-DSS compliance

nftables.adoc

1,138

Packet filtering - tables, chains, sets/maps, NAT

tcpdump.adoc

981

Packet capture - BPF filters, tshark, Wireshark

boot.adoc

921

Boot troubleshooting - GRUB, initramfs, emergency mode

performance.adoc

813

Performance analysis - USE method, profiling, BPF tools

system-hardening.adoc

852

System hardening - sysctl, SSH, SUID, AIDE integrity

Documentation Structure Pattern

Each page follows consistent structure:

  1. Quick Reference - Essential commands with examples

  2. Understanding - Architecture, concepts, how it works

  3. Core Operations - Common tasks with step-by-step

  4. Advanced Features - Power-user techniques

  5. Troubleshooting - Common issues and solutions

  6. Quick Command Reference - Copy-paste cheatsheet

Commit Details

commit 1896aa9
docs: Add comprehensive documentation for 14 stub pages

Pages filled with production-grade content:
- networking/connectivity/nmcli.adoc (~900 lines)
- networking/connectivity/ss-ip.adoc (~850 lines)
- server/logging/journald.adoc (~800 lines)
- storage/volumes/lvm.adoc (~900 lines)
- storage/encryption/luks.adoc (~850 lines)
- networking/firewall/firewalld.adoc (~900 lines)
- containers/runtime/podman.adoc (~950 lines)
- server/systemd/timers.adoc (~800 lines)
- security/audit/auditd.adoc (1,154 lines)
- networking/firewall/nftables.adoc (1,138 lines)
- networking/analysis/tcpdump.adoc (981 lines)
- troubleshooting/system/boot.adoc (921 lines)
- troubleshooting/system/performance.adoc (813 lines)
- security/hardening/system-hardening.adoc (852 lines)

15 files changed, 12966 insertions(+), 133 deletions(-)

Remaining Stub Pages (20)

Category Pages

Security

certificates.adoc, apparmor.adoc, namespaces.adoc

Storage

btrfs.adoc, zfs.adoc, device-management.adoc

Containers

docker.adoc, rootless.adoc, systemd-integration.adoc

Virtualization

libvirt.adoc, kvm/networking.adoc

Desktop

hyprland.adoc, wayland-essentials.adoc, xdg.adoc

Troubleshooting

display.adoc, audio.adoc, network.adoc, selinux.adoc

Server

server/tuning/performance.adoc

Reference

cheatsheet.adoc

CRITICAL: ISE RADIUS Data Missing (Work)

Symptoms

Discovered: 2026-02-13

ISE PAN UI observations:

  1. Live Logs: Entries appear in RADIUS Live Logs

  2. Detail View: Clicking any entry shows: "No Data available for this record. Either the data is purged or authentication for this session record happened a week ago. Or if this is an 'PassiveID' or 'PassiveID Visibility' session, it will not have authentication details on ISE but only the session."

  3. Reports > Endpoints and Users:

    • RADIUS Accounting: No endpoints (30-day window)

    • RADIUS Authentications: No endpoints (30-day window)

Deployment Architecture

ISE Distributed Deployment
D2 Source Location

pages/2026/02/diagrams/ise-distributed-deployment.d2

Render: d2 --theme 200 ise-distributed-deployment.d2 ../../images/diagrams/ise-distributed-deployment.svg

PSN Roles:

Node Personas

PSN-1

Session, Profiler, SXP, Policy Service, pxGrid

PSN-2

Session, Profiler, SXP, Policy Service, pxGrid

PSN-3

Session, Profiler, SXP, Policy Service, pxGrid

PSN-4

Session, Profiler, SXP, Policy Service (NO pxGrid)

Status: All deployment nodes show GREEN

Home Enterprise ISE Diagram

ISE Home Enterprise Deployment
D2 Source Location

pages/2026/02/diagrams/ise-home-deployment.d2

Render: d2 --theme 200 ise-home-deployment.d2 ../../images/diagrams/ise-home-deployment.svg

Key observation: Nodes healthy but data missing = logging/collection issue, NOT node health issue.

Focus investigation on: - PSN → PMNT syslog delivery - PMNT database write operations - Collection Filters configuration - Data Purge settings

This is NOT Normal

Live logs should always have corresponding detail records for recent authentications. 30-day reports being empty indicates:

  • MnT database not receiving/storing data

  • Data purge policy misconfigured

  • Database corruption

  • Replication failure between PAN and MnT nodes

Investigation Steps

# Check MnT database status
# (from ISE CLI)
show application status ise

# Check purge settings
# Administration > System > Maintenance > Data Purge

# Check disk usage on MnT node
show application disk-usage

# Verify data collection is enabled
# Administration > System > Settings > Logging > Collection Filters

Potential Root Causes

Cause Indicators Resolution

Data Purge Too Aggressive

Purge window < 30 days

Increase retention in Data Purge settings

MnT Database Full

Disk at 90%+ capacity

Increase disk, archive old data

Collection Filters

Certain log types filtered out

Review Collection Filters settings

Database Corruption

Application errors in logs

Support case, possible restore from backup

Node Sync Issues

PAN/MnT replication errors

Check node health, resync

TAC Case

  • Open TAC case for ISE RADIUS data missing

  • Attach support bundle from PMNT

  • Document timeline: when did reports last show data?

CLI Diagnostic Commands (Run on PMNT)

SSH to PMNT and run these in order:

1. Application & Service Status

# Overall ISE application status
show application status ise

# Check if all services are running
show application status ise | grep -i "not running\|stopped\|error"

2. Disk Usage (Critical for MnT)

# Disk usage summary
show disk-usage

# Detailed filesystem usage
show disk-filesystem

# Check if any partition is >80%
show disk-usage | grep -E "[89][0-9]%|100%"

3. Database Health

# Database status
show database status

# Database size
show database size

# Check for database fragmentation/errors
show database health

4. Logging & Collection Status

# Check logging targets (where PSNs send logs)
show logging application

# Check log collection status
show collector-queue status

# Check if queue is backed up
show collector-queue size

5. MnT Sync & Replication

# Check node synchronization
show mnt-sync status

# Check replication between PMNT and SMNT
show sync status

6. Process/Memory (if suspecting resource issues)

# Memory usage
show memory

# CPU utilization
show cpu usage

# Running processes
show process status ise

7. Recent Errors in Logs

# Last 100 lines of MnT logs
show logging application last 100 mnt

# Check for database errors
show logging application last 100 | grep -i "database\|oracle\|ORA-"

# Check for disk/write errors
show logging application last 100 | grep -i "disk\|write\|space\|full"

8. Purge Job Status

# Check scheduled purge jobs
show purge-status

# Check last purge run
show logging application last 200 | grep -i purge

Quick Copy-Paste Block (Run All)

show application status ise
show disk-usage
show database status
show database size
show collector-queue status
show mnt-sync status
show memory
show logging application last 50 | grep -i "error\|fail\|ORA-"

GUI Checks (Before CLI)

Setting Path What to Look For

Data Purge

Administration > System > Maintenance > Data Purge

Retention period (should be >30 days for your issue)

Collection Filters

Administration > System > Settings > Logging > Collection Filters

Any filters blocking RADIUS auth data

Remote Logging Targets

Administration > System > Logging > Remote Logging Targets

Verify PSNs are configured to send to PMNT

Log Categories

Administration > System > Logging > Logging Categories

RADIUS Accounting and Authentication enabled

MnT Node Config

Administration > System > Deployment

Verify PMNT has "Enable Monitoring" checked

Investigation Checklist

  • Check Data Purge settings (Administration > System > Maintenance > Data Purge)

  • Check MnT disk usage (show disk-usage)

  • Review Collection Filters (Administration > System > Settings > Logging)

  • Verify PSN → PMNT syslog config

  • Check PMNT application logs for database errors

  • Run CLI diagnostic commands above

  • Capture output for TAC case

BUG FIX: Antora UI Bundle Inconsistency Across domus-* Repos

Issue Discovered

While creating domus-o11y-ops (new observability documentation repo), discovered that 9 standalone playbooks were using the wrong UI bundle.

Root Cause

Repos were using the default Antora UI from GitLab instead of the custom domus-antora-ui bundle:

# WRONG - Default Antora UI (GitLab)
ui:
  bundle:
    url: https://gitlab.com/antora/antora-ui-default/-/jobs/artifacts/HEAD/raw/build/ui-bundle.zip?job=bundle-stable
    snapshot: true

# CORRECT - Custom domus-antora-ui
ui:
  bundle:
    url: https://github.com/EvanusModestus/domus-antora-ui/releases/latest/download/ui-bundle.zip
    snapshot: true

Impact

  • Standalone builds looked different from production (domus-docs)

  • Visual inconsistency during local development

  • No cross-reference breakage (component names unchanged)

Affected Repos (9 total)

Repo Status

domus-automation-ops

Fixed

domus-gabriel-docs

Fixed

domus-identity-ops

Fixed

domus-infra-ops

Fixed

domus-ise-ops

Fixed

domus-linux-ops

Fixed

domus-netapi-docs

Fixed

domus-python

Fixed

domus-secrets-ops

Fixed

Repos Already Correct

Repo UI Bundle

domus-captures

../domus-antora-ui/build/ui-bundle.zip (local)

domus-docs

./ui-bundle.zip (fetched by build.sh)

domus-ise-linux

Absolute local path

domus-o11y-ops

GitHub releases URL (new)

Fix Applied

# Command used to fix all repos
old_url="https://gitlab.com/antora/antora-ui-default/-/jobs/artifacts/HEAD/raw/build/ui-bundle.zip?job=bundle-stable"
new_url="https://github.com/EvanusModestus/domus-antora-ui/releases/latest/download/ui-bundle.zip"

for playbook in "${repos[@]}"; do
    sed -i "s|$old_url|$new_url|g" "$playbook"
done

Verification

# Verify no repos using GitLab default
find ~/atelier/_bibliotheca/domus-*/ -name "antora-playbook.yml" \
    -exec grep -l "gitlab.com/antora/antora-ui-default" {} \;
# Result: No matches (all fixed)

# Count repos using domus-antora-ui
find ~/atelier/_bibliotheca/domus-*/ -name "antora-playbook.yml" \
    -exec grep -l "domus-antora-ui" {} \; | wc -l
# Result: 12 repos

Prevention

When creating new domus-* repos, always use:

ui:
  bundle:
    url: https://github.com/EvanusModestus/domus-antora-ui/releases/latest/download/ui-bundle.zip
    snapshot: true

Related: domus-o11y-ops Structure Fix

Also fixed antora.yml location:

# WRONG (root level)
domus-o11y-ops/antora.yml

# CORRECT (matches other repos)
domus-o11y-ops/docs/asciidoc/antora.yml

This ensures start_path: docs/asciidoc works correctly in domus-docs aggregator.

Session: domus-o11y-ops and Load Balancing Documentation

New Repo: domus-o11y-ops

Created observability documentation component:

Section Pages

Prometheus

index, installation, configuration, promql, exporters, federation

Grafana

index, installation, dashboards, datasources, provisioning

Loki

index, installation, logql, promtail

Alerting

index, alertmanager, rules, routing

New Section: domus-linux-ops/networking/loadbalancing

Added load balancing documentation:

  • index.adoc - Overview, architecture patterns

  • haproxy.adoc - TCP/HTTP load balancing, ACLs, stats socket

  • nginx-lb.adoc - Upstream configuration, health checks

  • keepalived.adoc - VRRP failover, virtual IPs

  • ssl-termination.adoc - TLS offloading

Integration Pending

To complete domus-o11y-ops integration:

# 1. Initialize git repo
cd ~/atelier/_bibliotheca/domus-o11y-ops
git init && git add -A
git commit -m "feat: Initial observability documentation"

# 2. Create GitHub repo
gh repo create domus-o11y-ops --private --source=. --push

# 3. Add to domus-docs/antora-playbook.yml
# - url: https://github.com/EvanusModestus/domus-o11y-ops
#   branches: main
#   start_path: docs/asciidoc
#   edit_url: false

Pending Tasks

  • Practice Spanish oral presentation

  • SIEM gap analysis - review QRadar skills

  • Xianming Ding Linux researcher request

  • Continue domus-siem-ops content development

  • Update domus-push function with missing repos

  • Fill 14 domus-linux-ops stub pages (12,966 lines)

  • Fill remaining 20 domus-linux-ops stub pages

References