Skip to main content
replaced http://sharepoint.stackexchange.com/ with https://sharepoint.stackexchange.com/
Source Link

You can order up your approaches as below,

  1. ULS

  2. Event Viewer

  3. Text file.

I suggest, ULS - Its the SharePoint native logging and it manages to remove the older files periodically, its better to keep all the SharePoint related logs in one place "ULS". Use SPDiagnosticsService.Local.WriteTrace method in your timer job to log into the ULS logs

If you find that reading logs from ULS is difficult then you can end up with your own text file for logging the errors/messages.

Have a look at the below link too,

TimerJobs and ULSTimerJobs and ULS

Five suggestions to implement a better logging in SharePoint

You can order up your approaches as below,

  1. ULS

  2. Event Viewer

  3. Text file.

I suggest, ULS - Its the SharePoint native logging and it manages to remove the older files periodically, its better to keep all the SharePoint related logs in one place "ULS". Use SPDiagnosticsService.Local.WriteTrace method in your timer job to log into the ULS logs

If you find that reading logs from ULS is difficult then you can end up with your own text file for logging the errors/messages.

Have a look at the below link too,

TimerJobs and ULS

Five suggestions to implement a better logging in SharePoint

You can order up your approaches as below,

  1. ULS

  2. Event Viewer

  3. Text file.

I suggest, ULS - Its the SharePoint native logging and it manages to remove the older files periodically, its better to keep all the SharePoint related logs in one place "ULS". Use SPDiagnosticsService.Local.WriteTrace method in your timer job to log into the ULS logs

If you find that reading logs from ULS is difficult then you can end up with your own text file for logging the errors/messages.

Have a look at the below link too,

TimerJobs and ULS

Five suggestions to implement a better logging in SharePoint

Source Link

You can order up your approaches as below,

  1. ULS

  2. Event Viewer

  3. Text file.

I suggest, ULS - Its the SharePoint native logging and it manages to remove the older files periodically, its better to keep all the SharePoint related logs in one place "ULS". Use SPDiagnosticsService.Local.WriteTrace method in your timer job to log into the ULS logs

If you find that reading logs from ULS is difficult then you can end up with your own text file for logging the errors/messages.

Have a look at the below link too,

TimerJobs and ULS

Five suggestions to implement a better logging in SharePoint