🚨 Severity: awesome. You've been paged — welcome to my profile! 👋
All systems operational. This profile is monitored 24/7 by caffeine-driven synthetic checks.
| Service | Status |
|---|---|
| 🔭 Observability & Monitoring Dashboards, alerts & pipelines at scale · 3+ yrs uptime |
 |
| 🚨 Incident Response Root cause over quick fixes · MTTR ↓ |
|
| 📐 SLI / SLO Engineering Latency · traffic · errors · saturation · 99.9% |
|
| ☁️ Cloud & IaC AWS · GCP · Terraform / OpenTofu · plan ✔ |
|
| 📚 Learning Pipeline Always shipping new skills · continuous |
 |
| ☕ Coffee Saturation Refill scheduled, no action needed · < 90% |
 |
apiVersion: human/v1
kind: SiteReliabilityEngineer
metadata:
name: fabian-m
namespace: santiago-chile 🇨🇱
labels:
role: sre
specialty: observability
experience: 3y+
spec:
education: Computer Engineer @ Duoc UC 🎓
languages:
- Spanish (native) 🇨🇱
- English (professional) 🇺🇸
focus:
- High-Availability Systems
- Golden Signals
- SLI/SLO & MTTR Optimization
- Incident & Root Cause Analysis
status:
phase: Running ✅
workingOn: 🔭 Observability at scale
askMeAbout:
- SLOs
- Grafana
- Incident Management
- Alert noise reductionflowchart TD
A["⚙️ Services<br/>K8s · RabbitMQ · Redis · AWS"] --> B["📡 Metrics<br/>Prometheus · Datadog"]
A --> C["📜 Logs<br/>Loki · Splunk"]
B --> D["📊 Grafana dashboards"]
C --> D
D --> E{"🎯 SLO breached?"}
E -- no --> F["😴 Sleep well"]
E -- yes --> G["🚨 Correlate · BigPanda"]
G --> H["🧑🚒 Respond · ServiceNow"]
H --> I["📝 Postmortem & RCA"]
I -. "improve" .-> A
classDef ok fill:#064E3B,stroke:#10B981,color:#fff
classDef alert fill:#7F1D1D,stroke:#EF4444,color:#fff
classDef core fill:#4C1D95,stroke:#A855F7,color:#fff
class A,B,C,D core
class F ok
class G,H,I alert
Observability architecture with dashboards for K8s, RabbitMQ, Redis, AWS RDS & S3.
Root cause analysis, SLI/SLO framework & alert noise reduction.
High-availability architecture with centralized logging & synthetic monitors.
Infrastructure monitoring across multiple regions with IaC deployment.
🐍 A snake eating my contributions — the only acceptable kind of data loss.
🚨 Need an SRE? Click to open the runbook
# Step 1 — Identify the issue
$ echo "Need better observability"
# Step 2 — Escalate to the right person
$ page --to "Fabián M." --severity "let's-talk" \
--channel linkedin.com/in/fabianimv \
--fallback fabianignaciomv@gmail.com
# Step 3 — Resolution
✔ Dashboards built
✔ SLOs defined
✔ Alert noise reduced
✔ Team sleeps well
