Difference between revisions of "System log"
Tags: Mobile web edit Mobile edit Advanced mobile edit |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | < | + | <span style="color: #018e42; font-size: 24px; display: inline-block; margin-top: 15px; margin-bottom: 0px;"><strong>About System Log</strong></span> |
| + | |||
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. | 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 four levels of debugging. | There are four levels of debugging. | ||
| − | + | ||
{| class="wikitable" style="text-align: center; border-collapse:collapse; border-radius: 10px; overflow: hidden;" | {| class="wikitable" style="text-align: center; border-collapse:collapse; border-radius: 10px; overflow: hidden;" | ||
| Line 20: | Line 21: | ||
|} | |} | ||
| − | |||
You can tweak the currently viewed log level via the drop down control at the top left of the system log screen. | You can tweak the currently viewed log level via the drop down control at the top left of the system log screen. | ||
| Line 26: | Line 26: | ||
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. | ||
| − | |||
Latest revision as of 17:13, 23 April 2024
About System Log
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 four levels of debugging.
You can tweak the currently viewed log level via the drop down control at the top left of the system log screen.
By default all triggers, actions and constraints will be shown in the log but these can be enabled/disabled as you choose. Futhermore you can filter the log to enable/disable individual macros and global variables to help you drill down to only the information you are interested in.
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.