Christine Bodegaro

But how many nodes you need per cluster is really up to the customer to define what that payload looks like and what they want to capture.

Yeah, it's probably going to be between five and seven just because early, you know, and there's going to be probably a phase, right?

You may not want all of your APIs right away.

We run in production.

So that can be a healthy amount of data.

And you may not want that same level of detail around all of your APIs.

So that's where there's some variability.

Um, and as you add new partners, et cetera, that volume will likely grow.

So Christine start three and five.

Yeah, yeah.

So a bit of our origin story, I'll give you that very quickly.

And that is that a very large hardware manufacturer, fruit-based hardware manufacturer, had a precipitous drop in their online store once they launched a new version.

Couldn't figure out what it was.

rolled in there with our solution and tracked and logged all of the calls and was able to then say, where are they failing?

What's happening?

So we knew what process and then being able to say, how are these alike and figuring out what that cohort looked like.

And it turns out it was all clustered around a zip code failure.

So it was a trailing zero error.

which means that anything in a zip code ending in zero would fail.

And so people kept trying to buy and it would say, nope, nope, not a valid zip code.