Why New Relic
Access to powerful out-of-the-box visualizations, helpful alerts, great ease of use, advanced drilldown functions, and a single source of truth across multiple environments.
- Visibility into software performance, customer experience, and business metrics
- Empowers developers with a single source of truth
- Improves the accuracy of capacity planning ahead of high-traffic events
Baseball’s long history of innovation
America’s pastime may conjure images of pastoral afternoons quaffing beverages and noshing on hotdogs, but Major League Baseball actually boasts a long history of technical innovation. Baseball was the first sporting event broadcast on the radio in 1921 and the first sports game aired on television in 1939. In the 21st Century—thanks in good measure to MLBAM—baseball continues to be a hotbed of pushing the boundaries of cutting edge consumer technology.
Today, MLBAM is an online giant, powering some 10 million live streams daily. MLB.com estimates its owned and operated properties attracted roughly 25 million daily visitors and its wildly popular and successful MLB.com At Bat app logged more than 6.9 billion total minutes used by fans, making it the top mobile sports app in 2015. MLBAM also tracks state-of-the-art game and player analytics via Statcast powered by Amazon Web Services —made available to teams and fans through digital platforms and TV broadcasts. When the TV play-by-play announcer says a ball thrown from the shortstop to the first baseman traveled at 76 mph and hit the first baseman’s glove 37.4 milliseconds before the base runner got there, that’s data MLBAM helped measure, collect, and manage in real time.
Leveraging its market-leading expertise in digital media distribution, MLBAM has become “one of the world’s top tech players,” according to CBS News.
“[New Relic] is more than a developer tool, at this point it’s an operational tool as well,”
New Relic supports MLBAM in the cloud
Clearly, scaling is critical for MLBAM, which has led the company to embrace DevOps, the cloud, Amazon Web Services—and New Relic.
In 2014 an influx of large scale live events that needed to be executed in a short window, even sometimes simultaneously, led MLBAM to engage with AWS to handle “overflow” scaling needs, and based on that experience subsequently settled on AWS as its primary scaling strategy. However, MLBAM’s cloud vision was broader than simply accessing on-demand compute, storage, and networking resources.
“The cloud allowed us to not only scale our applications, but to scale our organization as well,” says Christian Villoslada, vice president of software engineering at MLBAM. To speed application development, the company began taking advantage of new engineering and operations tools and approaches, including DevOps and agile development. New Relic dashboards play a critical role here.
"All of a sudden it was just like the stadium lights went on and we could see the whole field. We could see every single play that was going on. It was just an awesome amount of visibility into how our stacks were performing. That’s the biggest gain that we had. I would not want that to go away."
How New Relic adds visibility
In this new model, MLBAM saw a critical need for shared, end-to-end visibility into how its apps are performing and the customer experience it was delivering. “Everything is sending data to New Relic,” says Paolo Vaca, Director of Web Software Engineering at MLBAM. “As developers work on new features, they can go to the dashboard and see if their features are having any performance impacts or if there are errors that they just can’t catch sifting through the AWS logs.”
“There were two major holes for my team,” notes Mike Lenner, vice president of software engineering at MLBAM. “One was visualization. There wasn't a way to make performance data clear, crisp, and commonly available across teams. The second issue was troubleshooting complex applications with APIs to other systems. For instance, we’d see an increase in latency, but couldn’t easily pinpoint why.”
The key is to identify and fix potential problems before users complained about them. “The earlier we can find out there’s an issue, the better our ability to preserve the customer experience,” explains Sean Curtis, senior vice president of engineering at MLBAM. “We're competing against the biggest and best platforms in the world, so you have to provide the best customer experience.”
In the beginning, that wasn’t always happening. “Information about performance issues often came from users,” recalls Shawn Will Smith, associate director at MLBAM. “Then the engineers would start trying to figure out what was going wrong.”
But with New Relic, “all of a sudden it was just like the stadium lights went on and we could see the whole field. We could see every single play that was going on,” says Vaca. “It was just an awesome amount of visibility into how our stacks were performing. That’s the biggest gain that we had. I would not want that to go away.”
New Relic helps empower MLBAM’s development teams
To better manage the cloud transition, MLBAM transferred internal ownership for all of its services away from its central operations team to the individual development teams that build each service. These largely autonomous development teams now are responsible for everything about their services: code, test, deployment, and production support.
New Relic helps the teams work together and take ownership of their services, giving them a place to compare and drill into metrics like error reporting and page load times. “What I really like,” adds Lenner, “is that it has been a cultural change too. We've definitely been more transparent amongst teams about what's going on, especially if a team that's dependent on another team's services. But also wanting to know prior to end-user customers alerting us to their issues, is first and foremost.”
As Curtis puts it: “Each team has to understand that they have to drive transparency around how well they're doing, how well they are able to measure their effectiveness within that area.”
MLBAM’s automated scoreboard
Unlike the latest fashion in ballpark design, there’s nothing manual about the performance scoreboards MLBAM built with New Relic. The company relies on a suite of New Relic products for access to an automated, full-team view of how its applications are performing.
New Relic Insights™, meanwhile, helps MLBAM to more easily surface data from other New Relic products. And because mobile app performance is so often affected by factors beyond MLBAM’s own backend, the company is now getting started with New Relic Mobile™ to track performance of its many mobile apps, says MLBAM’s Mike Leonard. New Relic Synthetics are also playing increasing roles, including for transactional synthetics monitoring, and MLBAM is currently considering generating its own custom metrics. Put it all together, and MLBAM now has access to automated cross-team views and metrics of how its applications are performing.
Because each production team owns its products and services, each is free to choose the tools that work best for them. Tellingly, however, more than 80% of MLBAM applications running in the cloud are now monitored by New Relic.
“New Relic empowers our developers to experiment and work fast without compromising on the quality of the MLB fan experience."
MLBAM uses New Relic from development through production
“We use New Relic throughout the entire development workflow,” in both pre-deployment and production servers, says Vaca. “As developers work on certain features, they can go to the New Relic dashboard and see how performance is affected,” both in testing and in the real world. New Relic is also integrated into MLBAM’s continuous delivery process, where it increases confidence in deployments, and consequently improves the frequency of software releases and updates. “New Relic empowers our developers to experiment and work fast without compromising on the quality of the MLB fan experience,” says Curtis.
Once applications are in production, New Relic helps MLBAM keep a watchful eye on performance, with New Relic Alerts™ notifying the appropriate technical teams any time a critical threshold is exceeded. “New Relic is normally the first thing that gives us that heads up,” Curtis says. “We can immediately address whatever is going on at that point without necessarily having users call in and complain,” he adds.
New Relic also helps MLBAM pinpoint issues regarding interactions with third-party services and APIs—and like many modern operations, MLBAM works with many, many outside services. “The Service Maps feature in New Relic becomes hugely important to us when there’s something critical happening,” explains Curtis. “To have a service map provide a visual of red, yellow, or green on status, including third-party services, is great because it really increases our ability to respond quickly and consistently deliver a good experience."
If things do head south, MLBAM puts customers ahead of technology. “We expect our downstream dependencies to fail.” Krone says. “We build our systems so that if we encounter a failure trying to determine if you have access, we just give you access. Customer experience first. It's so much easier to explain after the fact, ‘We had a failure, and we let some odd number of people watch when they shouldn't have," versus, ‘We blocked everyone out.’”
“There’s always a state of change, so measurement becomes even more important, and harder to do well, in an environment that's entirely dynamic. New Relic collects data across the entire ecosystem that allows us to understand how we're doing and how we can make it better.”
New Relic helps MLBAM come through in the clutch
With New Relic helping MLBAM identify the sources of performance issues, the company continues to reduce its mean time to resolution (MTTR) and improve the customer experience. “It raises the bar in many ways, including how our teams collaborate and the ability to resolve incidents in real time,” says Curtis. “We’re often able to realize these types of issues before they’ve had any adverse effect on our customers. We can route [users] around a problem until the root cause has been addressed.”
“The a-ha moment was really when a developer can see what's going on, diagnose what the actual issue is, and be able to remediate it and restore it, Villoslada says. Just as important, “It just makes for a better overall product.”
Critically, “New Relic makes it easier for us to accurately plan and prepare for big events,” says Curtis. “Using load testing, we can see and understand the influx of traffic and the effect of users coming through the system.”
“The earlier we can find out there’s an issue, the better our ability is to preserve the customer experience. In our business, we're competing against the biggest and best platforms in the world, so you have to provide the best customer experience.”
MLBAM: fans using New Relic to better serve fans
Joe Inzerillo, executive vice president and chief technology officer at MLBAM, explains that “New Relic helps the organization collect data across the entire ecosystem that allows us to understand how we're doing and how we can make it better. You can’t make something super high quality until you can measure it, and if you can’t measure it, how do you know it’s super high quality?”
“We’re very fortunate to work with passionate folks who are true baseball fans,” concludes Krone. “They eat, live, and breathe our products. New Relic gives them the visibility they need to support their passion and build something fans will truly enjoy.” And to help make sure customers won’t be left in the dark during the most important moments of the big game.
Major League Baseball trademarks and copyrights are used with permission of the applicable MLB entities. Visit MLB.com