Nathen Harvey

In early January, we quietly added native support for Tracing with OpenTelemetry to Sematext. 🚀 Let me skip the usual blah blah about OTel and no vendor lock-in and such and jump straight to what you get. Links at the bottom. 💰50–80% lower cost than Datadog, New Relic, Dynatrace or Grafana Cloud This is self-explanatory. :) ... and may be enough for some folks to give it a go. ✅ Really dead-simple setup If you’re already using OpenTelemetry, you’re already set! Sematext Agent acts as the Collector. It exposes HTTP and gRPC endpoints. Just point your instrumentation SDK at the agent. ✅ Immediate out of the box insights For each service see RED metrics (rate, errors, duration), see slow traces, alerts, overall latency distribution, top slow endpoints, health of each service… ✅ Intuitive, SRE-friendly UI Fast, clean and modern UI. Quickly drill from service → endpoint → trace → span. ✅ Auto-instrumentation out of the box For languages/runtimes and frameworks that have auto-instrumentation just use that. For others, instrument manually. All instructions are copy/paste in the UI. Some links: - docs: https://lnkd.in/e5mh_nzW - some screenshots: https://lnkd.in/eZZs5757  - agent & OTel: https://lnkd.in/euE2nDdP - product info: https://lnkd.in/erhEK6SJ #OpenTelemetry #Tracing #Observability #DevOps #SRE #SoftwareEngineering #Microservices #Monitoring #Sematext

44

In 2023, three engineers walked out of the AWS halls in Tel Aviv and into a problem no one else was brave, or crazy, enough to fix: cloud storage waste. You know the kind. You're running EBS volumes on AWS, watching your cloud bill light up like a pinball machine, and no matter how many dashboards you stare at, the costs never scale down. Zivan Ori, Ziv Serlin, and Yoav Ilovich didn't just see the bloat, they lived it. These guys didn't pivot into cloud. They built it. Ori and Serlin co-founded E8 Storage, sold it to AWS, then led the EBS dev team from the inside. Ilovich ran product at Taboola, Pagaya, and Fleetonomy before Via scooped that one up. These aren't tourists. They're locals in the cloud chaos. So they founded Datafy, because apparently, "Autonomous Storage Scaling for People Who'd Rather Not Light Their Money on Fire" didn't fit on the AWS Marketplace listing. And let's talk results. Via Transportation plugged in and saw fully #automatedstorage scaling with zero downtime. H2O.ai cut EBS costs by 40% without giving up an ounce of flexibility. This isn't a maybe. It's a matter of math. The kind that gets you up to 60% in cost savings, zero engineering hours to implement, and a system that scales without that 3 a.m. Slack ping from DevOps. One line of code. No lifting. No guessing. No "best practices" PDF to forget you bookmarked. Investors didn't need a TED Talk to catch the signal. Bessemer Venture Partners led the new $20 million seed round, yes, a seed round. When you've got Adam Fisher, who's helped push over a dozen Israeli startups to the exit sign, betting on your math, you're not raising for hype. You're raising because the numbers demand it. Insight Partners doubled down, with Liad Agmon, of Dynamic Yield by Mastercard and McDonald's $300 million acquisition fame, coming back for more. When return investors show up with bigger checks, they're not following the trend. They're following conviction. So what's next? Datafy's headed straight into the U.S. market, where #AIinfrastructure is scaling like a startup at an open bar. Their platform already runs on any Linux distro, works seamlessly with EC2, EKS, ECS, and is 100% #SOC2 compliant. No recommendations. No dashboards begging for your attention. Just cold, hard optimization, running on a low-level storage engine that does what most humans can't, or won't. This isn't a product. It's a wake-up call for every AWS-heavy startup bleeding budget without even knowing it. Enterprises building in #AI, transportation, and big data better take note: the cloud's been playing you. Datafy is the fix. #Startups #StartupFunding #VentureCapital #SeedRound #Cloud #CloudCompute #CloudComputing #CloudCostOptimization #Storage #Data #DataDriven #Infrastructure #Technology #Innovation #TechEcosystem #StartupEcosystem If engineering peace of mind is what you crave, Vention is your zen.

3

Day 2 — Modernization Is Not Migration. It’s Momentum. If Post 1 was about why data platforms feel harder than they should, this post is about moving forward without breaking things. In my conversations with CRIS, one theme was very clear: “We can’t afford big-bang cutovers anymore.” Everyone has lived this story at least once: • long “freeze” windows • weekend cutovers that spill into Monday • parallel systems nobody fully trusts • teams praying the rollback plan stays on the whiteboard That’s not modernization. That’s survival. When we dug deeper with CRIS, we explored a different model: 🔹 Modernization as a continuous flow, not a one-time event. 🔹 Near-zero downtime as a design goal, not a miracle. On the EDB PG AI Platform, that looked like: • Using a Migration Copilot to guide the journey step by step • Streaming data from existing systems into Postgres with near-zero downtime • Keeping applications online while schemas evolve • Treating upgrades and patching as routine, not crisis projects • Pulling in data from external sources without constant manual plumbing The result isn’t just a “new database”. It’s a different rhythm: • Change becomes smaller and safer • Risk becomes managed, not avoided • Teams stop arguing about when to modernize and start asking what’s next Modernization is not about leaving something behind. It’s about unlocking what comes after. With CRIS, the most energizing part wasn’t the tools themselves — it was the realization that they don’t have to choose between stability and progress. In the next post, I’ll talk about where this leads: how operational and transactional data can start powering ML models, AI agents, and support experiences built on real, trusted data. For now: Modernization isn’t a cutover date on a slide. It’s the moment your platform starts supporting continuous change instead of resisting it. #Modernization #DataPlatforms #PostgreSQL #EDB #PGAI #EnterpriseIT #TechLeadership #CRIS

13

By making our RouteSavvy API PLUS available on Microsoft Marketplace, it's now easier than ever for Azure customers to start harnessing the power of OnTerra's advanced multi-vehicle route optimization service. Whether you're a small, medium or large organization that is trying to modernize and scale your delivery, logistics, field services, sales routes, or fleet management operations, RouteSavvy API PLUS is a customer-proven solution to consider. To learn more, go to OnTerra's RouteSavvy API PLUS offering page on Microsoft Marketplace at https://lnkd.in/gYGeQ57j.

16

1 Comment

From thousands of conversations, most outbound teams don't lack tools. They lack a single layer that ties everything together. We fixed that this week by connecting Claude to the entire Forge Stack via the Salesforge MCP server. Here's what that actually means: Claude now has live access to: → Every campaign, sequence, and sending account → Inbox activity, warm-up behavior, deliverability signals → Lead segments, enrichment data, infra config → Performance gaps across the whole system Instead of jumping between dashboards, you ask a question. Claude organizes the data, surfaces what matters, and tells you exactly what to fix. Simply put, Salesforge MCP + Claude = More 🥓 made We built 5 core workflows around this: 1. Campaign Usage Monitor 2. Performance Analyst 3. Campaign Health Dashboard 4. Infrastructure & Inbox Monitor 5. Full Outbound Audit Report Each one is a single prompt. Each one replaces hours of manual review. This isn't reporting. It's your outbound operating system. Full guide with workflows, prompts, and setup guide prepped for you. Comment “Claude” below and I’ll send you the guide. P.S Repost for priority access 🥓

51

34 Comments