Poke

@Dennis I have also not been around lately and just saw your messages from Feb 2020. Hope you're doing alright, bud. You are one of my favorite individuals on this site. Let me know if there's anything I can do to help

don't think i've mentioned it in here yet... i'm switching jobs :] tomorrow is my last day with my current employer

@Lyxal java wouldn't let you do that

that is forever in tech lol

i can't imagine that's a secure web browser in 2020

not sure what OS you're on, but it sounds like you need to update or get a new browser

well no shit, lol. safari 5 came out a decade ago?

@AdmBorkBork always golf

what a mess

bleh

i'm also updating sql versions

that's true

well like worst case you dual write all your data

that's what i figured :P

not sure how feasible that is

If possible I'd love for it to not require code changes on the application side

with minimal downtime :\

@BradC Oh neat. Do you have any ideas/suggestions for updating from a mirrored database to an alwayson cluster?

Any big sql server fans in here?

wtf

and that accepted answer

What the heck is this softwareengineering.stackexchange.com/questions/404737/…

they tell me things

i've got buddies who work in fang

yeah their stuff is crazy

:D

that's 20k, 40k, 60k

oops i cut the y-axis

anyway that's nothing compared to the infrastructure that i actually own i.imgur.com/GK7b7bM.png

nooooo, definitely not :P

whaaat

eep

cough

don't worry about the fact that it was like 50k hits/day

yes, the number of calls

The API has some logging but the "client ip" that was listed was for an address in a SNAT pool... so I had no idea which host

oops :]

that hadn't been updated in a while

spoiler alert... it was our dev server

@DJMcMayhem There was an API that was being retired and my team was still hitting it in a few places. The large jumps down in that graph represent me finding our use of the API and updating the code to hit a newer supported version. That last little bump was annoying me because I didn't know where the requests were coming from... only that they were with my team's service account. Finally figured out where it was and killed it

you both rock

:]

someone please appreciate this with me

so I had to really dig into the ole noggin

The folks who manage the API didn't have comprehensive logs and thus could not tell me where the code lived

mmmmmmm

right at the end there you can see the empty gap of no requests

feels good

there is always the consideration that you might be over-engineering something too