Case study 9 of 12 · /resources/case-studies/tnbt

Ops monitor design

Finding unusual operational changes, so it opens on a dark monitoring screen with one anomaly flagged.

For review: SEO and checks (not shown to visitors)
SEO title
TNBT Tech Case Study | DevOps TechLab (37 characters)
Meta description
Operational questions in plain language; data-backed answers without writing SQL. How DevOps TechLab built it on AWS. (117 characters)
URL
/resources/case-studies/tnbt
Keywords
Amazon Bedrock, Nova Pro, ECS Fargate, Aurora PostgreSQL
Check before publishing
  • Rewritten from the case study on devopstechlab.com (PDF supplied 1 Oct 2026). No figures added beyond the original page.
  • Client has agreed to be named on the new site (confirmed 1 Oct 2026).
  • PENDING: original diagram file from the team, to replace the crop from the PDF.
  • PENDING: real figures from the team (time saved, speed or volume), measured with the client.
  • The original page contains an internal editorial note about unverified metrics. Remove it from the live site.
  1. Home
  2. Resources
  3. Case studies
  4. TNBT Tech
AI & GenAIAWSQueryDashClient story

TNBT Tech

AI agent that finds unusual operational changes and their likely causes

Operational questions in plain language; data-backed answers without writing SQL. Built on QueryDash, our agentic investigation platform on AWS.

Told by a Generative AI Engineer from DevOps TechLabOperations2 min read

The client

TNBT Tech uses QueryDash, our agentic investigation platform, for operations.

A typical question the agent answers. “Identify unusual operational changes and determine their likely causes.”
QueryDash is our agentic investigation platform on AWS: people ask questions in plain language, and an AI agent investigates the data and explains what it found.

The challenge

  • Investigating operational data and spotting unusual changes meant manual SQL across many queries.
  • Complex investigations were slow and relied on technical staff.

How the agent works

The agent loop

Understand the goal. The agent restates what you are trying to find out.

Production data stays protected. Every SQL statement is validated before it runs; write and schema-changing operations are rejected.

What we did

  1. 1Discovery

    understood the questions users needed answered, the data and how it relates, and defined secure, read-only access to production data.

  2. 2Platform

    QueryDash, our agentic investigation platform on AWS. A React web app on CloudFront and S3, an Application Load Balancer, the agent on Amazon ECS Fargate, Amazon Bedrock with Amazon Nova Pro, conversation and investigation memory in DynamoDB, credentials in AWS Secrets Manager, monitoring in CloudWatch.

  3. 3The agent loop

    understand the goal, plan, discover the data, generate SQL, validate it as read-only, execute, analyse, then replan or retry until it can explain the answer.

  4. 4Safety

    every SQL statement is validated before it runs; write and schema-changing operations are rejected.

  5. 5Onboarding

    database connectivity, Bedrock and Nova Pro configuration, secure credentials, read-only SQL validation, conversational context, real-time streaming and validation of representative scenarios.

  6. 6Operations

    application, infrastructure and agent monitoring, query support, troubleshooting and ongoing tuning of planning, SQL generation and recovery.

The architecture

Architecture as built (QueryDash platform)
  • Amazon Bedrock
  • Nova Pro
  • ECS Fargate
  • Aurora PostgreSQL
  • DynamoDB
  • Secrets Manager

The result

  • Users ask in natural language instead of writing SQL or waiting for a technical team.

  • The agent runs multi-step investigations, recovers from failed queries and shows evidence for its findings.

  • Follow-up questions keep the context of the investigation.

  • Production data stays protected with read-only, validated access.

  • The same platform extends to new questions without building a new analytics workflow each time.

Want something like this for your team?

Tell us the questions your team asks or the work that slows you down. An engineer will suggest a small first build on Amazon Bedrock.

Next story · AI & GenAIDexlyn: Autonomous BI agent that explains what drives revenueDriver tree design · 2 min read