Overview of source types for Data Manager
You can use Data Manager to ingest data of the following source types.
After you install the add-on that is applicable to your data input type, Data Manager supports Common Information Model (CIM) normalization. Installing the add-on enables data processing that occurs when a search is run, called search-time processing. You must install the add-on on the part of your Splunk Cloud deployment that performs the parsing or search-time functionality for your data. You don't need to configure the add-on.
For more information on which add-on applies to your data input type, see the Prerequisites topic in the chapter of your cloud data input type in this manual.
For information on the CIM, see the Overview of the Splunk Common Information Model topic in the Common Information Model Add-on manual.
Getting data in for AWS
You can get data in for the following AWS data sources.
Data source | Description | Source type and example event |
---|---|---|
Amazon API Gateway | Amazon API Gateway is an AWS service for creating, publishing, maintaining, monitoring, and securing REST, HTTP, and WebSocket APIs at any scale. Amazon API Gateway reports metrics through Amazon CloudWatch. | Source type:
Example event:
|
AWS CloudHSM | AWS CloudHSM is a cloud-based hardware security module (HSM) that lets you generate and use your own encryption keys on the AWS Cloud. | Source type:
Example event:
|
AWS CloudTrail | AWS CloudTrail is a service that enables governance, compliance, operational auditing, and risk auditing of your AWS account. | Source type:
Example event:
|
Amazon DocumentDB | Amazon DocumentDB (with MongoDB compatibility) is a fully managed database service that is purpose-built for JSON data management at scale. | Source type:
Example event:
|
Amazon EKS | Amazon EKS is a managed service that you can use to run Kubernetes on AWS without installing, operating, and maintaining your own Kubernetes control plane or nodes. | Source type:
Example event:
|
Amazon GuardDuty | Amazon GuardDuty is a threat detection service that continuously monitors for malicious activity and unauthorized behavior to protect your AWS accounts, workloads, and data stored in Amazon S3. | Source type:
Example event:
|
AWS IAM Access Analyzer | AWS IAM Access Analyzer helps you identify the resources in your organization and accounts, such as Amazon S3 buckets or IAM roles, that are shared with an external entity. | Source type:
Example event:
|
AWS IAM Credential Report | AWS IAM Credential Report lists all users in your account and the status of their various credentials, including passwords, access keys, and MFA devices. | Source type:
Example event:
|
AWS Lambda | AWS Lambda is a compute service that lets you run code without provisioning or managing servers. | Source type:
Example event:
|
Metadata | Metadata is data about your instance that you can use to configure or manage items such as EC2 Instances, IAM Roles, and Security Groups. | Source type:
Example event:
|
Amazon RDS | Amazon RDS is a web service that allows users to set up, operate, and scale a relational database in the cloud. | Source type:
Example event:
|
AWS Security Hub | AWS Security Hub gives you a comprehensive view of your security alerts and security posture across your AWS accounts. | Source type:
Example event:
|
AWS CloudTrail (S3) | Gain visibility into CloudTrail metrics from their S3 logs. | Source type:
Example event:
|
AWS S3 access logs (S3) | Gain visibility into S3 access logs from their S3 logs. | Source type:
Example event:
|
AWS Load Balancer (ELB) access logs | Gain visibility into ELB access logs from their S3 logs. | Source type:
Example event:
|
AWS CloudFront (CF) access logs | Gain visibility into CloudFront access logs from their S3 logs. | Source type:
Example event:
|
Getting data in for Microsoft Azure
You can get data in for the following Microsoft Azure data sources.
Data source | Description | Source type and example event |
---|---|---|
Microsoft Entra ID | Microsoft Entra ID is a cloud computing service created by Microsoft for building, testing, deploying, and managing applications and services through Microsoft-managed data centers. | Source type:
Example event:
|
Azure Activity Logs | Azure Activity Logs are platform logs in Azure that provide insight into subscription-level events. This includes such information as when a resource is modified or when a virtual machine is started. | Source type:
Example event:
|
Azure Event Hub | Note: Available for public preview customers. Azure Event Hubs are data streaming services that can process large volumes of events per second with low latency. They can stream events from any source to any destination.
| Source types:
azure:monitor:aad azure:monitor:resource azure:monitor:activity Example event:
|
Azure Event Hubs
Using Data Manager, you can ingest data from Azure Event Hubs to Splunk Cloud Platform. The Azure Event Hubs functionality provides an event streaming platform that you can scale. It can process large volumes of data units, called events, per second. To learn about Azure Event Hubs and their throughput capacity, see the following articles in the Azure documentation:
Event Hubs reside in a management container called a namespace. It can contain one or more event hubs. When you create an event hub on Azure, you need to select an existing namespace or create one.
The entities that send data to an event hub are event publishers, also called event producers. Event consumers are entities that read data from the event hub, like Splunk Cloud Platform. You can divide event consumers into consumer groups. Although a consumer group can include several event consumers, the best practice is to create a separate consumer group for each.
By creating partitions on an event hub, you can organize events and help processing large volumes of events. Partitions multiply the available capacity and scale out the number of parallel consumers. Also, you can map events to partitions, so that each event has a processing owner. To learn about features of Event Hubs, see Features and terminology in Azure Event Hubs in the Azure documentation.
Partition count is the total number of partitions in an event hub. It must be between one and the maximum limit which depends on the event hub tier. The best practice is to choose the number of partitions that you expect to need during the peak load on an event hub.
The event lives on the event hub for a limited time that varies from 24 hrs to 7 days. It is called a retention time and depends on the event hub tier. To learn about tiers of Event Hubs, see: Basic vs. standard vs. premium vs. dedicated tiers in the Azure documentation.
Getting data in for Google Cloud Platform
You can get data in for the following Google Cloud Platform data sources.
Data source | Description | Source type and example event |
---|---|---|
Audit Logs - Admin Activity | Audit Logs - Admin Activity records administrative activities within your Google Cloud resources. | Source type:
|
Audit Logs - System Events | Audit Logs - System Events records administrative activities within your Google Cloud resources. | Source type:
|
Audit Logs - Policy Denied | Audit Logs - Policy Denied records administrative activities within your Google Cloud resources. | Source type:
|
Audit Logs - Data Access | Audit Logs - Data Access records administrative activities within your Google Cloud resources. | Source type:
Example event:
|
Access Transparency Logs - Access Transparency | Review logs of actions taken by Google staff when accessing user content. User-generated content is text entered into Gmail, Docs, Sheets, Slides, and other apps. | Source type:
Example event:
|