Exclude shotgun from reports? | ||||||
| posted by Greg Whynott on Jan. 15, 2015, 5:40 p.m. (1 day ago) | ||||||
| ||||||
| Thread Tags: discuss-at-studiosysadmins | ||||||
| ||||||
10 minutes before I leave to go home I start thinking about this.... sure to cause lost sleep too.. anyway.... We had this system in place for years which would monitor uploads to the internet via netflow data. Whenever the upload limit trigger was reached we would get an email alerting us to a 'large upload daily limit reached'. The we started using shotgun online. And the reporting system was spamming us... I seen many of the connections were for amazon and going to the shotgun servers. So I excluded that range. A week or so later shotgun was using other IP blocks. So I wrote them a letter explaining what I was attempting to do and "could you provide me a list of IP ranges we can expect you to use" and the answer was "no, Amazon takes care of that, we don't know what they would be from day to day". Which in all honesty sounds like a crock of dung as that is not how it works typically. What if someone wants to reach your servers via IP? Anyway maybe it is true, I'm not up to speed with how Amazon is running things. so this is my new challenge I'm working on. any ideas? I'm thinking of having a script that does a look up on our shotgun address every hour and excludes IP blocks from the reports each day.. thinking there is something similar... not too keen on setting up a https proxy, but maybe some wire snarfing routine... i'm sure i'll wake up at 3 AM with an "ah-ha" solution, is the way it usually works.. -g |