In this post, we will discuss some key considerations and strategies to collect and analyze your AWS Lambda logs. This will include 1) what to know about logging Lambda functions, 2) how to ship log data to a centralized logging solution, and 3) how to search and visualize log data on monitoring dashboards.

The aim of this article is to demonstrate how you can instrument a Java application using Opentelementry and Jaeger. In this example, we will be instrumenting our Java application using OpenTelemetry and the OpenTelemetry Java client, and the tracing data will be exported and visualized using Jaeger. We will use the Logz.io Jaeger backend as it is compatible with common tracing standards like Zipkin, OpenTelemetry, and OpenTracing.

Companies generate data at an exponential rate, and the task of analyzing data to produce relevant security insights can be overwhelming. With evolving market dynamics and threat landscapes, security teams have a greater need for integrated and scalable monitoring that provides real-time and meaningful insights into the state of organizational security posture.

As my colleague, Tim Frank, wrote about recently in his blog post, "The Department of Defense Data Strategy: An Important Start," in late 2020 the Department of Defense (DoD) released its new Data Strategy — providing focus and direction for the Department’s efforts to become data-centric at all levels of its enterprise.

Previously, I wrote a Beginner’s Guide to Jaeger + OpenTracing Instrumentation for Go providing guidance on manually instrumenting Go services. This is useful for cases where we want fine-grained tracing of specific functions. However, what if all we want is to trace a service’s inbound and outbound calls with little to no additional code?

Modern web applications can be complex. A typical application stack usually involves several components spread across different layers. For example, HTML5 and AngularJS can make up a site’s front end. User inputs and queries from the front end can be passed on to containerized microservices running on a middleware, which in turn could pass the queries to a back-end database. Systems like WAFs and LDAP servers can be used for security and authentication.

When building a microservices system, configuring events to trigger additional logic using an event stream is highly valuable. One common use case is receiving notifications when errors are seen in one of your APIs. Ideally, when errors occur at a specific rate or frequency, you want your system to detect that and send your DevOps team a notification. Since AWS APIs often use stateless functions like Lambdas, you need to include a tracking mechanism to send these notifications manually.

Visibility into your Salesforce environment is crucial for keeping your data secure and ensuring a seamless user eperience. That’s why we are excited to announce that Datadog can now collect Salesforce event logs directly from your Real-Time Event Monitoring stream, giving you deep insights into the security and operational performance of your Salesforce environment.

The global market for log management was valued at $1.9 billion in 2020, according to MarketsandMarkets. Analysts predict this will grow to $3.7 billion by 2025. With this massive growth in log data, there will also be massive demand for escalated support in log management systems.

Organizations that want to do business with the Department of Defense are required to achieve CMMC compliance by the end of this year. Sumo Logic can serve as a tool to assist your organization in achieving CMMC compliance.