Integration with Splunk for Log aggregation

Splunk transforms machine-generated data into valuable insights that can help make your business more productive, profitable, and secure. 

OvalEdge posts three kinds of Logs to Splunk:

1. Application / Server Logs
2. Job / Process Logs
3. Audit Logs

1. Application / Server Logs

All the Application logs are captured using Log4j with different Log Levels.

By default, these logs are captured to ovaledge.log (10 MB), after 10 MB old logs will be moved to archive files ovaledge.x.log.

Archives are maintained up to 50 files by default.

These events are captured in the form of plain text or json. The same logs can be posted to Splunk using TCP Appender or Rest Appender at the time of writing to ovaledge.log.

2. Job / Process Logs

OvalEdge executes the processes like Crawling, Profiling, Relationship building, Lineage, etc., in the form of Jobs. In these jobs, logs are captured at various steps to understand the status of the process.

These logs can be configured to Splunk for review and analysis. This is implemented using Rest services.

3. Audit Logs

OvalEdge captures various Audit logs as part of the user accessing the application. This includes:

1. User Login and Logout
2. User Access updated
3. Metadata Changes on the Data Objects
4. Others

All these logs can be configured to Splunk for review and analysis. This is implemented using Rest services.