Postgres db having regular 70B "spike" of egress despite no TCP proxy
I want to preface this by saying that this is not a pressing issue of any sort, and mostly just curiosity.
My Postgres database communicates with my discord bot (java - I sincerely regret that decision) over the private network, and since i never look at the database tables, I decided it would be a smart idea to disable the TCP proxy, as I wasn't using it. I also noticed a reasonably regular 70B "spike" of egress (as opposed to the expected 0, since I should be the only one talking to the database, and I am doing so solely over the Private Network). I wrote it off as perhaps a crawler or something indexing that ip. After removing the TCP proxy, the 70B spikes persisted, however, even through redeploys.
Attached you find a screenshot of my network graph, for the last 6 hours
What is my Postgres service sending?
8 Replies
Project ID:
1a73e8f4-a61d-4a67-9bd7-3539b677698bim kinda colour blind, are we talking about these tiny bumps?
yes! my apologies, i didnt know. It's those small bumps. They happen semi regularly
If you want i could try and see if i can get a lightmode screenshot for you if that helps?
haha no no, im not monochromatic.
so removing the tcp proxy does stop incoming traffic from reaching the container, but it doesnt cut off outgoing internet connections, could be something as simple as an ntp update
I'm not familiar with that term. A quick google returns it's some sort of time synchronisation?
correct, just a guess, could be so many things
Well, at least it's nothing out of the ordinary, and hey, I learnt something new! Thanks Brody!
no problem! 🙂