opensearch-project / opensearch-project/observability-stack
[BUG] Agent Observability Dashboard: Missing index-pattern-fields for GenAI attributes
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 41
- Forks
- 39
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 10
Description
Description:
Multiple panels in the "Agent Observability" dashboard are failing to load data because the required index pattern fields cannot be located. The dashboard appears to be looking for OpenTelemetry GenAI semantic convention attributes that are either not indexed or mapped incorrectly in the default logs-otel-v1* pattern.
Panels Affected:
- Request Model (attributes.gen_ai.request.model)
- Tool Name (attributes.gen_ai.tool.name)
- Input Tokens (attributes.gen_ai.usage.input_tokens)
- Operation Name (attributes.gen_ai.operation.name)
Steps to reproduce:
Open Dashboards -> Observability -> Dashboards.
Select the Agent Observability dashboard.
Observe the error: Could not locate that index-pattern-field (id: ...) on at least 4 visualization panels.
Expected behavior:
The dashboard should gracefully handle missing fields or provide a clear setup guide to ensure OTel GenAI attributes are correctly mapped as keywords or long values during ingestion.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by opening Dashboards → Observability → Dashboards and reproducing the Agent Observability failure. Inspect how the default logs-otel-v1* pattern is used for the four listed GenAI fields, then determine whether missing fields should be handled gracefully or documented with setup guidance. Done means the affected panels no longer fail without a clear resolution path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100