Avatar

Employee

Hi Ishan,

If you want to simply forward the string to another tool , I think there are better ways of achieving that without causing regression risks to your existing campaign setup.

 

1. Forward the logs received in the nl6/var/<instance_name>/redir/logs/ folder to your tool as it is or apply some filtering commands ( awk /sed ) to only forward the data for user_agent strings.

 

This can be achieved by running a shell script which will extract the lines and send only the column containing the user_agent string.

 

2. Use a log forwarder service ( e.g - Splunk , new relic etc. )  to forward your redirection logs directly to the analytics tool.

assuming you have a linux environment , you can access the apache logs in the 

/var/log/apache2/ directory and they will be name access.log or ssl_access.log 

 

Additionally , NmsTracking_UserAgentRules will be overridden each day if you have the Refresh for deliverability workflow running on the instance. 

That workflow will overwrite the rules with the one present on the global deliverability server.

 

The Method GetTrackingLogs is only used to fetch data from a Mid-sourcing server where there is a Hybrid setup ( MKT has the database and workflows running and email sending is done via Mid ) .

In this setup , the Mid server acts as a tracking server but the logs are pulled into the MKT instance by the tracking workflow using this method.

 

Regards,

Adhiyan