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
Copy file name to clipboardExpand all lines: README.md
+27-4Lines changed: 27 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,9 +2,9 @@
2
2
3
3
Library for Stackify users to integrate Stackify in to their projects. Provides support for sending errors, logs, and custom metrics to Stackify. Also some support for querying metric data back out of Stackify for use in external projects.
- Can be plugged in to custom built or other logging frameworks
29
29
- Does not depend on the Stackify monitoring agent. All data is sent directly to Stackify.
30
30
31
+
The packages for log4net, NLog and Elmah all depend on StackifyLib. StackifyLib also has support for custom metrics and accessing some of Stackify's API to pull data back out.
31
32
32
33
The following is required in your App.config or Web.config:
33
34
@@ -70,6 +71,11 @@ If you log an object with the message, Stackify's log viewer makes it easy to se
70
71
71
72
###NLog 2.0.1.2 - v3.1+
72
73
74
+
**Install via NuGet package**
75
+
```
76
+
PM> Install-Package StackifyLib.NLog
77
+
```
78
+
73
79
Nuget packages are compiled against 2.0.1.2 but any newer version (including v3) will work with a valid assembly binding redirect.
74
80
75
81
<dependentAssembly>
@@ -107,7 +113,13 @@ Options
107
113
- logMethodNames - Method names will show up in the StackifyLog viewer most of the time as the class name that did the logging. For exceptions it will usually show the method name. To enable the exact method name for all logging, set this property to true. Note that it does cause a small performance hit due to walking the StackTrace.
108
114
109
115
###log4net v2.0+ (v1.2.11+)
110
-
Note: Nuget packages are compiled against 2.0.0 (1.2.11) but any newer version will work with a valid assembly binding redirect. log4net 2.0.3 is actually 1.2.13 which makes the binding redirect look strange.
116
+
117
+
**Install via NuGet package**
118
+
```
119
+
PM> Install-Package StackifyLib.log4net
120
+
```
121
+
122
+
Note: Nuget packages are compiled against 2.0.0 (1.2.11) but any newer version will work with a valid assembly binding redirect. log4net 2.0.3 is actually 1.2.13 which makes the binding redirect look strange.
@@ -161,11 +173,22 @@ log4net does not internally have methods for logging a log message along with an
161
173
logger.Debug("Starting some process for client 1", dictionary); //extension method
162
174
163
175
###log4net v1.2.10
176
+
177
+
**Install via NuGet package**
178
+
```
179
+
PM> Install-Package StackifyLib.log4net.v1_2_10
180
+
```
181
+
164
182
Note: If you use 1.2.10 then you must use our special nuget package for that version. There is no way to use an assembly redirect because the public key of log4net v1 and v2 are different. Everything else is the same about using log4net with Stackify.
165
183
166
184
167
185
###Direct API
168
186
187
+
**Install via NuGet package**
188
+
```
189
+
PM> Install-Package StackifyLib
190
+
```
191
+
169
192
If you use a custom logging framework or a framework not currently supported, you can easily send logs to Stackify with our core library and API like so:
170
193
171
194
StackifyLib.Logger.Queue("DEBUG", "My log message");
0 commit comments