April 19, 2018 By Carlos Santana 2 min read

Log Analysis just got easier for serverless apps

In serverless applications, functions are small and need to execute in less amount of time in a stateless environment. Logging then becomes a challenge for DevOps to do Root Cause Analysis (RCA) or get insights about the behavior of their applications.

One logging approach is to add code to your functions to send logs to an external API, which can be a painful process for you and the performance of your applications. You don’t want to add complexity to your functions in terms of security, extra endpoints and protocols, as opposed to just concentrating on your business logic scoped to the single function. Because every millisecond counts when using serverless, you don’t want end users waiting while you send logs during action invocation.

IBM Cloud Functions now forward logs to the IBM Cloud Log Analysis service, where you can perform full-text search through all generated messages and query based on specific fields (like log-level).

In the case of IBM Cloud Functions, the platform takes care of the complexity, allowing you to collect and analyze logs using the ELK Stack (Elasticsearch, Logstash, and Kibana) as a centralized log management solution. Just print a line to standard out or error and your logs will be available in a secure, scalable way, without worrying about infrastructure for logging.

You can use the logging capabilities in the IBM Cloud to understand the behavior of your Serveless Applications.

No special instrumentation is required to collect the standard out (stdout) or standard error (stderr) logs.

User Logs

For example, you can now leverage serverless logs to provide the following features:

  • Provide an audit trail for an application

  • Detect problems in your application

  • Identify vulnerabilities

  • Troubleshoot your app

  • Trace your app across components in the Cloud Platform

  • Detect patterns that you can use to preempt actions that could affect your Serverless Application.

Activation Records

In addition to log lines, IBM Cloud Log Analysis also indexes the results (activation records) generated by IBM Cloud Functions. The results contain rich-metadata relevant for activations, such as their duration or result-code (success, error). All of the fields are queryable, and as such can help you understand how your Cloud Functions Actions are behaving.

With Kibana, you can do queries, build visualizations, and easily compose dashboards customized for your environment.  To build a visualization, first access the management tab in the Kibana dashboard, and then refresh the field list for the index pattern, so that terms become available for selection.

Get started with IBM Cloud Functions

For more information make sure you to check out the IBM Cloud Functions documentation.

More from

Data protection strategy: Key components and best practices

8 min read - Virtually every organization recognizes the power of data to enhance customer and employee experiences and drive better business decisions. Yet, as data becomes more valuable, it's also becoming harder to protect. Companies continue to create more attack surfaces with hybrid models, scattering critical data across cloud, third-party and on-premises locations, while threat actors constantly devise new and creative ways to exploit vulnerabilities. In response, many organizations are focusing more on data protection, only to find a lack of formal guidelines and…

What you need to know about the CCPA draft rules on AI and automated decision-making technology

9 min read - In November 2023, the California Privacy Protection Agency (CPPA) released a set of draft regulations on the use of artificial intelligence (AI) and automated decision-making technology (ADMT). The proposed rules are still in development, but organizations may want to pay close attention to their evolution. Because the state is home to many of the world's biggest technology companies, any AI regulations that California adopts could have an impact far beyond its borders.  Furthermore, a California appeals court recently ruled that…

Enhancing triparty repo transactions with IBM MQ for efficiency, security and scalability

3 min read - The exchange of securities between parties is a critical aspect of the financial industry that demands high levels of security and efficiency. Triparty repo dealing systems, central to these exchanges, require seamless and secure communication across different platforms. The Clearing Corporation of India Limited (CCIL) recently recommended (link resides outside ibm.com) IBM® MQ as the messaging software requirement for all its members to manage the triparty repo dealing system. Read on to learn more about the impact of IBM MQ…

IBM Newsletters

Get our newsletters and topic updates that deliver the latest thought leadership and insights on emerging trends.
Subscribe now More newsletters