Starting with Agent version 1.59 ruxit shows more if its power. It now gives you service visibility into all, even un-instrumented, processes (i.e., processes where ruxit doesn’t even have an agent!).
How does this work?
This works whenever we have a deeply monitored process on the calling side. Using the example shown, by understanding the Web request called from the RuxitIconography Web request service, and knowing the network connections of all monitored hosts, we know that RuxitIconography makes Web requests to CouchDB. The same works for Apache and
mod_proxy calls. What’s more, because of this, ruxit can now correlate process- and infrastructure-level problems on un-instrumented processes to the mapped service and from there to the callers of the service. In other words, if RuxitIconography slows down because CouchDB has a disk issue, ruxit will know and tell you!