The Thawing Triage Part 4

Baldev continued, "There has been a multi-disciplinary change in the organizational hierarchy which lead to a top-down approach of analyzing incidents rather than the bottom-up methodology and we are still in terms of streamlining this newer approach wherein Incidents are escalated and de-escalated as per the standard procedure which is still under de facto construction, which means that the intrinsic modus operandi has been either updated or upgraded, We will channelize the necessary forces to debug and detest the same."

"Yes you are right" said Cicily ,"The whole operational procedure needs to be re-visited so that the business impact is mitigated as quickly as possible as we are on the verge against the race of time"

What are they talking about?  Wondered San .

Meanwhile the Infrastructure guy confirmed on the channel that there were no issues observed within his workspace.

There are a beep sound. "Guy this is Challam (VenkataChallam) , Program Director for ITRADE support. I was pulled in to the call, Can someone brief me the issue and the steps being taken to resolve the issue with the Root Cause Analysis?"

Baldev Reiterated the issue.

"Do we know the clear impact? Have we downgraded the application? Do we know how much head room we have to mitigate the impact??" Rumbled Challam.

Baldev briefed him.

why dont they just record and play the issue? pondered San still debugging the issue.

 "Hands on deck guys hands on deck!" Shouted Challam. "We need to mobilize our forces to channelize our energies into issue resolution. Do what is to be done and try to expedite the issue, I need to get onto another call will be right back" And he disappeared.

Thank god, My ears are at ease thought San.

The Thawing Triage : Part 3

San dialed into the Triage and announced his name and team name, within seconds all the other relevant teams started dialing in one by one, whenever some one dialed in there was a beep sound, followed by their announcement.
Mr Jenkins made his statement : Seems every one necessary has dialled in, please keep the Bridge updated with information and if any help required done hesitate to contact me.

 ******** Bridge Opened for ITrade Application Outage **********

Bang on!!

The bridge started the operation,

Can someone please brief the issue?? I understand there is an outage in Itrade Application but don't have the specifics. Said Mr Benedict from the Infrastructure Team,

"We received alerts and then we started investigating the issue.. it seems.. "

"It was I who notified the Support on the incident" Suddenly Cicily screamed cutting sort of San's explanation.  Cicily was a business user who unknown to San was also called as High Pitch. She was known to scream and batter her way in calls. "Only after I called was the issue looked into!!"

"Guys Guys Guys!!" Yelled another voice "What is this I am hearing, who is from Support? Why wasnt this looked upon proactively?? We should have notified the stakeholders before they coming to s...  I can see a huge gap here.. This is Baldev here" Baldev was the Project Manager for ITrade.

San was perturbed, "What's happening?" He thought, people are more focused on rants than issue resolution. And the gap he was talking about might be in milli seconds!!

San stepped forward. "I am in the shift currently, I saw the alert and promptly followed the protocols.."

"This is not about just following the protocols, we need to communicate fastidiously to the stakeholders. Can you send notification asap!!" Thundered Baldev.

"I already sent .. "

"Send another with the current status that bridge is open and the appropriate steps are being taken to mitigate the Risk associated with the Outage ASAP!"

San head started aching, He looked at Bakhsi who was eating popcorn now sitting in his room. Lucky fellow he thought.  He pinged him.

San: Bakshi, i might need some help in driving the call, everybody is banging me left and right

Bakshi: Sorry yaar, I am really busy, I am working on business analytics to forecast which needs to be delivered within 6 months, really busy..

Six months?? You said as if it were 6 minutes!! thought San.
There is no use, San understood, he had to drive the call himself.

Baldev continued his speech. "Cicily I am extremely sorry that this had to come to you to gain traction, we will note this in our AGM Dashboard and will be streamlining the process with Multitude Pipeline methodology. Let's focus on the resolution currently and we will take up the rest with our Post Incident Review call."

San started reviewing the back end scripts now. He was trying to understand the issue as why the process went down in the first place, however he could see the script was more than 1K lines long without any proper documentation.

Wait Three Seconds!

An interesting piece of code from Java Script : Understanding the Weird Parts

//long running function

function waitthreeseconds(){

    var ms = 3000 + new Date().getTime();

    while (new Date() < ms){

        

    }

    console.log("Function Finished")

    }

waitthreeseconds();

The Thawing Triage: Musing of IT Industry : Part 2

"This should be a Severity 1 incident! We need to this to be resolved ASAP!!
The lady on the call started yelling.
San shuddered, "Yes Cicily I am working it.. "
"I am getting another call, let me know the details ASAP!!" She cut the call.
San's ears were filled with the words ASAP.  It was easier said than done.  He quickly dusted his ears and rubbed his eyes. He looked at the CC (Command Center) chat room and could see a Mr Jenkins respond.  He put in a long listing of Issue details in the chat.

Mr Jenkins: Please fill in the below details so that we can raise this as a Major Incident.

             Incident Description:
             Business Justification:
             Incident Ownership
             Severity
             Incident Queue:
             Time of the outage:
             Teams required:

OMG! thought San, He knew that he will be asked all these details while shadowing Bakshi, but there was never a single Major Incident in the past one week of Knowledge Transfer. Everything he saw was through some sort of Wiki Documentation.

He quickly started filling the template with whatever information he had.  He knew there were situations when even after filling in details The CC guys didn't give a triage stating that the justification was not enough.
Also parallelly he sent out an incident communication using another template he managed to pull out from Wiki.

He pasted the detail in the CC chat room and shivered. There were beads of perspiration on his forehead though the AC in the room was full. He made a quick glance at Bakshi - He had his headphones on now and was swinging left and right making strange hand signals. He is enjoying music while I am facing music here thought San.

Mr Jenkins: Though the issue desription is not fully clear, keeping that this is impacting Trading, I am giving you the Major_INC_2 channel. You will find the dial in details in the channel.

San: Thank you!!

Thank god thought San, Atleast the first step is done. He quickly accessed the Major_INC_2 channel and was about to dial in when his phone again rang. He could see Chandan Sahu who was the Program Manager on the dial pad.
 (People used to call him Chan - AKA Jackie Chan,also BP Chan (Blood Pressure Chan).  He picked the call.
"Hey is this Sanmugham??"
"Yes chan"
"What the hell is going on? No one from the Support team has opened any Bridge call ? It had been 6 minutes that the incident has been reported?? Have we done the service degradation?? Have we notified the Stake Holders??"

Baap re!! San was dumbfounded. "I have followed the process, have opened the Triage..."
"What process have you followed?? Can you show me the documentation?? " The pounding continued..

Meanwhile in the incident chat Mr Jenkins started pinging asking if someone is joining the call, if not within 10 seconds he had to release the bridge as per the protocol.

"Chan they have opened the incident channel, let me join there to address the issue"
"Ok! " Chan slammed the phone down (San could hear the banging sound).  He should be given a BP tablet 

Fizz BUZZ!!

let number= 1;

while (number<= 100){

        if (number%3 === 0){

        console.log("Fizz");

        }

    else if (number%5 === 0){

        console.log("Buzz");

    }

    else{

    console.log(number);

    }

    number = number + 1;

}

1
2
Fizz
4
Buzz
Fizz
7
8
Fizz
Buzz
11
Fizz
13
14
Fizz
16
17
Fizz
19
Buzz
Fizz
22
23
Fizz
Buzz
26
Fizz
28
29
Fizz
31
32
Fizz
34
Buzz
Fizz
37
38
Fizz
Buzz
41
Fizz
43
44
Fizz
46
47
Fizz
49
Buzz
Fizz
52
53
Fizz
Buzz
56
Fizz
58
59
Fizz
61
62
Fizz
64
Buzz
Fizz
67
68
Fizz
Buzz
71
Fizz
73
74
Fizz
76
77
Fizz
79
Buzz
Fizz
82
83
Fizz
Buzz
86
Fizz
88
89
Fizz
91
92
Fizz
94
Buzz
Fizz
97
98
Fizz
Buzz

Learning JavaScript

My First steps into JS.

Wrote the below simple While Loop to produce triangles.  Will continue to delve into JS.

let triangle= "#";

while (triangle.length <= 10){

    console.log(triangle);

    triangle = triangle + "#";

}

# ## ### #### ##### ###### ####### ######## ######### ##########

First Node JS Webserver

I have started studying  Node.js® : JavaScript runtime built on Chrome's V8 JavaScript engine using online sources. The below is from the book Up and Running Node JS.

Hope to create a mini project sometime.

Below is the code: 

var http = require('http'); 
http.createServer(function (req, res) { 
    res.writeHead(200, {'Content-Type': 'text/plain'}); 
    res.end('Hello World\n'); 
}).listen(8124, "127.0.0.1"); 
console.log('Server running at http://127.0.0.1:8124/');

The Thawing Triage: Musing of IT Industry : Part 1

Sanmugham (aka San) finished his usual breakfast of corn flakes and milk at his desk and again started monitoring (staring intently) at the SmartAlert tool.  As a production support executive fresher, he knew what stay ahead of his day schedule. And till a day before, he was sitting beside his senior Bakshi  shadowing (I.e. just looking) who now got promoted to Level 3 (and attained Moksha) was displaced into a separate room with a desk and chair.

San peeped over his cubicle and could see Bakshi enjoying his new room, he is doing nice time-pass thought San. He could see Bakshi switching between his Deskstop monitor and his mobile phone and jeering.

San was bit nervous, he had to handle everything alone now. Bakshi clearly said he wont help in anymore (which he anyway never did) and he had to prove himself and this meant this even would decide his confirmation from his probationary period.

He opened the Incident Management Tool (Which is an web application to record any issues within systems) and glared at the open less severe Incidents which lay in the queue. He could see someone were assigning them.  God Forbid there shoudn’t be a Severity 1 (which was a critical production infraction) thought San.

He looked at the system clock, it was 9:30 AM.

Suddenly the SmartAlert Tool beeped.  He saw the alert queue turned amber and then RED!

My God, exclaimed San, the Scanner Daemon  process was down. He refreshed the IMT(Incident Management Tool) and could there were continuous Incident getting created. His heart started racing.

This is going to be a major issue, He had to act fast as this could cause an outage to ITrade application which was a regulatory traders app.

Immediately with his shaking hands he opened the Command Center chat room and pinged the Incident details asking for a Triage call (Basically Triage call is a platform with a unique id where various teams join to resolve production issue).

And then a phone rang, he immediately picked it but could see that there was another call appearing in the dashboard, “Hello we are unable to access Itrade application, Can this be addressed ASAP!!” a rude voice yelled from the other side. “Do we have any Triage open??”

“Yeah .. we are working on it..” he fumbled his words.