BlaBlaCar offers a ridesharing service, connecting people who need to travel with drivers who have empty seats. BlaBlaCar has now become the world’s leading long-distance ridesharing platform. We’ve all heard of them and the $200 million they raised last summer, prompting internationally famous magazines, such as Forbes and Fortune, to dub them as “Europe’s Newest Unicorn”. Of course, their success is awe-inspiring, and we are proud to be working with them.
So we met with Saad Bouchehboun, the Technical Manager at BlaBlaCar, who told us about his mission and how he is using Logmatic.io’s platform to help him get ahead. This is what Saad told us:
“The member is the boss”
With more than 20 millions users, ensuring our app is performing correctly is absolutely key to the quality of our service. In fact, proper performance isn’t enough. Making sure everything goes as smoothly as possible for our members is engraved in our DNA: “the member is the boss” is one of our mottos – it pushes us to constantly innovate.
With monitoring dashboards on screens in our offices, our developers, lead devs and architects all use Logmatic.io as a day-to-day alerting system to assist us in our work.
Making deployment fixes for payment and mobile easier
The developers of our payment backend and BlaBlaCar mobile app all use the Logmatic.io log analyzer to check that the code they delivered is behaving appropriately. Constantly watching over their monitoring screen, our payment team monitors metrics while mobile devs use it mainly to watch for API alerts and errors, and to monitor each country separately.
Now that devs get alerts and can see what is happening down at the log level, they are completely autonomous. Before, they needed to ask architects to create a specific dashboard that would isolate the problem on ELK, which took several minutes. Devs were losing time, architects were losing time, whereas now devs have access to the right information on their own, with just one tool, in just a few minutes. So developers can improve their code and deployment autonomously.
Isolating countries and monitoring latency
Architects at Blablacar take care of infra, network and ops. Their job is at the heart of our activity, and their time is precious. So it’s very good news our devs don’t have to ask them for information when the deployed code is not behaving properly!
We need to be able to monitor each country’s access to our servers to ensure our members in each country always have good access to our service, which is just what Logmatic.io provides us with – an efficient log management system. Before working with them, we were using ELK in our log system: at that time, it was complicated to make it work properly, we couldn’t create alerts, and creating monitoring dashboards is not as intuitive as with logmatic.io. Architects were fully booked and did not have the time to properly work on the logging entries.
Also, to ensure a good member experience within our BlaBlaCar app, we need to know how long it takes a member to see their search results. So we need to calculate the real latency, including the one coming from our members’ side. We chose to send our mobile apps logs to Logmatic.io to answer that question because of its alerting capabilities, and the dashboards that are easy to create. With Logmatic.io, we get very granular information that reduces the bug fix time.
So for example, one evening last week, Logmatic.io log analyzer saw the number of errors of an API call had multiplied by four. We were able to look at the dashboard and directly filter information to look at different metrics. We understood right away the exact delimited case that had created it and we fixed it right away.
Logmatic.io has enabled us to have dashboards representing calls per API and define alerts on them. We are now alerted very early on about production problems, and we have time to get things in hand several minutes before they affect a large number of members. This of course prevents them having a bad user experience and contacting our Member Relations team.
Facilitating collaboration on security with our Member Relations team
Many interactions with our Member Relations team are now much easier, as we can easily find the information they need. They, in turn, get fast and clear answers and can move on to other topics – all thanks to log management.
With regard to one of Logmatic.io‘s new releases, we are now working on the creation of error alerts over certain percentages.
Besides, we are considering to pour data coming from Logmatic.io into some of our own internal tools so that other departments can better access this new type of data and get the most of log analytics.
Left wanting to see how Logmatic.io looks like? Have a quick look at our platform videos on our Product page. Or maybe you’re interested in reading more of our customers use cases? Pick the story you’re interested in on our Use cases page.