Activity Logs - Revision history

SarahK: Redirected page to System Logs

2022-01-27T17:08:18Z

Redirected page to System Logs

DanR: /* Limiting/Clearing Logs */

2021-03-09T15:21:12Z

‎Limiting/Clearing Logs

SarahK at 14:13, 4 August 2020

2020-08-04T14:13:38Z

SarahK: /* Reviewing Activity Logs */

2020-08-04T12:54:41Z

‎Reviewing Activity Logs

SarahK at 16:55, 18 May 2020

2020-05-18T16:55:44Z

NickH: /* Limiting/Clearing Logs */

2018-07-31T14:47:26Z

‎Limiting/Clearing Logs

Matt: Created page with 'The activity log in WHMCS records events that occur to allow for tracking who and what initiated various actions and to allow for troubleshooting any errors or problems that occu…'

2011-01-06T01:21:54Z

Created page with 'The activity log in WHMCS records events that occur to allow for tracking who and what initiated various actions and to allow for troubleshooting any errors or problems that occu…'

New page

The activity log in WHMCS records events that occur to allow for tracking who and what initiated various actions and to allow for troubleshooting any errors or problems that occur.

For example, if automatic setup ever fails for any reason, the activity log will hold the error message response that came back from the module to allow you to find out why. Similarly, if you have any problems with the cron, the activity log will show you what tasks the cron is performing and allow you to see at exactly which point or item it is failing.

==Reviewing Activity Logs==

There are 2 types of log entries, client logs and system logs. Client logs are events and actions relating to a specific client and can be viewed from the '''Log''' tab within a Clients Profile. Alternatively the full system log which includes both client and system log entries can be accessed via '''Utilities > Activity Log'''

Each action/event records the date/time the action occured, a description indicating what happened, the currently logged in admin user who invoked the action (System shows for non admin initiated actions) and the IP Address of the user who caused it (ie. the admins IP, the clients IP or the system IP).

In both locations, you can filter the log entries for entries on a specific date, performed by a specific username/IP, and/or containing certain keywords you specify. This allows you to narrow the log down quickly and easily for the specific action or event you are looking for.

==Limiting/Clearing Logs==

The system log entries are automatically purged and kept to the limit set in '''Setup > General Settings > Limit Activity Log''', while client log entries will be kept indefinately so the logs can easily reach many thousands. This shouldn't affect the performance of your system in any way but if you do want to trim client history logs then there's an option to delete all entries before a certain date to prune the logs in '''Utilities > System Cleanup'''

← Older revision		Revision as of 17:08, 27 January 2022
Line 1:		Line 1:
−	~~<div class="docs-alert-info">~~	+	#REDIRECT [[System_Logs]]
−	~~<span class="title">WHMCS 7.x and earlier</span><br />~~
−	~~In WHMCS 7.x and earlier, you can find this at '''Utilities > Activity Log'''.~~
−	~~</div>~~
−
−	~~The activity log in WHMCS records events that occur to allow for tracking who and what initiated various actions and to allow for troubleshooting any errors or problems that occur.~~
−
−	For example, if automatic setup ever fails for any reason, the activity log will hold the error message response that came back from the module to allow you to find out why. Similarly, if you have any problems with the cron job, the activity log will show you what tasks the cron job is performing and allow you to see at exactly which point or item it is failing.
−
−	~~For more information about WHMCS log files, see~~ [[~~System_Utilities#Activity_Logs\|System Utilities~~]].
−
−	~~==Reviewing Activity Logs==~~
−
−	There are two types of log entries: client logs and system logs. Client logs are events and actions relating to a specific client, and you can view them from the '''Log''' tab within a client's profile. You can access the full system log, which includes both client and system log entries, via '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Logs'''.
−
−	Each action or event records the date and time the action occured, a description indicating what happened, the currently-logged-in admin user who invoked the action ('''System''' for non-admin-initiated actions) and the IP address of the user who caused it (for example, the admin's, client's, or system's IP address).
−
−	In both locations, you can filter the log entries for entries on a specific date, for a specific username or IP address, or containing certain keywords. This allows you to narrow the log down quickly and easily for the specific action or event you are looking for.
−
−	~~==Limiting/Clearing Logs==~~
−
−	~~The system automatically purges system log entries when the daily cron tasks execute and when you load the Activity Log page.~~
−
−	~~System log entries are limited based on your settings in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > General Settings > Limit Activity Log'''.~~
−
−	The system keeps client log entries indefinitely, so the logs can easily reach many thousands. This shouldn't affect the performance of your system, but if you do want to trim client history logs, you can delete all entries before a certain date in '''Utilities > System Cleanup'''.

← Older revision		Revision as of 15:21, 9 March 2021
Line 20:		Line 20:
	==Limiting/Clearing Logs==		==Limiting/Clearing Logs==

−	The system automatically purges system log entries and ~~limits them according to~~ your settings in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > General Settings > Limit Activity Log'''. The system keeps client log entries indefinitely, so the logs can easily reach many thousands. This shouldn't affect the performance of your system, but if you do want to trim client history logs, you can delete all entries before a certain date in '''Utilities > System Cleanup'''.	+	The system automatically purges system log entries when the daily cron tasks execute and when you load the Activity Log page.
		+
		+	System log entries are limited based on your settings in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > General Settings > Limit Activity Log'''.
		+
		+	The system keeps client log entries indefinitely, so the logs can easily reach many thousands. This shouldn't affect the performance of your system, but if you do want to trim client history logs, you can delete all entries before a certain date in '''Utilities > System Cleanup'''.

@@ Line 1: / Line 1: @@
 The activity log in WHMCS records events that occur to allow for tracking who and what initiated various actions and to allow for troubleshooting any errors or problems that occur.
@@ Line 7: / Line 12: @@
 ==Reviewing Activity Logs==
-There are three types of log entries: client logs and system logs. Client logs are events and actions relating to a specific client, and you can view them from '''Log''' within a client's profile. You can access the full system log, which includes client, user, admin, and system log entries, via '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Logs''' ('''Utilities > Activity Log''' in WHMCS 7.10 and earlier).
+There are two types of log entries: client logs and system logs. Client logs are events and actions relating to a specific client, and you can view them from the '''Log''' tab within a client's profile. You can access the full system log, which includes both client and system log entries, via '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Logs'''.
-Each action or event records the date and time the action occured, a description indicating what happened, the currently-logged-in client and user or admin who invoked the action ('''System''' for non-admin-or-user-initiated actions) and the IP address of whoever caused it (for example, the admin's, user's, client's, or system's IP address).
+Each action or event records the date and time the action occured, a description indicating what happened, the currently-logged-in admin user who invoked the action ('''System''' for non-admin-initiated actions) and the IP address of the user who caused it (for example, the admin's, client's, or system's IP address).
-In both locations, you can filter the log entries for entries on a specific date, for a specific username or IP address, or for certain keywords. This allows you to narrow the log down quickly and easily for the specific action or event you are looking for.
+In both locations, you can filter the log entries for entries on a specific date, for a specific username or IP address, or containing certain keywords. This allows you to narrow the log down quickly and easily for the specific action or event you are looking for.
 ==Limiting/Clearing Logs==
-The system automatically purges system log entries and limits them according to your settings in '''Setup > General Settings > Limit Activity Log'''. The system keeps client log entries indefinitely, so the logs can easily reach many thousands. This shouldn't affect the performance of your system, but if you do want to trim client history logs, you can delete all entries before a certain date in '''Utilities > System Cleanup'''.
+The system automatically purges system log entries and limits them according to your settings in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > General Settings > Limit Activity Log'''. The system keeps client log entries indefinitely, so the logs can easily reach many thousands. This shouldn't affect the performance of your system, but if you do want to trim client history logs, you can delete all entries before a certain date in '''Utilities > System Cleanup'''.

@@ Line 7: / Line 7: @@
 ==Reviewing Activity Logs==
-There are two types of log entries: client logs and system logs. Client logs are events and actions relating to a specific client, and you can view them from the '''Log''' tab within a client's profile. You can access the full system log, which includes both client and system log entries, via '''Utilities > Activity Log'''.
+There are three types of log entries: client logs and system logs. Client logs are events and actions relating to a specific client, and you can view them from '''Log''' within a client's profile. You can access the full system log, which includes client, user, admin, and system log entries, via '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Logs''' ('''Utilities > Activity Log''' in WHMCS 7.10 and earlier).
-Each action or event records the date and time the action occured, a description indicating what happened, the currently-logged-in admin user who invoked the action (''System'' for non-admin-initiated actions) and the IP address of the user who caused it (for example, the admin's, client's, or system IP address).
+Each action or event records the date and time the action occured, a description indicating what happened, the currently-logged-in client and user or admin who invoked the action ('''System''' for non-admin-or-user-initiated actions) and the IP address of whoever caused it (for example, the admin's, user's, client's, or system's IP address).
-In both locations, you can filter the log entries for entries on a specific date, for a specific username or IP address, or containing certain keywords. This allows you to narrow the log down quickly and easily for the specific action or event you are looking for.
+In both locations, you can filter the log entries for entries on a specific date, for a specific username or IP address, or for certain keywords. This allows you to narrow the log down quickly and easily for the specific action or event you are looking for.
 ==Limiting/Clearing Logs==
 The system automatically purges system log entries and limits them according to your settings in '''Setup > General Settings > Limit Activity Log'''. The system keeps client log entries indefinitely, so the logs can easily reach many thousands. This shouldn't affect the performance of your system, but if you do want to trim client history logs, you can delete all entries before a certain date in '''Utilities > System Cleanup'''.

← Older revision		Revision as of 14:47, 31 July 2018
Line 13:		Line 13:
	==Limiting/Clearing Logs==		==Limiting/Clearing Logs==

−	The system log entries are automatically purged and kept to the limit set in '''Setup > General Settings > Limit Activity Log''', while client log entries will be kept ~~indefinately~~ so the logs can easily reach many thousands. This shouldn't affect the performance of your system in any way but if you do want to trim client history logs then there's an option to delete all entries before a certain date to prune the logs in '''Utilities > System Cleanup'''	+	The system log entries are automatically purged and kept to the limit set in '''Setup > General Settings > Limit Activity Log''', while client log entries will be kept indefinitely so the logs can easily reach many thousands. This shouldn't affect the performance of your system in any way but if you do want to trim client history logs then there's an option to delete all entries before a certain date to prune the logs in '''Utilities > System Cleanup'''