Do you recognize a good idea when you see one? We want to hear from you!
Header Image

I suggest you ...

Add Interface information to logs

For troubleshooting purposes, including the interface that a packet/URL is going out would be very helpful.

While viewing a live log I would just need the interface, eth0, eth1, br1, etc, added to the line so that I can be sure that my multipathi rules are working.

For example:

2010:05:12-07:17:47 proxy httpproxy[4561]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="GET" srcip="192.168.0.2" user="" request="0" url="http://somelink.com"; INTERFACE="eth1"

9 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Michael WilsonMichael Wilson shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Michael WilsonMichael Wilson commented  ·   ·  Flag as inappropriate

        Often times I don't have access to the command line, so no that wouldn't be an option. The Bandwidth monitor doesn't offer FQDN, just IP address so it's not all that helpful. Plus I can't filter the bandwidth monitor like I can the live log.

      • Bob AlfsonBob Alfson commented  ·   ·  Flag as inappropriate

        Interesting. I'm going to bet that the information in the HTTP log is generated long before the Astaro "knows" which interface a message will use, but I'd be interested to hear from someone who's not just making an educated guess like I am.

        Michael, can you get the information you need from tcpdump at the command line or the Bandwidth Monitor from the Dashboard?

      Feedback and Knowledge Base