-
Notifications
You must be signed in to change notification settings - Fork 2
System Tab
These two utility boxes provide the same resources. The local site is separated from other sites, because the rebuild process requires actually rebuilding from raw system data, whereas rebuilding for remote sites is just a new collection of available logs from that site. To rebuild the logs for another site, you will need to have that site rebuild the logs and then your site can trigger another collection.
Name
Nickname of DT site
Domain
Domain of DT site
Snapshot
The snapshot column lists the date and status of the last snapshot generated. The “Refresh Snapshot” button will delete the current snapshot and rebuild it.
Activity
The activity column lists the number of activity records in the database.
The “Delete All Local Activity” button will find all the logs for the current site and delete them from the movement activity log. This does not delete any site data that has a different site id from the local site. This only deletes the logs generated by the local site.
The “Rebuild Activity” button will trigger a rebuild process for contacts, groups, and other events, as well as plugins. This button will not add duplicate data, so if the activity log for contacts is fully built e the process will skip contacts and continue to the next category, checking if the log has been generated for that category.
The movement activity log is built from a system log in the core of Disciple Tools. The system log records all database changes and events in the system, but is not user readable. This is why the movement_log is built from just specific activities that mark progress and setback from a movement perspective.
Note: The following sections of the system tab are primarily for troubleshooting. They provide system information and database health information.
The activity keys and totals is a simple system health tool. It shows the registered movement events (keys) that are being logged by the system and how many are logged by the local system and how many from other systems.
If a plugin has registered to log activities to the movement log (like the training plugin logging New Training Scheduled, New Trainings Completed, etc) these should show up in the list. If they do not, this is helpful for troubleshooting.
Additionally, a table with the current Sites, Site IDs, Network Dashboard profile storage ids, and Site Link record ids are listed for diagnostics purposes. These tables can be ignored unless troubleshooting.
These are basic troubleshooting tools for local system health and network activity.
Trigger Sites Button
You can use this button to quickly tell your system to visit all the sites you are connected to. It basically sends a ping to wake up and trigger all connected sites in the network.
If there are a few sites in your network that do not have a lot of activity, and if they have not had a sign on in a few days, the activity log and snapshot might not have been triggered to build.
Rebuild Migrations Button
This is also a troubleshooting button. Migrations are background upgrades to the database. If for some reason, a migration has fallen behind or gotten stuck, you can force the system to reset and rerun migration changes.
This section lists the “cron jobs” that run in the background in the mornings. Again this is a diagnostic tool that allows you to see what tasks are running and when they will run next. You can also reset and re-spawn one of the scheduled tasks.
Next Collection
This column will tell you when the next time this event will run.
Collection Name
The name of the scheduled action.
Schedule Definition
These should be set to daily collection every 24 hours (1440 minutes). This defines when to reschedule the next event after an event has run.
Delete and Re-spawn Button
This is a non-destructive process. It just deletes the current scheduled task and forces it to rerun. This is helpful if somehow a task has scheduled itself twice.
A final piece of the diagnostic tools are the links to the cron logs that are written every day when the processes run. Errors as well as successes are logged here for review.