Ingest Logs from Multiple Sources in ObserveOps
ObserveOps collects logs from six source categories: application servers, syslog devices, databases, cloud providers, TCP/UDP listeners, 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 or agentlessly from Windows, vCenter, Cisco, and others |
Where to Connect 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 Connecting a Source
Once a source is connected, its logs begin flowing into ObserveOps. Open Live Trail to confirm logs are arriving in real time. Then build a pipeline in Configure Log Pipelines to parse and enrich those logs before they reach storage.