Inside Nile SLA Commitments: Availability, Coverage & Air Quality

Transcript:

SCREEN 1  — Nile Tile

 Welcome back! In this demo, lets dig deeper in to the Nile Tile

As you know this isn't a passive view. Our physical and dedicated radio sensors are actively monitoring the network every single minute, around the clock.

Right now the dashboard is scoped to the last two hours, and as you can see, everything is green. That's the steady state you want to be in.

But to really demonstrate the value of this level of visibility, let me expand the time window. I'm going to set time filter  to the last seven days.

SCREEN 2  — Nile Tile— 7-Day View

Now we can see the full picture across the week.

You'll notice we had some fluctuations in two key metrics — Availability and Coverage. These are the two dimensions Nile tracks as part of the SLA commitment.

Now let me zoom in. I want to walk through what happened at the TX Building specifically.

SCREEN 3  — TX Building — Availability Event

Here we are at the building level for our Texas site.

As you can see, we had an availability impact here. Whenever an outage or degradation event occurs, the system automatically creates an event record — you don't need to go hunting for it. It surfaces right here in context.

You have two ways to investigate: you can click directly on the event in the timeline, or you can drill down by floor to pinpoint exactly where the issue was occurring.

 Let me click into this event — you can see it ran for 276 minutes. That's a meaningful incident, and I want to show you exactly what we captured.

SCREEN 4  — Event Detail — Availability Deep Dive

 Clicking the event drops us directly into the minute-by-minute timeline, anchored to exactly when the event started — in this case, May 23rd at 4:49 AM.

This chart is doing a few things at once, so let me break it down.

First, it shows you when availability was impacted, minute by minute. Second — and this is something unique to Nile — it overlays Air Quality Index data, or AQI. Why? Because our monitoring relies on probes in the environment, and if air quality drops below a certain level, it can affect probe readings. Specifically, an AQI value below 35 can impact the probes.

So when you're looking at availability data and you see an AQI flag, that context is already baked in. You're not chasing a false positive, and you're not missing a real issue — the system accounts for environmental conditions automatically.

This is minute-by-minute, timestamped data. When a user calls in at 5 AM saying they couldn't connect, you don't need to recreate what happened — it's already documented.

SCREEN 5  — Healthy Availability — Baseline Comparison

Before we move on to coverage, I want to show you what a clean availability record looks like — just for contrast.

This is a healthy example. Every minute is green. No gaps, no partial minutes, no flags. 

This is the baseline your team can hold us to. When every row is green, the network delivered on its availability commitment for that entire period.

 Now let's go back up to the building level and look at the coverage metric.

SCREEN 6  — TX Building — Coverage Event

Back at the building view, we can see there was also a coverage-related event.

Just like with availability, the event is surfaced automatically. No manual log review, no ticket needed to find it.

Let me click into this event to show you the same level of detail we just saw on the availability side.

SCREEN 7  — Coverage Event Detail — Signal Threshold

 Here's the coverage detail view.

Our threshold for coverage is -67 dBm. If the signal strength falls below that value — or registers as zero — that minute is marked red and it counts against the SLA.

 Again, this is minute-by-minute. You can see exactly when the signal dropped, for how long, and on which floor or zone.

Let me wrap up with a quick summary of what we just walked through.

Nile deploys physical, dedicated radio sensors that monitor your campus network 24 hours a day, seven days a week. Every minute of data is captured and stored — availability, coverage, capacity, signal strength, environmental conditions.

When a user calls your helpdesk and says they had a connectivity issue this morning, that information is already in the portal. The time, the location, the cause — it's all there. You're not spending hours trying to reproduce the problem.

And what we'll cover in future sessions is how this same data feeds into proactive alerting — pushing events directly into your ITSM before your users even pick up the phone.

Thanks for watching.