bleemeo (@bleemeo) header
bleemeo (@bleemeo) profile picture

Servers, Containers, and Applications monitoring made easy. #DevOps #Monitoring #Observability #Cloud

Toulouse, France
Joined March 2015
Photo by bleemeo (@bleemeo)Photo by bleemeo (@bleemeo)Photo by bleemeo (@bleemeo)Photo by bleemeo (@bleemeo)Photo by bleemeo (@bleemeo)Photo by bleemeo (@bleemeo)Photo by bleemeo (@bleemeo)Photo by bleemeo (@bleemeo)Photo by bleemeo (@bleemeo)Photo by bleemeo (@bleemeo)
πŸ”• An anomaly is not a severity. Severity: "something is wrong, a human must act now." Rare. Pages. Anomaly: "this is different from usual." Frequent. Context. Page on "unusual" and your team learns to sleep through the pager.
1
13
☁️ New in Bleemeo: Azure. VMs, SQL Database, Cosmos DB, Load Balancers, Blob Storage, Functions and your Azure spend, on the same dashboards as your servers. Read-only (Monitoring Reader), auto-discovery, three steps. bleemeo.com/solutions/azure-…
1
1
42
🧠 New in Bleemeo: anomaly detection. CPU, memory and swap on every server, learned from 2 weeks of their own daily and weekly rhythm. No threshold to set. It never pages anyone. And each anomaly shows how long before an alert followed. bleemeo.com/features/ai-mach…
1
2
94
πŸ“… "Disk at 74%" is a reading. "90% on Dec 3" is a decision. Percentage thresholds fire for weeks on slow disks and with minutes left on fast ones. Project the trend to a date β€” and check it held before you believe it.
1
2
19
πŸ₯¨ Day two at PromCon Munich β€” we're here all day, come say hi. Yesterday's lightning talk: Prometheus long-term storage on ClickHouse. Native TimeSeries engine, SSD β†’ HDD β†’ S3 tiering in one TTL, SQL next to PromQL. Slides + snippets: bleemeo.com/events/promcon-e…
2
61
β›΅ Four days out of range for the Bleemeo seminar in Porquerolles β€” sailing, coastal paths, and the year's hard questions taken outdoors. A monitoring company going somewhere with patchy signal is absurd. It's also the last place on earth where nobody can push to prod. πŸ˜„
1
4
40
πŸ“š The three pillars, minus the buzzword: πŸ“Š Metrics β†’ THAT it broke πŸ“œ Logs β†’ WHAT broke πŸ•ΈοΈ Traces β†’ WHERE the time went Start at the metric, drill into the trace, confirm in the logs. Teams that start in the logs spend the whole incident grepping. πŸ” bleemeo.com/resources/devops…
1
2
23
bleemeo retweeted
New integration announcement πŸ“£ ilert + Bleemeo! @Bleemeo is a French monitoring platform, built in Toulouse since 2015, covering servers, containers and applications on open standards like Prometheus, with data hosted entirely in the EU. It now connects natively to ilert: threshold breaches reach the responder on duty through your escalation policy, and alerts close automatically once the issue clears. Two European vendors, one alerting chain that never leaves the EU. Learn more here: eu1.hubs.ly/H0yt5Cg0
2
4
73
🀝 New: Bleemeo Γ— @ilerthq A native Bleemeo alert source in ilert, a native ilert integration in Bleemeo. No webhook, no payload template β€” you copy one key. Bleemeo decides something is wrong. ilert decides who gets woken up about it. πŸ“ž bleemeo.com/blog/ilert-partn…
1
2
36
β˜€οΈ Back at your desk. Nothing broke in August β€” it just drifted. The 30-min audit: 1. read what fired while you were away, bin the noise 2. list what expires before December 3. un-summer the on-call rota 4. page yourself, watch where it lands Cheaper now than in October.
1
3
34
πŸŒ™ 2am, something's broken. Five steps, every time: 1️⃣ Detect 2️⃣ Triage 3️⃣ Mitigate βͺ 4️⃣ Resolve 5️⃣ Learn The one everyone gets wrong: 3 before 4. Roll back BEFORE you understand. Customers stop hurting at step 3.
1
2
15
πŸ“± Bleemeo mobile now has home screen widgets β€” iOS and Android. 🟒 Account health: check donut, worst status, total (+ iOS lock screen) πŸ“Š Agent: CPU / mem / disk / load for one server πŸ”„ Every 15 min, instantly on an alert push App 15.0 β†’ docs.bleemeo.com/mobile-appl…
1
1
65
🧨 Labels don't add up in Prometheus. They multiply. 3 jobs Γ— 12 instances Γ— 5 statuses = 180 series. Fine. Add user_id (40k values) β†’ 7,200,000 series. Same metric, same traffic, OOM at 2 a.m. πŸ”₯ If you'd never "sum by" it, it's not a label β€” it's a log line. πŸ“œ
1
2
34
πŸ–₯️ The corridor TV with 24 graphs that nobody reads: you put a dashboard on a wall. Different object, different rules. πŸ“ legible at 5 meters 🍯 state, not curves πŸ• a clock β€” or "all green" and "frozen since Tuesday" look identical 🚫 zero interaction github.com/bleemeo/dashglass
1
3
67
πŸ”” Most alerts are noise β€” and noise trains your team to ignore the real page. 😴 A good alert: πŸ“Š fires on a symptom users feel (not a lone CPU spike) ⏳ waits ("for: 5m") so blips don't page πŸ“© says what broke, where, how bad One good alert beats twenty nobody reads. πŸ—‘οΈ
1
2
48
πŸ“Š "We target 99.9% uptime." That's 43 minutes a month. Not a slogan β€” a budget. πŸ’° πŸ”΅ 99% β†’ 7h 12m 🟒 99.9% β†’ 43m 🟠 99.99% β†’ 4m 19s Budget left? Ship. Budget gone? Stabilise. And 100% isn't a target, it's paralysis. 🧊
1
2
31
πŸš€ We just open-sourced DashGlass: Grafana-style dashboards, as code. πŸ“¦ single Go binary, no database πŸ“„ one dashboard = one clean file β†’ 1-line diffs 🌿 edit in the UI, review in git πŸ” PromQL-native + Grafana import Apache 2.0, self-hostable: github.com/bleemeo/dashglass
1
5
171
⏰ The 3am "disk full" page has a one-line fix. Don't alert on "disk > 90%" β€” it fires too late, or too often. Alert on the trend: predict_linear(disk_used_perc[6h], 4*3600) >= 100 = "will it hit 100% in the next 4h?" πŸ“… Hours of warning, not minutes.
1
2
23
πŸ“± It's 2am. Your phone buzzes. Do you: πŸš’ grab the laptop 🧘 check if it self-healed πŸ“Š open the dashboard πŸ›‘οΈ follow the runbook Find your type in our free Summer Workbook β˜€οΈ β€” the (very serious 😌) SRE personality quiz. Which one are you? πŸ‘‡ bleemeo.com/resources/devops…
1
2
35
🎯 You can't watch every metric. Google's SRE team cut it to four: ⏱️ Latency (p95, not average) πŸ“ˆ Traffic (req/s) πŸ”΄ Errors (5xx rate) 🌑️ Saturation (CPU/mem/disk) Latency + Errors = what users feel. Traffic + Saturation = what the box is doing.
1
2
39