rik/blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix typo

Browse Source
This commit is contained in:
Danny Berger
2014-11-26 10:30:19 -07:00
parent 0d488bec3b
commit 2488ed3c5d
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
blog/_posts/2014-11-14-logging-logging-and-finding-bottlenecks.md
View File

@@ -48,8 +48,8 @@ message and indicating when the log message was originally emitted. However, whe
was up to an hour delay between seeing the messages in dashboards and we had no way to measure how long messages were was up to an hour delay between seeing the messages in dashboards and we had no way to measure how long messages were
stuck nor see where they were stuck. We decided to inject a few more fields into events... stuck nor see where they were stuck. We decided to inject a few more fields into events...
First, we wanted to know when log messages were first entering our logsearch stack. This would be help validate that First, we wanted to know when log messages were first entering our logsearch stack. This would help validate that our
our shippers are pushing data into the cluster in a timely manner (rather than significant batching or simply getting shippers are pushing data into the cluster in a timely manner (rather than significant batching or simply getting
stuck). To do this, I configured ingestors to add the current time to every message when it came in. I also added stuck). To do this, I configured ingestors to add the current time to every message when it came in. I also added
fields documenting which BOSH job received the message to help us keep an eye on how balanced the ingestors may be. fields documenting which BOSH job received the message to help us keep an eye on how balanced the ingestors may be.
So, now our messages have a few additional fields... So, now our messages have a few additional fields...