Robotlogs via NLog to Database: No debugfile and no data transferred

[jeevith (Jeevith Hegde, Ph.D.)]

Hi @PeCour,

Not exactly an answer to your query.

We also create a NLog file but the use case is to let the Splunl Forwarder use it.

You can refer how we used the targets and rules to achieve this in this post

Logs - ElasticSearch

Hi @Felipe_Kotinda, That is correct. The data flow is Robot Execution log (Robot Machine) - .txt → Orchestrator log (Orchestrator Machine) - .txt → Splunk Forwarder (on both Robot Machine and Orchestrator Machine) → Splunk Index → Splunk Query → Splunk Dashboard / Report One thing to note here is we use dedup (remove duplicates) in Splunk so that our dashboards do not contain results from both Robot and Orchestrator Logs. Retentionpolicy is set to 1 year after which we still have acces…