Collect from Other Data Sources

Sumo Logic can collect logs and metrics from a variety of data Sources.

In this section, we will introduce the following concepts:

🗃️ Amazon CloudWatch Logs

3 items

📄️ Amazon MSK Prometheus metrics collection

Amazon Managed Streaming for Apache Kafka (Amazon MSK) Open Monitoring, exposes Kafka metrics to third-party sources to monitor and troubleshoot MSK clusters. This page provides instructions for configuring metrics collection for Amazon MSK.

📄️ Auto-Subscribe ARN (Amazon Resource Name) Destination

You can use an Amazon CloudWatch Log Group subscription to collect log events from CloudWatch Logs in real-time, and send them to Sumo Logic.

📄️ Collect AWS ECS Fargate Container Logs

This page describes how to collect application container logs from AWS ECS clusters launched with AWS Fargate using AWS FireLens. This method also works with ECS clusters with EC2 containers. However, the recommended method for collecting EC2 logs is to utilize the Docker logging driver.

🗃️ Azure Blob Storage

2 items

🗃️ Azure Monitoring

2 items

📄️ Collect Logs from Heroku

You can upload data from your Heroku app directly to Sumo Logic by pointing a Heroku log drain to the URL for an HTTP Source. The log drain forwards batches of data directly to the HTTP Source.

📄️ Collect StatsD Metrics

There are three basic parts to a StatsD implementation: application libraries, a simple protocol used to define the metrics, and a daemon/server that aggregates the metrics for a time window and flushes the aggregated metrics to a metrics back-end system. There are many StatsD libraries and StatsD daemons. If you want to add StatsD to your application and send your metrics to Sumo, we recommend using collectd as your metrics collection agent, with the StatsD input enabled. With Sumo’s collectd Plugin, you can add metadata to your metrics and send your metrics to Sumo in a multi-dimensional, metrics 2.0 format.

📄️ Collect Logs for SentinelOne

This page provides instructions for ingesting SentinelOne logs into Sumo Logic. For more information, on SentinelOne please visit the SentinelOne website.

📄️ Collect AWS Lambda Logs using an Extension

AWS Lambda Extensions enable us to more easily integrate into the AWS Lambda execution environment to control and participate in the AWS Lambda lifecycle and the AWS Lambda Logs API enables us to collect AWS Lambda logs. Sumo Logic, therefore, has developed a new open-source AWS Lambda extension that is a lightweight process that runs within the same execution environment as your Lambda functions and uses the Lambda logs API to send platform, function, and extension logs to Sumo Logic. Sumo Logic's Lambda Extension works with AWS Lambda functions that are built for both x86_64 and ARM 64 (Graviton2) architectures.

🗃️ VMware vRealize

3 items

📄️ Collect Logs from AWS Fargate

This page describes how to collect logs from AWS Fargate.

📄️ Collect Logs from Oracle Cloud Infrastructure

Oracle Cloud supports the export of OCI Service logs, Audit logs, Application logs and Security logs to Sumo Logic. For more details please see this document that is documented and supported by Oracle.

📄️ Collect Logs from Palo Alto Networks Cortex Data Lake

This page provides you instructions on how to Collect Logs from the Palo Alto Networks Cortex Data Lake.

🗃️ Telegraf

5 items

📄️ Collect Prometheus Metrics

You can collect Prometheus metrics in Kubernetes or outside of Kubernetes using Telegraf to collect and a plugin to send data to Sumo Logic. This guide walks through the plugins and options to set up your collection.

📄️ Collect Ruby on Rails Logs

When collecting more complex application logs, like those generated by Ruby on Rails (RoR) applications, you must complete a few essential steps to make sure that your logs are ingested and parsed correctly.

📄️ Create a Sumo Lambda Function

Sumo provides a Lambda function for use with Amazon Web Services (AWS). It collects AWS Lambda logs using CloudWatch Logs and it extracts and adds a RequestId field to each log line to make correlation easier.

📄️ Deploy Sumo Logic Collectors on AWS OpsWorks

AWS OpsWorks provides a simple platform that allows you to easily create and manage stacks and applications. It supports standard components such as application servers, database servers, and load balancers, which you use to assemble a stack. These components all come with a standard configuration, but AWS OpsWorks also provides tools to help you create custom components and configuration. AWS OpsWorks also lets you manage related AWS resources, such as Elastic IP addresses and Amazon EBS volumes.

📄️ Docker Collection Methods

This page describes and compares alternative methods for collecting Docker logs and metrics. You can employ these methods in self-managed Docker environments or with managed Docker services like ECS and Swarm.

📄️ Import Raw Data from Splunk

Although you can import data from Splunk, Sumo Logic does not support Splunk functionality or any commands included below.

📄️ Integrate Halo Event Logs into Sumo Logic

The Halo Event Connector enables you to pull security event logs from Halo into Sumo Logic, including alerts from your configuration, file integrity, and software vulnerability scans. Halo can also deliver unprecedented visibility of your cloud servers, directly into your log management console. You can track server events such as your server rebooting, shutting down, changing IP addresses, and much more.