Improve Your Application Insights Using Log Analysis with LogDNA

By: Charles Comiskey

Platform service logs in Log Analysis with LogDNA

Great log analysis insights begin with capturing data from your full application and environment. Data may originate from outside the cloud, workloads running inside your cloud account, and from multi-tenant Cloud Services you provision. Developers may control the quality of logging from their code. Relevant environment logging can be a challenge, especially when your application is using a multi-tenant service.

Improve Your Application Insights Using Log Analysis with LogDNA-1

IBM Log Analysis with LogDNA has a solution for multi-tenant services running on IBM Cloud. Starting now, platform service logs from your IBM Cloud multi-tenant services will be appearing in your provisioned LogDNA instances. Platform service logs from IBM Cloud Databases are available today. Other services will begin sharing relevant logs soon.

An IBM Cloud Databases example

IBM Cloud Databases for PostgreSQL shares platform service logs. Users may want to understand if their instance is in a healthy state, or they might want insights into query performance.  The new platform service log data that is coupled with LogDNA’s features allows users to assess and take action.

Healthy environment

In this example, the PostgreSQL instance indicates it is in a healthy state—two data members configured for High Availability, a leader that is accepting reads and writes, and a follower that is asynchronously receiving reads and is eligible for promotion in case of a leader failure.

Improve Your Application Insights Using Log Analysis with LogDNA-2

Slow query

In this other instance, platform service logs from the PostgreSQL instance allow developers to analyze the performance of SQL queries and tune them. The length of query time in the first log entry is resulting in a delay of the second query’s execution.

Improve Your Application Insights Using Log Analysis with LogDNA-3

Getting started

As a user of a participating Cloud Service, if you have a Log Analysis with LogDNA instance defined, the logs can be set up to arrive in two simple steps:

  1. Provision a Log Analysis with LogDNA instance (if one does not already exist)

  2. Update your configuration to enable logs from the services

You’re ready to go! Participating Cloud Services will then begin to share relevant log data with tenants, such as your account.

Cloud Services have write-only ability to share the log data. For security-minded audiences, data can only be shared with the tenant and not read back. Cloud services also do not have the ability to delete or claw back data once it is shared. Logs collected by Log Analysis with LogDNA are immutable. For compliance-minded audiences, data collected in the region stays in the region. For example, data from a Frankfurt-hosted IBM Cloud Database instances will go to the Log Analysis with LogDNA instance in Frankfurt.

Logs shared from Cloud Services happen live as they are processed. Taking advantage of this feature requires you to have a logging instance set up in your account. If you do not already have an instance, create your first logging instance today.

Great insights from your Log data

Enterprise-grade log management extends beyond collection. Log Analysis with LogDNA’s core log management abilities provide optimal log management, including alerting, intuitive search, filtering, live streaming tail, and raw, blazing fast search results that help developers and support find and fix issues fast.

Log Analysis with LogDNA also supports archive and compliance. Archive logs to your IBM Cloud Object Storage, and the service is compliant with PCI SOC2 Type 1, GDPR, and Privacy Shield.

Automated logging from participating cloud services is immediately available in US-South and will soon roll out to other worldwide data centers. Learn which services are participating from here.

Begin or continue your logging journey today.

Be the first to hear about news, product updates, and innovation from IBM Cloud