Hello, everybody and welcome to the ThoughtWorks Technology Podcast. My name is Rebecca Parsons,

the chief technology officer for ThoughtWorks. I'm one of your hosts. And I'd like to introduce

the rest of the panel for today. Then we'll talk a little bit about observability and monitoring.

So, Neil. Hi, everybody. I'm Neil Ford, director and meme wrangler at ThoughtWorks and another of your

regular recurring hosts. And today we have a couple of our colleagues who are quite interested

in the subject we're going to talk about today. So I'll let them introduce themselves.

Barani. Hello, this is Barney

Subramaniam. I'm head of technology, Thorntz, India. Hello, this is Prasanna. I'm also the head of

technology for Thoughtworks India. We can find that out later. We have three, actually. There are two of us here.

Okay, so we'd like to talk to you today about observability and monitoring.

And there wasn't necessarily a whole lot to talk about when everything was running in a

JVM on a single process, you know, life is good.

But we have encountered multiple situations where we've had to

start to tease apart the distinction between these two things when we're in a distributed

architecture world. So let's start with the basics. Barani and Prasana, how do you define the difference

between the activities of monitoring and observability

and what the outcomes are that we're trying to achieve?

Right. I would define monitoring as a continuous process of checking the output of the system.

Right. So it can be anything like,

is the process alive?

Are we getting the heartbeat?

Or the less latency is satisfying the SLA.

...