Skip to content

Commit 4f05844

Browse files
committed
adding additional logging resource
1 parent 402dd4b commit 4f05844

File tree

3 files changed

+24
-1
lines changed

3 files changed

+24
-1
lines changed

feeds/all.atom.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,2 @@
11
<?xml version="1.0" encoding="utf-8"?>
2-
<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2014-03-28T17:20:47Z</updated></feed>
2+
<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2014-03-29T09:26:20Z</updated></feed>

logging.html

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -123,6 +123,16 @@ <h3>Open Source Log Aggregators</h3>
123123
<li><a href="https://github.com/facebook/scribe">Scribe</a> A project written by facebook to aggregate logs. It's designed
124124
to run on multiple servers and scale with the rest of your cluster. Uses the Thrift messagaing format so it can
125125
be used with any language. </li>
126+
</ul>
127+
<h2>Logging resources</h2>
128+
<ul>
129+
<li><a href="http://www.hybridcluster.com/blog/logging-storytelling/">Logging as Storytelling</a>
130+
is a multi-part series working the analogy that logs should read like
131+
a story so you can better understand what's taking place in your web
132+
application.
133+
<a href="http://www.hybridcluster.com/blog/logging-storytelling-lets-add-action/">Part 2 describes actions</a>
134+
and
135+
<a href="http://www.hybridcluster.com/blog/logging-storytelling-3-types/">part 3 talks about types</a>.</li>
126136
</ul>
127137
<br/>
128138
Next read the

source/content/pages/19-logging/1901-logging.markdown

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,7 @@ log data to Sentry for aggregation. Sentry provides a clean web application
2828
interface for viewing the exceptions. Sentry can also be configured with a
2929
mail plugin to send emails when exceptions occur.
3030

31+
3132
## Logging Aggregators
3233
When you are running your application on several servers, it is helpful
3334
to have a monitoring tool called a "logging aggregator". You can configure your
@@ -37,6 +38,7 @@ provides tools such as to viewing searching, and monitoring logging events acros
3738
Another advantage of log aggregatortion tools is they allow you to set up custom alerts
3839
and alarms so you can get notified when error rates breach a certain threshold.
3940

41+
4042
### Log Aggregator Third Party Services
4143
* [loggly](https://www.loggly.com/) Loggly is a third party cloud based application that
4244
aggregates logs. They have instructions for every major language, including python. It includes email
@@ -46,6 +48,7 @@ integration with S3 for
4648
* [splunk](http://www.splunk.com/) Splunk offers third party cloud and self hosted solutions
4749
for event aggregation. It excells at searching and data mining any text based data.
4850

51+
4952
### Open Source Log Aggregators
5053
* [Graylog2](http://graylog2.org/) Provides a central server for log aggregation as well as a GUI for
5154
browsing and searching through log events. There are libraries for most major languages, including python.
@@ -55,3 +58,13 @@ configure log data workflows.
5558
* [Scribe](https://github.com/facebook/scribe) A project written by facebook to aggregate logs. It's designed
5659
to run on multiple servers and scale with the rest of your cluster. Uses the Thrift messagaing format so it can
5760
be used with any language.
61+
62+
63+
## Logging resources
64+
* [Logging as Storytelling](http://www.hybridcluster.com/blog/logging-storytelling/)
65+
is a multi-part series working the analogy that logs should read like
66+
a story so you can better understand what's taking place in your web
67+
application.
68+
[Part 2 describes actions](http://www.hybridcluster.com/blog/logging-storytelling-lets-add-action/)
69+
and
70+
[part 3 talks about types](http://www.hybridcluster.com/blog/logging-storytelling-3-types/).

0 commit comments

Comments
 (0)