[Logstash]: Node/Pipeline Health Report: Make sure the colour schema corresponds to the status name

[herrBez]

Integration Name

Logstash [logstash]

Dataset Name

• logstash.node.status
• logstash.pipeline.status

Dashboard Affected

• [Metrics Logstash] Pipeline Health Report
• [Metrics Logstash] Node Health Report

Integration Version

2.10.1

Agent Version

9.3.2

OS Version and Architecture

Elastic Cloud

User Goal

Having a better overview of the current status:

• Green should map to green
• Yellow to yellow
• Red to red
• Unknown to gray

Existing Features

Currently the dashboard display a strange colour schema;

• Green is mapped to green ✅
• Yellow to "pink/red" ❌
• Red to yellow ❌
• Unknwon to gray ✅

What did you see?

The coloring schema of the Dashboard Logstash Node Health is confusing:

Anything else?

No response

[github-actions]

tl;dr I can reproduce a status-color schema inconsistency in the Logstash Node Health dashboard definition: one logstash.node.status visualization maps green/red/yellow/unknown, but the Node Health datatable status column maps only red/yellow/unknown, so the schema is not consistently defined per status name.

Recommendation
Update the Node Health datatable status column in packages/logstash/kibana/dashboard/logstash-9a72208d-e446-48b9-8a63-c4256b9aa4e3.json to use the same explicit status mapping as the other Node Health visualizations (include green in colorMapping.assignments, aligned with red/yellow/unknown).

Findings

• Node Health chart mapping includes all status names:
  • packages/logstash/kibana/dashboard/logstash-9a72208d-e446-48b9-8a63-c4256b9aa4e3.json:282-339
  • Includes rules for red, green, yellow, unknown.
• Node Health datatable status column mapping omits green:
  • packages/logstash/kibana/dashboard/logstash-9a72208d-e446-48b9-8a63-c4256b9aa4e3.json:829-872
  • Includes only red, yellow, unknown.
• Pipeline Health datatable has full explicit mapping including green:
  • packages/logstash/kibana/dashboard/logstash-838aac39-8edd-48b0-95b4-289e42b1e98a.json:2665-2708.
• Data ingestion passes status through directly (status: body.status), so this is dashboard mapping/config, not ingest parsing:
  • packages/logstash/data_stream/health_report/agent/stream/stream.yml.hbs:33.
• Related historical work:
  • Health report dashboards introduced in PR #12677.
  • Later health_report updates in PR #17401.

Verification

I validated by inspecting the saved object JSON in-repo:

$ nl -ba packages/logstash/kibana/dashboard/logstash-9a72208d-e446-48b9-8a63-c4256b9aa4e3.json | sed -n '276,339p;829,872p'
# 276-339: Node Health chart colorMapping has red/green/yellow/unknown
# 829-872: Node Health datatable colorMapping has red/yellow/unknown (green missing)

$ nl -ba packages/logstash/kibana/dashboard/logstash-838aac39-8edd-48b0-95b4-289e42b1e98a.json | sed -n '2665,2708p'
# Pipeline Health datatable colorMapping includes green/red/yellow

Note: I couldn’t read issue bodies for related issues due repository-integrity policy restrictions in this run, so duplicate analysis was limited to accessible PR/changelog references.

Detailed Action Plan

1. Edit packages/logstash/kibana/dashboard/logstash-9a72208d-e446-48b9-8a63-c4256b9aa4e3.json in the Node Health datatable column block around :829-872.
2. In visualization.columns[].colorMapping.assignments, add a green rule mirroring the existing schema used elsewhere in the same dashboard (e.g., colorIndex: 0, paletteId: eui_amsterdam_color_blind, rule.values: ["green"]).
3. Keep red, yellow, unknown mappings unchanged to avoid behavior drift.
4. Re-export/refresh the dashboard object and confirm status cells render with consistent semantic mapping for all status names.
5. Add a changelog entry if package version bump is needed for dashboard-only fix.

Related Items

Type	Link / File	Relevance
PR	#12677	Added Logstash Health Report data and dashboards
PR	#17401	Later health_report-related updates
File	packages/logstash/kibana/dashboard/logstash-9a72208d-e446-48b9-8a63-c4256b9aa4e3.json:282-339	Node Health chart full status mapping
File	packages/logstash/kibana/dashboard/logstash-9a72208d-e446-48b9-8a63-c4256b9aa4e3.json:829-872	Node Health datatable mapping missing green
File	packages/logstash/kibana/dashboard/logstash-838aac39-8edd-48b0-95b4-289e42b1e98a.json:2665-2708	Pipeline datatable full status mapping
File	packages/logstash/data_stream/health_report/agent/stream/stream.yml.hbs:33	Confirms status ingest source

Note

🔒 Integrity filter blocked 4 items

The following items were blocked because they don't meet the GitHub integrity level.

• #18627 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #18627 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #12464 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #12465 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

---

What is this? | From workflow: Issue Triage

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.