Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am currently monitoring the logs of produced by our application server. But before I can do that, I would have to know which server's logs I would go to. To do this I do a tail of both logs and watch which of the logs "run" when I navigate to that page. If one of the logs run then I know which server I would go to for monitoring. This becomes complicated however, when both logs run at the same when I key in the the url of the application. When that happens what I do is login and then after logging in, I stop both logs and read my login name in both of them. Only then will I know which server I am using.

Is there an easier way to do this? Maybe I can use a packet sniffer like wireshark or something. Our application is both accessible on the public web as well as the intranet.

share|improve this question

migrated from Nov 24 '10 at 19:37

This question came from our site for computer enthusiasts and power users.

I often just stick some commented text into the HTML that includes the local server name or at least identifies it without necessarily having the hostname, then check for it when loading the page.

share|improve this answer

You can let the load balancer add a header, preferably not a real hostname, but one that would allow you to understand which server it is.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.