LogDNA and IBM find synergy in cloud

IBM Cloud Case Study

In 2018 LogDNA partnered with tech giant, IBM, to become the sole logging provider for IBM Cloud. This is the story of how the partnership started. Since then, LogDNA has grown to support thousands of internal IBM teams and enterprises on IBM Cloud and is deployed in eight multi-zone regions across the globe. 

Users have access to two offerings in the cloud catalog. IBM Log Analysis with LogDNA provides detailed insights into all environments by centralizing application, system, and server logs into a single UI. Users can deploy on IBM Cloud in minutes, see their logs instantly in Live Tail, and search using natural language. Intelligent Parsing, real-time Alerts, and custom visualizations help teams stay up to date with the data that’s most valuable to them. 

IBM Cloud Activity Tracker with LogDNA is for anyone using IBM Cloud Services to help them gain insights into actions that change the state of these services. This offering provides real-time Alerts, custom Views, and data visualizations with Boards and Graphs to show a snapshot of Cloud Service activities and help users identify trends over time.

Read more
industry

Cloud

REQUIREMENTS
  • Hosted on IBM Cloud
  • Able to easily integrate with IBM Cloud Services
  • Centralized logging for IBM Cloud, internal IBM teams, and IBM customers
  • Scalability
LOGDNA SOLUTIONS
  • Built on IBM Cloud Kubernetes Service (IKS)
  • Deployed in 8 IBM data centers across the globe
  • Collects logs from dozens of IBM Cloud Services
  • Provides centralized logging for:
  • All of IBM Cloud
  • Internal teams including IBM Watson and the Weather Company
  • Thousands of IBM customers
  • Managing petabytes of log
BUSINESS IMPACT

case studies

LogDNA Helps Employment Hero Embrace Microservices at Scale

Employment Hero, which was founded in 2014, originally deployed a software stack composed of monolithic applications. It started refactoring those applications to fit a microservices architecture around 2017. At the same time, it made the move toward a Kubernetes-centric environment for hosting its applications.The company’s engineers quickly discovered, however, that the logging and monitoring solution they had in place at the time was not sufficient for managing microservices applications. The platform did not offer an easy way to collect logs within a distributed environment where each service stores logs in a different place, let alone analyze the logs efficiently. Tracing user requests across the logs of multiple services was difficult, and there was no support for live tailing logs to track the latest activity.

As Luong Vo, Platform Engineering Manager atEmployment Hero, explained, “We needed the logging system to be scalable, easy to search, accurate in time, and support live tailing,” and the existing logging solution didn’t do that. At first, Luong and his team experimented with using self-hosted Elasticsearch, Logstash and Kibana—theELK stack—to meet their need for microservices friendly log aggregation and analytics. However, “we found that we were spending too much time scaling Elasticsearch and maintaining the whole stack,” he said, prompting them to search for a more user friendly alternative.

After evaluating other logging platforms, theEmployment Hero team settled on LogDNA.

Read more
Better Mortgage Speeds Kubernetes Troubleshooting with Help from LogDNA

Better Mortgage promises its customers a seamless experience for securing a mortgage. To deliver fully on that promise, the company must ensure that it can quickly identify, troubleshoot, and resolve software performance and security issues that arise within its IT environments.

With the help of LogDNA, Better Mortgage was able to build a software monitoring and analytics stack that delivers the visibility its engineers need to find and fix problems fast. Read the full case study for a look at why Better Mortgage migrated from an open source analytics solution to LogDNA, and how LogDNA helped the company optimize the management of its complex, Kubernetes-based environments.

Read more
LogDNA is the Key to Kubernetes Observability

When you develop security software for containers, Kubernetes, and cloud services, as Sysdig does, you have an especially keen appreciation of what it takes to build an effective observability stack. You are also in a strong position to appreciate the efficiency that comes with modern observability tools that work seamlessly with next-generation platforms, such as Kubernetes. 

Both of these factors contributed to Sysdig’s decision to adopt LogDNA for gaining operational observability into its internal IT infrastructure. We recently spoke to Mark Breitung, a senior member of the DevOps team at Sysdig, about why the company chose LogDNA, and how the solution enables the holistic, contextualized observability that his team needs to keep the Sysdig platform running smoothly.

Read more
Modern Logging for Modern Account Opening

We sat down with James Qualls, a Director of Engineering at MANTL, to hear how LogDNA is empowering the developers on his team to own their monitoring. James is one of two Directors of Engineering at MANTL. He handles Infrastructure, and his counterpart, Eric Gomez, handles Application Architecture. James and his team are responsible for everything underneath the work that Eric’s team stands on top of.

Read more
IBM Cloud Case Study

First published on www.ibm.com on October 7, 2019.

Written by: Norman Hsieh, VP of Business Development, LogDNA

You know what they say: you can’t fix what you can’t find. That’s what makes log management such a critical element in the DevOps process. Logging provides key information for software developers on the lookout for code errors.

While working on their third startup in 2013, Chris Nguyen and Lee Liu realized that traditional log management was wholly inadequate for addressing data sprawl in the modern, cloud-native development stack. That epiphany was the impetus for LogDNA, a twist on a logging platform that could respond and scale in dynamic cloud environments.

Pivoting to meet DevOps need

What was straightforward when writing code for one server became unwieldy as virtualization, with multiple servers in a single machine, moved into the data center and exploded the amount of log files. As applications grow, so do code issues. And as pressure mounts on IT for zero downtime, developers need real-time visibility and an easy way to chase data activity. Containers help isolate issues, but they still largely depend on the IT infrastructure team who are unfamiliar with the applications to manage logging, and that can tax limited resources.

Building on top of the popular elasticsearch, LogDNA set out to create a solution modernized enough to provide DevOps intelligence and automatically organize all that data. Fortunately, the LogDNA team saw the writing on the wall: Kubernetes. The timing was perfect. Developers were starting to adopt the lightweight, open source platform for managing containerized workloads. LogDNA seized on the advanced orchestration capabilities of Kubernetes in cloud environments and spun out an integrated, managed software-as-a-service (SaaS) solution that began to gain traction.

Looking for a strong partner

This work caught the attention of the IBM Cloud team, which itself was shifting focus to Kubernetes services and DevOps and working actively in the open source community. We quickly found synergy between our efforts. That synergy helped weave the LogDNA logging platform into the IBM global ecosystem, binding the two companies together as partners to deliver innovative, managed Kubernetes services.

While LogDNA is in the business of logging, it is also a storage and big data company. When the team initially looked at the IBM Cloud Kubernetes Service, they worried that it wasn’t going to meet our demands. Fortunately, several IBM distinguished engineers introduced the LogDNA team to the IBM Cloud Kubernetes Service bare metal offering.

The flexibility of a bare metal option allowed LogDNA to get the IOPS (input/output operations per second) we need to read and write quickly out of storage, and at a less-expensive price than network-based storage.

The IBM-LogDNA relationship is an example of true collaboration. IBM has quickly responded to product developments recommended by the LogDNA team. However it’s not only IBM delivering enhancements; LogDNA has adjusted some process and infrastructure planning based on suggestions from the IBM team. The refinement of the logging-related offerings is a chance for the LogDNA and IBM teams to work hand-in-hand to build better services.

Getting to the heart of DevOps

LogDNA’s product is heavily focused on the DevOps space. It provides better insights, better observability into development stacks and better building tools that help developers. It offers the convenience of a very robust log management tool without the inconvenience of having to manage or configure anything.

In a world that churns out disruptive direct-to-consumer applications (think Uber), there is a growing market for a level of scalability not being addressed by others in the market today.

With the combination of IBM and LogDNA, we can help clients no matter where they are on their journey — public clouds, on-premises or hybrid. The goal is to provide a log management tool that optimizes a developer’s data. The LogDNA tool focuses heavily on things like automatic parsing. Any data that comes into LogDNA is automatically taken care of, since the tool can recognize the exact kind of incoming logs. Our tool bundles its services for simplicity and ease of use, so developers don’t need to worry about logs.

Partnering around the world

The IBM global footprint is enabling LogDNA to deliver this service consistently around the world. As the preferred logging service, LogDNA is available in the IBM Cloud Service Catalog today and will be available in all IBM service regions. IBM customers can select and order LogDNA services by identifying that they want logging; this pulls LogDNA directly into their order.

In addition to customer-requested orders, IBM plans to use LogDNA for all of its internal systems, which further extends the relationship.

Ultimately, the joint effort of IBM and LogDNA is helping our customers stay focused on their priorities, and leave the logging to us.

To learn the full story, read the case study.

Read more
industry

Cloud

REQUIREMENTS
  • Hosted on IBM Cloud
  • Able to easily integrate with IBM Cloud Services
  • Centralized logging for IBM Cloud, internal IBM teams, and IBM customers
  • Scalability
LOGDNA SOLUTIONS
  • Built on IBM Cloud Kubernetes Service (IKS)
  • Deployed in 8 IBM data centers across the globe
  • Collects logs from dozens of IBM Cloud Services
  • Provides centralized logging for:
  • All of IBM Cloud
  • Internal teams including IBM Watson and the Weather Company
  • Thousands of IBM customers
  • Managing petabytes of log
BUSINESS IMPACT

case studies

LogDNA Helps Employment Hero Embrace Microservices at Scale

Employment Hero, which was founded in 2014, originally deployed a software stack composed of monolithic applications. It started refactoring those applications to fit a microservices architecture around 2017. At the same time, it made the move toward a Kubernetes-centric environment for hosting its applications.The company’s engineers quickly discovered, however, that the logging and monitoring solution they had in place at the time was not sufficient for managing microservices applications. The platform did not offer an easy way to collect logs within a distributed environment where each service stores logs in a different place, let alone analyze the logs efficiently. Tracing user requests across the logs of multiple services was difficult, and there was no support for live tailing logs to track the latest activity.

As Luong Vo, Platform Engineering Manager atEmployment Hero, explained, “We needed the logging system to be scalable, easy to search, accurate in time, and support live tailing,” and the existing logging solution didn’t do that. At first, Luong and his team experimented with using self-hosted Elasticsearch, Logstash and Kibana—theELK stack—to meet their need for microservices friendly log aggregation and analytics. However, “we found that we were spending too much time scaling Elasticsearch and maintaining the whole stack,” he said, prompting them to search for a more user friendly alternative.

After evaluating other logging platforms, theEmployment Hero team settled on LogDNA.

Read more
Better Mortgage Speeds Kubernetes Troubleshooting with Help from LogDNA

Better Mortgage promises its customers a seamless experience for securing a mortgage. To deliver fully on that promise, the company must ensure that it can quickly identify, troubleshoot, and resolve software performance and security issues that arise within its IT environments.

With the help of LogDNA, Better Mortgage was able to build a software monitoring and analytics stack that delivers the visibility its engineers need to find and fix problems fast. Read the full case study for a look at why Better Mortgage migrated from an open source analytics solution to LogDNA, and how LogDNA helped the company optimize the management of its complex, Kubernetes-based environments.

Read more
LogDNA is the Key to Kubernetes Observability

When you develop security software for containers, Kubernetes, and cloud services, as Sysdig does, you have an especially keen appreciation of what it takes to build an effective observability stack. You are also in a strong position to appreciate the efficiency that comes with modern observability tools that work seamlessly with next-generation platforms, such as Kubernetes. 

Both of these factors contributed to Sysdig’s decision to adopt LogDNA for gaining operational observability into its internal IT infrastructure. We recently spoke to Mark Breitung, a senior member of the DevOps team at Sysdig, about why the company chose LogDNA, and how the solution enables the holistic, contextualized observability that his team needs to keep the Sysdig platform running smoothly.

Read more
Modern Logging for Modern Account Opening

We sat down with James Qualls, a Director of Engineering at MANTL, to hear how LogDNA is empowering the developers on his team to own their monitoring. James is one of two Directors of Engineering at MANTL. He handles Infrastructure, and his counterpart, Eric Gomez, handles Application Architecture. James and his team are responsible for everything underneath the work that Eric’s team stands on top of.

Read more

Get started with LogDNA

Start Trial