Ingest Logs from Multiple Sources in ObserveOps
ObserveOps collects logs from various source categories: application servers, syslog devices, databases, cloud providers, TCP/UDP forwarders, and event sources. Each source connects through an ingestion profile that tells ObserveOps where to collect logs, how to collect them, and what log type to assign.
Source Categories at a Glance
| Category | How Logs Arrive |
|---|---|
| Application | Via MotaAgent installed on the source server |
| Syslogs | Directly over the network via syslog protocol |
| Database | Via MotaAgent installed on the database server |
| Cloud | Pulled from cloud provider APIs (AWS, Azure, Office 365, and others) |
| TCP/UDP | Directly over TCP or UDP network connections |
| Events | Via MotaAgent (agent-based) or (agentless-based) from Windows, vCenter, Cisco, and others |
Where to Add Log Sources
Go to Settings > Observability Pipeline > Log Ingestion to add and manage all log sources.
For step-by-step instructions on connecting each source type, see Log Ingestion.
After Adding a Source
Once a source is configured, logs begin flowing into ObserveOps. Open Live Trail to verify that logs are arriving in real time.
After the source is configured and ingestion profiles are mapped to log types, logs automatically flow through the respective OOTB pipelines or user-created pipelines for custom logs. Use this:
To learn more about parsing and enriching logs before storage, see Configure Log Pipelines.