Presenters
Source
Beyond Code: How Drive Terra Empowered Their Entire Company with Observability 🚀
Ever been on the receiving end of a “We need to monitor our data!” request? You’re not alone. In the fast-paced world of tech, product, business, and leadership teams often demand visibility into operations. But what happens when that demand stretches beyond the realm of software engineers and SREs?
At Drive Terra, they faced this exact challenge. They’re not just another software company; they’re revolutionizing urban mobility with electric bikes that utilize swappable batteries. This intricate ecosystem involves a complex interplay of hardware, operations, and business stakeholders, all needing a clear view of what’s happening on the ground.
The Drive Terra Ecosystem: More Than Just Bikes 🚴♀️⚡️
Drive Terra’s operation is a symphony of moving parts:
- The Core: A network of stations housing batteries for quick swaps, a fleet of bikes, a robust cloud infrastructure, and a user-friendly mobile app.
- The Ground Game: Extensive operations ensuring everything runs smoothly.
This complex system relies on a diverse team:
- Engineers: Software, IoT, hardware (firmware, connectivity, devices), and electrical engineers (battery cells, charge cycles) work hand-in-hand.
- Mechanical Engineers: They ensure the bikes themselves are in top condition, from gears to steering.
- Operations: Fleet managers keep the bikes on the road, logistic coordinators manage battery charging and station logistics, maintenance teams handle repairs, and warehouse/inventory teams manage stock.
- Leadership: The CEO seeks overall visibility, partners managers track specific partner fleets (like Amazon, Kareem, Uber), and the finance team monitors KPIs.
- Partners: They need to see their drivers and bikes operating efficiently.
The Observability Chasm: Bridging the Technical and Non-Technical Divide 🌉
The biggest hurdle? The disconnect between non-technical teams (operations, leadership, partners) and the technical teams (engineers).
- Non-Technical Needs: They crave insight into operation costs, KPIs, and require weekly reports. The old way involved clunky Excel sheets.
- Technical Capabilities: Engineers could track IoT devices, servers, and the electrical systems within the bikes.
- The Pain Point: When a partner called asking about a specific bike’s downtime, getting a clear, real-time answer was a challenge.
This is where the concept of observability proved to be a game-changer, extending far beyond its traditional engineering roots.
Grafana: The Unsung Hero of Company-Wide Visibility ✨
Drive Terra’s solution? Grafana. Initially met with skepticism (“You are crazy to do this!”), the implementation of Grafana transformed their approach to monitoring.
Key Features and Benefits:
- Real-Time Dashboards: Auto-refreshing dashboards (every 30 seconds, 5 seconds, or even 1 second!) provide live insights.
- Digital Twin in Grafana: They’ve effectively created a full digital twin of their operations, allowing everyone to understand hardware performance, fault by fault.
- Battery Monitoring: Visualize the status of the two batteries in each bike and track their lifecycle across bikes and stations.
- IoT Data Integration:
- An IoT box in each bike captures GPS data every 10 seconds, along with voltage, charge cycle, fault codes, and motor data.
- Data is livestreamed to servers using MQTT.
- MongoDB stores IoT data, while PostgreSQL handles metadata and inventory.
- RabbitMQ plays a role in their data pipeline.
- Out-of-the-Box Alerts: Grafana’s alerting system allows for immediate notifications, mirroring the need for on-call engineers with on-call battery or station operators to manage critical situations, especially in harsh environments like Dubai’s heat.
- Interactive Dashboards: Station operators can even control functionalities like starting or stopping a process directly from Grafana via API calls, eliminating the need to access a separate, complex system.
The Journey of Implementation: From One Use Case to Company-Wide Adoption 🗺️
Drive Terra’s path to comprehensive observability was iterative and collaborative:
- Start Small: They began with a single, critical use case: battery health.
- Expand Scope: They then moved to fleet status.
- Iterate and Gather Feedback: The key was to pick any KPI, build a dashboard, gather feedback from the team, and refine it.
- Empower Non-Technical Teams: While technical teams can leverage existing templates, building dashboards for non-technical users was the “hard part” but crucial for success. The non-technical team became their champion.
The Big Takeaway: Observability is for Everyone! 💡
The most profound lesson learned at Drive Terra is that observability is not just for engineers; it’s for the entire company. From the CEO to every employee, having a clear, accessible view of operations fosters better decision-making, faster problem-solving, and ultimately, a more efficient and successful business.
So, the next time you hear the call for monitoring, remember Drive Terra’s journey. With the right infrastructure, database, and data pipeline, you can achieve company-wide visibility and keep everyone fully charged!