4aca2264c58c82ef0097948664617205055e44a7
Guides/Logging-Basics.md
| ... | ... | @@ -67,6 +67,16 @@ Fatal only logs severe errors that cause crashes or program termination. Very fe |
| 67 | 67 | ``` |
| 68 | 68 | The value here ends up being the name of the log file output. It is recommended you change the "-FATAL" part if you change your logging level. The output file will be placed in the root level of the application. |
| 69 | 69 | |
| 70 | +## Logging Specific Sections |
|
| 71 | + |
|
| 72 | +It is possible to log the behavior of certain areas, and ignore others. For example, if we wanted to get only the current settings variables: |
|
| 73 | + |
|
| 74 | +AdHocContext.LogActiveAreas = new List<LogArea>() { LogArea.Settings }; |
|
| 75 | + |
|
| 76 | +Or, if you want to diagnose the Dash 2.0 page, then a configuration like this would be useful: |
|
| 77 | + |
|
| 78 | +AdHocContext.LogActiveAreas = new List<LogArea>() { LogArea.WebService, LogArea.ResponseServer }; |
|
| 79 | + |
|
| 70 | 80 | ##More Information |
| 71 | 81 | |
| 72 | 82 | For more information about logging, please visit the [log4net documentation](http://logging.apache.org/log4net/release/features.html). |
| ... | ... | \ No newline at end of file |