Highlighted
Absent Member.
Absent Member.
443 views

Exchange Server Connector tuning required to avoid reading old logs

Hi All,

Exchange server connector starts reading all the old logs and get crashed as logs are huge for last 15 days. How do we control this reading logs so that connector is not crashing.

Any parameters other than memory from 256 to 1 GB and cache from 1 to 10 GB?

​ : I know you are back now. Please help buddy.

Regards,

Amit

Labels (1)
0 Likes
6 Replies
Highlighted
Absent Member.
Absent Member.

Hi Amit,

Change below value to true in agent.properties file.

agents[0].preservestate=true

regards,

Mohammed

0 Likes
Highlighted
Absent Member.
Absent Member.

By default connector process last 256 files only, you change this value as per your requirements from agent.properties file

agents[0].processinglimit=256

regards,

Mohammed

0 Likes
Highlighted
Absent Member.
Absent Member.

Thanks Mohammed. Helpful

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Hi Amit,

Is it reading from single large log file ??  -> Enable Log Rotation

Or the folder reader reads from multiple files inside the folder  ?? -> Use Wildcards to avoid reading the old logs. And make sure it converts the logs after reading to processed state, else it will read old logs files again.

As Yahiya mentioned, u can limit the event processing rate. If it is still crashing, enable batch forwarding to test the stability of the connector.

Cheers,

Bala

0 Likes
Highlighted
Absent Member.
Absent Member.

Thanks buddy

0 Likes
Highlighted
Absent Member.
Absent Member.

Thanks Mohammed!

Just in case anyone else runs into this reading multiple folders in the same connector, I found this needs to be set for each folder -

agents[0].foldertable[0].preservestate=true

agents[0].foldertable[0].processinglimit=256

agents[0].foldertable[1]...

agents[0].foldertable[2]...

One additional item (also set for each folder):

agents[0].foldertable[0].startatend=true

Regards,

Alec

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.