You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you log an object with the message, Stackify's log viewer makes it easy to search by these parameters. You can always search by the text in the log message itself, but searching by the logged properties provides a lot more power. If you always logged a "clientid" for example on every log message, you could search in Stackify for "json.clientid:1" and quickly see all logs and errors affecting that specific client. Another big difference and advantage to logging objects is you can do a range type search "json.clientid:[1 TO 10]" which would not be possible by a straight text search.
95
95
96
96
97
-
### NLog 4.5
97
+
### NLog
98
98
99
99
**Install via NuGet package**
100
100
```
@@ -119,14 +119,24 @@ Sample config:
119
119
</nlog>
120
120
```
121
121
122
-
Logging custom objects is supported and will be searchable in Stackify's log viewer
122
+
123
+
NLog 4.5 (and newer) supports message templates, where structured properties becomes searchable in Stackify's log viewer
0 commit comments