[rsyslog-notify] Forum Thread: Re: RSyslog not sending messages - (Mode 'reply')

[noreply at adiscon.com]

User: troy 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=25201#p25201

Message: 
----------
I need to clarify @lethalduck's comment that:

> It sounds like papertrail don't have much insight into their own system.

We have a ridiculous, off-the-charts amount of insight into our own system,
including thousands of metrics on how Papertrail is performing and complete
end-to-end blackbox monitoring -- that is, we automatically send "canary"
log messages to Papertrail and confirm they arrive at the data store.

There's a reason that many of the repos on <!-- m --><a class="postlink"
href="https://github.com/eric?tab=repositories">https://github.com/eric?tab=repositories</a><!--
m --> (one of the people behind Papertrail) are about instrumentation,
monitoring, on , including a ton of work on aphyr's riemann (<!-- m --><a
class="postlink"
href="https://github.com/eric/riemann">https://github.com/eric/riemann</a><!--
m -->) and porting codahale's metrics library to Ruby (<!-- m --><a
class="postlink"
href="https://github.com/eric/metriks">https://github.com/eric/metriks</a><!--
m -->). These are not hallmarks of lacking "insight into [our] own system."

What we don't have is a way to dedicate a few days to troubleshooting a
sender-specific problem, nor to replay a TCP session merely because we want
to. While we generally provide a lot of client support and get a kick out
of doing it, providing thousands of dollars of support specific to your
system, for free, isn't reasonable. If I had a few more weekends of my own,
I - and everyone on our team - would personally enjoy troubleshooting a
system-specific compatibility issue. That's not a lack of insight, though.

Troy