Overview

Learn how to ingest JSON logs

Augtera stack can be configured to ingest logs encoded in JSON over UDP or from a Kafka broker as explained in Kafka section.

There are two deployment models to consider.

1. On-premise: In this mode, the Collector stack is deployed within on-premise network reachable by applications sending logs. JSON logs must be sent over UDP (port 33338) to Augtera's Collector stack. Platform stack can be deployed at any location (Augtera SaaS public cloud, private cloud, your public cloud or a different on-premise location). Appropriate security policies must be in place to allow Augtera's collector stack to be able to connect to Augtera's platform stack. HTTPS is used by collector stack to connect to platform stack.

2. Off-premise: In this mode, the Collector stack is deployed at an off-premise location, such as Augtera's SaaS cloud. JSON logs must be sent over UDP (port 33338) to Augtera's Collector stack.

The following diagram shows the flow of JSON logs to Augtera stack over UDP.

JSON logs from applications to Augtera Stack over UDP

Data Encoding

Following table describes the JSON schema of the log message.

Num	Attribute	Type	Description
1	timestamp	String	Epoch in milliseconds
2	syslogHostname	String	Sender's device name
3	severity	String	String equivalent of severity as defined in RFC 5424. For e.g. Emergency for severity=0
4	application	String	Name of application
5	description	String	Log message
6	type	String Constant	Value must be set to syslog
7	eventSource	String Constant	Value must be set to syslog
8	eventType	String Constant	Value must be set to syslog
9	key	String	Value must be set to string concatenation of syslogHostname, application and severity, such as:syslogHostname:application:severity
	Optional Attributes
10	processID	String	Process identifier of the application