Difference between revisions of "System log"
| Line 5: | Line 5: | ||
* Extended - This adds an additional level of detail, sometimes this is helpful to debug complex issues such as when a time based trigger doesn't appear to be firing at the correct time. | * Extended - This adds an additional level of detail, sometimes this is helpful to debug complex issues such as when a time based trigger doesn't appear to be firing at the correct time. | ||
* Extreme - This adds additional log messages for a few specific scenarios. Most users will never need to use this as it's mostly used for the developer to track complex issues. | * Extreme - This adds additional log messages for a few specific scenarios. Most users will never need to use this as it's mostly used for the developer to track complex issues. | ||
| + | |||
| + | You can enable extended and extreme logging via the options menu on the system log screen. | ||
By default all triggers, actions and constraints will be logged but any of these can be turned off via the menu on the system log page. | By default all triggers, actions and constraints will be logged but any of these can be turned off via the menu on the system log page. | ||
Any individual macro can be disabled from logging via the edit macro page. This is useful for example if you have one macro that runs very regularly and ends up filling the log with non useful information. | Any individual macro can be disabled from logging via the edit macro page. This is useful for example if you have one macro that runs very regularly and ends up filling the log with non useful information. | ||
Revision as of 08:02, 5 February 2021
The system log contains a detailed history of what has happened within MacroDroid. It is an essential tool to help debug any problems with your macros and to understand when your macros are firing.
There are three levels of debugging.
- Standard - This is the default level and contains enough infornation to keep track of what is happening.
- Extended - This adds an additional level of detail, sometimes this is helpful to debug complex issues such as when a time based trigger doesn't appear to be firing at the correct time.
- Extreme - This adds additional log messages for a few specific scenarios. Most users will never need to use this as it's mostly used for the developer to track complex issues.
You can enable extended and extreme logging via the options menu on the system log screen.
By default all triggers, actions and constraints will be logged but any of these can be turned off via the menu on the system log page.
Any individual macro can be disabled from logging via the edit macro page. This is useful for example if you have one macro that runs very regularly and ends up filling the log with non useful information.