---
title: "Discussion on \"The dashboard is green and one of your models is not on it\" | Hashnode"
description: "Discussion on \"The dashboard is green and one of your models is not on it\". Amazon Bedrock AgentCore Observability natively covers only agents on AgentCore runtime in AWS. On August 13, 2026 AWS published a walkthrough for wiring up agents running on-premises and on other clo"
url: "https://hashnode.com/posts/the-dashboard-is-green-and-one-of-your-models-is-not-on-it/6a8158f7ad2d365d301c37ab"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The dashboard is green and one of your models is not on it](https://blog.bhuveshdhiman.com/the-dashboard-is-green-and-one-of-your-models-is-not-on-it?utm_source=hashnode&utm_medium=feed)

Amazon Bedrock AgentCore Observability natively covers only agents on AgentCore runtime in AWS. On August 13, 2026 AWS published a walkthrough for wiring up agents running on-premises and on other clo

Aug 16 · 2 min read · blog.bhuveshdhiman.com  
Read the article

-   [#ai](https://hashnode.com/tag/ai)
-   [#ai-agents](https://hashnode.com/tag/ai-agents)
-   [#observability](https://hashnode.com/tag/observability)
-   [#llm](https://hashnode.com/tag/llm)

## Written by

[Bhuvesh Dhiman](https://hashnode.com/@bhuveshdhiman)

@bhuveshdhiman · Mumbai, India

  
[View profile](https://hashnode.com/@bhuveshdhiman)

Sharing learnings as a senior software engineer

## Responses 1

Markdown supported · ⌘↵ to post

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Aug 17](https://hashnode.com/posts/the-dashboard-is-green-and-one-of-your-models-is-not-on-it/6a8158f7ad2d365d301c37ab/comment/6a831f5ce1cd816acf9acde6)

The line about an absent metric looking exactly like a low one is the trap, because auto-instrumentation is sold as the thing you stop thinking about, which is precisely why nobody audits its gaps. I run a synthetic call with known token counts through each model path and fail the check if the emitted usage does not match, which surfaces the silently-dropped path fast. Do you assert expected-vs-emitted token counts anywhere, or catch these by eyeballing the cost chart?
