#tblogs

[sostumbling]

But if you think about me

And you neither tell me about that

Why do you think about me?

Charles Bukowski

[qicktrick]

FACEOFF WIN WE ARE ON FIREEEEEEEEEEE 🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🗣️🗣️🗣️🗣️🗣️🗣️🗣️🗣️🗣️🗣️

Correction: GOAL WE ARE ON FIREEEEEEEEEEEE 🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🗣️🗣️🗣️🗣️🗣️🗣️🗣️🗣️🗣️🗣️🗣️🗣️🗣️🗣️🗣️🗣️🗣️🗣️

[egotisticallyenthralled]

rrate my fit

[deslizada]

ohhhhh my god I need to be railed so bad. just like absolutely ****** ** *** ****. someone please **** ** make me cry and then make fun of me for crying. this happens every time I do my t shot

[cocajimmycola]

HI WE DID NOT SEE THE TAGLIST POST PLEASE IGNORE THE LAST ASK

KEKW

[lazeecomet]

The Story of KLogs: What happens when an Mechanical Engineer codes

Since i no longer work at Wearhouse Automation Startup (WAS for short) and havnt for many years i feel as though i should recount the tale of the most bonkers program i ever wrote, but we need to establish some background

WAS has its HQ very far away from the big customer site and i worked as a Field Service Engineer (FSE) on site. so i learned early on that if a problem needed to be solved fast, WE had to do it. we never got many updates on what was coming down the pipeline for us or what issues were being worked on. this made us very independent

As such, we got good at reading the robot logs ourselves. it took too much time to send the logs off to HQ for analysis and get back what the problem was. we can read. now GETTING the logs is another thing.

the early robots we cut our teeth on used 2.4 gHz wifi to communicate with FSE's so dumping the logs was as simple as pushing a button in a little application and it would spit out a txt file

later on our robots were upgraded to use a 2.4 mHz xbee radio to communicate with us. which was FUCKING SLOW. and log dumping became a much more tedious process. you had to connect, go to logging mode, and then the robot would vomit all the logs in the past 2 min OR the entirety of its memory bank (only 2 options) into a terminal window. you would then save the terminal window and open it in a text editor to read them. it could take up to 5 min to dump the entire log file and if you didnt dump fast enough, the ACK messages from the control server would fill up the logs and erase the error as the memory overwrote itself.

this missing logs problem was a Big Deal for software who now weren't getting every log from every error so a NEW method of saving logs was devised: the robot would just vomit the log data in real time over a DIFFERENT radio and we would save it to a KQL server. Thanks Daddy Microsoft.

now whats KQL you may be asking. why, its Microsofts very own SQL clone! its Kusto Query Language. never mind that the system uses a SQL database for daily operations. lets use this proprietary Microsoft thing because they are paying us

so yay, problem solved. we now never miss the logs. so how do we read them if they are split up line by line in a database? why with a query of course!

select * from tbLogs where RobotUID = [64CharLongString] and timestamp > [UnixTimeCode]

if this makes no sense to you, CONGRATULATIONS! you found the problem with this setup. Most FSE's were BAD at SQL which meant they didnt read logs anymore. If you do understand what the query is, CONGRATULATIONS! you see why this is Very Stupid.

You could not search by robot name. each robot had some arbitrarily assigned 64 character long string as an identifier and the timestamps were not set to local time. so you had run a lookup query to find the right name and do some time zone math to figure out what part of the logs to read. oh yeah and you had to download KQL to view them. so now we had both SQL and KQL on our computers

NOBODY in the field like this.

But Daddy Microsoft comes to the rescue

see we didnt JUST get KQL with part of that deal. we got the entire Microsoft cloud suite. and some people (like me) had been automating emails and stuff with Power Automate

This is Microsoft Power Automate. its Microsoft's version of Scratch but it has hooks into everything Microsoft. SharePoint, Teams, Outlook, Excel, it can integrate with all of it. i had been using it to send an email once a day with a list of all the robots in maintenance.

this gave me an idea

and i checked

and Power Automate had hooks for KQL

KLogs is actually short for Kusto Logs

I did not know how to program in Power Automate but damn it anything is better then writing KQL queries. so i got to work. and about 2 months later i had a BEHEMOTH of a Power Automate program. it lagged the webpage and many times when i tried to edit something my changes wouldn't take and i would have to click in very specific ways to ensure none of my variables were getting nuked. i dont think this was the intended purpose of Power Automate but this is what it did

the KLogger would watch a list of Teams chats and when someone typed "klogs" or pasted a copy of an ERROR mesage, it would spring into action.

it extracted the robot name from the message and timestamp from teams

it would lookup the name in the database to find the 64 long string UID and the location that robot was assigned too

it would reply to the message in teams saying it found a robot name and was getting logs

it would run a KQL query for the database and get the control system logs then export then into a CSV

it would save the CSV with the a .xls extension into a folder in ShairPoint (it would make a new folder for each day and location if it didnt have one already)

it would send ANOTHER message in teams with a LINK to the file in SharePoint

it would then enter a loop and scour the robot logs looking for the keyword ESTOP to find the error. (it did this because Kusto was SLOWER then the xbee radio and had up to a 10 min delay on syncing)

if it found the error, it would adjust its start and end timestamps to capture it and export the robot logs book-ended from the event by ~ 1 min. if it didnt, it would use the timestamp from when it was triggered +/- 5 min

it saved THOSE logs to SharePoint the same way as before

it would send ANOTHER message in teams with a link to the files

it would then check if the error was 1 of 3 very specific type of error with the camera. if it was it extracted the base64 jpg image saved in KQL as a byte array, do the math to convert it, and save that as a jpg in SharePoint (and link it of course)

and then it would terminate. and if it encountered an error anywhere in all of this, i had logic where it would spit back an error message in Teams as plaintext explaining what step failed and the program would close gracefully

I deployed it without asking anyone at one of the sites that was struggling. i just pointed it at their chat and turned it on. it had a bit of a rocky start (spammed chat) but man did the FSE's LOVE IT.

about 6 months later software deployed their answer to reading the logs: a webpage that acted as a nice GUI to the KQL database. much better then an CSV file

it still needed you to scroll though a big drop-down of robot names and enter a timestamp, but i noticed something. all that did was just change part of the URL and refresh the webpage

SO I MADE KLOGS 2 AND HAD IT GENERATE THE URL FOR YOU AND REPLY TO YOUR MESSAGE WITH IT. (it also still did the control server and jpg stuff). Theres a non-zero chance that klogs was still in use long after i left that job

now i dont recommend anyone use power automate like this. its clunky and weird. i had to make a variable called "Carrage Return" which was a blank text box that i pressed enter one time in because it was incapable of understanding /n or generating a new line in any capacity OTHER then this (thanks support forum).

im also sure this probably is giving the actual programmer people anxiety. imagine working at a company and then some rando you've never seen but only heard about as "the FSE whos really good at root causing stuff", in a department that does not do any coding, managed to, in their spare time, build and release and entire workflow piggybacking on your work without any oversight, code review, or permission.....and everyone liked it

[ethanssideblogthingy]

oh i shouldnt hve made hta tblog

[catinca123]

I feel like my Tblog is my little secret because even tho people know I have tumblr they are not bothered to see it because they don’t use

I write here all my thought and I receive no likes and that’s actually amazing like I can’t talk about anyone and they will never know even my best friend but I love that girl if she would see my page she would think I am the weirdest person bc I talk about her that much 😶‍🌫️

[verdantlights]

LMAOOO IT DIDNT TAG MY ALNS TBLOG BUT AGAGWHHAHWH YAAAYY!!! this is @/eventseraphim i just changed it LMAO

if you want, i can make a post regarding assets and profiles, i can even create all assets needed if youd like! as i said, i am very excited to be doing this and im like. vibrating. im so excited.

Welcome to ALNST Season 40!

hello! i’m june, the admin of this account! my main blog is @junebluues. here’s some organizational tags i will be using on this blog:

#! round matchups -> for anything regarding the round brackets!

#round [number] -> this is going to be for easier searching, mostly

#! asks

#! reblog

#! announcements -> announcements can be made at any time! please send me an ask at any time if your oc will be escaping before their round so i can make a proper announcement at the time of your choosing. if there are any other things you’d like me to announce, you can send those over as well!

#! juneposting -> basically things related to me running this blog but not related to any of the rounds or announcements. think of this as me going ooc, in a way? i can't explain it til it happens 😭

(this is subject to change as the season goes on)

i'm not alone in running s40, by the way! i'm only running the blog. so far, zen ( @zerostyrant ) and plip ( @pwippy ) have both offered their help!

here is the masterdoc for all the characters (s39 to some of 41):

participating S40 ocs:

innamorati / @alien-til-i-stage

toki / @eventseraphim ( @zerostyrant )

clove / ^

yumi / @imperfectnothing ( @rockwgooglyeyes )

asuka / ^

dante / ^^

sebastian / @sotogalmo

eeta / ^

naz / @lookatmysillies ( @bluemoonscape )

yael / ^

monica / @nottoonedin

isla / ^

yvonne / @thorny-chaparral ( @aakaneeee )

eliana / ^

aoto / ^^

atlas / ^^^

aamon / ^^^^

cinnabar / @myworld-collapsing ( @apriciticreveries )

asahi / ^

ciaran / @starry-skiez

yuna / ^

eri / ^^

casimir / ^^^

jiu / @severedscales

kioku / ^

numa / my oc!

xael / ^

sirius / ^^

brandon / @neverforgetyou ( @tsukacchako )

willow / ^

mentha / @rosedeleca

ambrosia / ^

mill / @waterydream ( @amuseables )

wren / @ivanttakethis

juliet / @yunoftheclouds

gaia / @subzeromoron

leto / @paradisedisconcert

can / ^

clementine / @chevalperd

maya / @cloverandstuff

ava / @tinypaperstar

if anyone needs me to update this list, please tell me!

other:

please try and send me round songs in advance! if not, i completely understand!

hello,, creators of the s40 announcers... would you like me to use them in announcements in the season? i'm rather confused of their roles in this all, please tell me what you'd like me to do with them.

if there is any lore you need me to know in advance, please don't be afraid to tell me!

don't be afraid to spam notifs on here. the season can get hectic, and i don't mind waking up to people freaking out over rounds

i will sometimes need breaks, please understand! i'll let everyone know when i'll be taking a leave. i think i'll still implement the 1 week breaks between rows. we will still be taking 1 day breaks in between rounds like season 39.

be patient with me! i might sometimes release rounds late. i'm sorry if that happens!

please send me your oc's icons, or any art you'd like to use as their round profile! it would be very helpful!

zen is doing the season bracket, not me! please thank zem for zeir hard work <3 more information on this is in this post!

please enjoy season 40! i'm going to try and see when this should start after s39, and i really want to give everyone enough time to get stuff done. thank you!

(this post may update in the future.)

[sostumbling]

30th March 1853, Vincent Willem van Gogh was born.❤️

[ruanitabr]

Batom Blog Taciele Alcolea T-Blogs : Um Big Beijo

[harlems-hero]

Still never saw a hand raised. Who upset?!?

Melo unlocking them likes is proving nothing. Of course you’ll unlock them now, you’ve cleaned them up so you look safe. We’ve seen all your likes of various different women whether they’re here or not. It’s not cute. Got a good woman yet your eyes are still wondering. It’s sad.

Didn't look very safe to me! I'm just saying, if it was my man, I wouldn't be impressed with him liking all that.

[deslizada]

you know what? fuck it. I do regret getting top surgery. my tits would have looked fantastic with all this hair on them

[cocajimmycola]

im so bored entertain me pls

[missdaytbl]

Beleza não tem padrão Bonito é ser de verdade! #tumblrgirls #tblogs #instatumblr #beautifulgirl #very #blessedforever #blogs #blogday #kiss https://www.instagram.com/p/BsQl85ghrLz/?utm_source=ig_tumblr_share&igshid=zoqiocvhpx6c