Skip to content

[redis_otel] Add redis otel content pack - #17681

Merged
Linu-Elias merged 8 commits into
elastic:mainfrom
Linu-Elias:redis_otel
Mar 19, 2026
Merged

[redis_otel] Add redis otel content pack#17681
Linu-Elias merged 8 commits into
elastic:mainfrom
Linu-Elias:redis_otel

Conversation

@Linu-Elias

@Linu-Elias Linu-Elias commented Mar 5, 2026

Copy link
Copy Markdown
Contributor

Proposed commit message

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

redis_otel-overview redis_otel-memory-persistence screencapture-localhost-5601-app-management-insightsAndAlerting-triggersActions-rules-2026-03-05-16_29_44
@Linu-Elias
Linu-Elias requested a review from a team as a code owner March 5, 2026 11:12
@github-actions

github-actions Bot commented Mar 5, 2026

Copy link
Copy Markdown
Contributor

✅ Vale Linting Results

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

@Linu-Elias Linu-Elias changed the title add package Mar 5, 2026
@Linu-Elias Linu-Elias changed the title [redis_otel] add redis otel content pack Mar 5, 2026
@andrewkroh andrewkroh added New Integration Issue or pull request for creating a new integration package. dashboard Relates to a Kibana dashboard bug, enhancement, or modification. documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. labels Mar 5, 2026
@ishleenk17

Copy link
Copy Markdown
Member

@claude review the PR.
Also look at the screenshots of the dashboard for review. Take a look at other opentelemetry packages to review.
Some points to keep in mind while reviewing

  1. Yaml files for dashboards should be there
  2. Category should have opentelemetry
  3. Kibana version should be 9.2.1 and above
  4. Screenshots should be updated in the manifest
  5. discovery.fields should be proper in the manifest
  6. Service logo should have service+ opentelemetry logo
  7. README should have proper collector configuration and versions mentioned in compatibility
@github-actions

github-actions Bot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

Claude finished @ishleenk17's task in 3m 26s —— View job


Review Complete: [redis_otel] Add redis otel content pack

I've reviewed this PR against the specified criteria and submitted an APPROVE review.

Review Checklist:

  • Gather repository context and review other OTel packages
  • Check YAML files for dashboards
  • Verify category includes opentelemetry
  • Verify Kibana version is 9.2.1 and above
  • Check screenshots in manifest
  • Verify discovery.fields in manifest
  • Review service logo (service + OTel logo)
  • Review README for collector configuration and compatibility versions
  • Review dashboard screenshots

Review Summary:

Criteria Status Notes
Dashboard YAML files N/A Dashboards in this repo are JSON (standard practice)
Category has opentelemetry ✅ Pass categories: [datastore, observability, opentelemetry]
Kibana version ≥ 9.2.1 ✅ Pass Set to ^9.3.0
Screenshots in manifest ✅ Pass Both dashboard screenshots included
discovery.fields ✅ OK Uses discovery.datasets (consistent with similar packages)
Service + OTel logo ✅ Pass Logo combines Redis icon with OpenTelemetry branding
README collector config ✅ Pass Includes configuration example and version info

Dashboard Screenshots Review:

  • Overview dashboard has appropriate sections for Memory & Throughput, Connections & Keyspace, Replication & Persistence, and Detail
  • Memory & Persistence dashboard includes Memory, CPU Time, Fork Duration, and RDB Changes visualizations
  • Both dashboards filter by data_stream.dataset: redisreceiver.otel

Additional Observations:

  • Package passes elastic-package lint
  • Changelog properly references this PR
  • Alert rules cover critical scenarios (rejected connections, memory fragmentation, high eviction, replicas disconnected)
  • SLO templates define appropriate 99.5% targets for command latency, fork duration, and connection availability

--- |


Why is Claude responding? | Type @claude to interact further

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

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've reviewed this PR against the specified criteria. The package is well-structured and follows the patterns of other OpenTelemetry integration packages.

Review Summary:

Criteria Status Notes
Dashboard YAML files N/A Dashboards in this repo are JSON (standard practice)
Category has opentelemetry ✅ Pass categories: [datastore, observability, opentelemetry]
Kibana version ≥ 9.2.1 ✅ Pass Set to ^9.3.0
Screenshots in manifest ✅ Pass Both dashboard screenshots included
discovery.fields ✅ OK Uses discovery.datasets which is consistent with similar packages
Service + OTel logo ✅ Pass Logo combines Redis icon with OpenTelemetry branding
README collector config ✅ Pass Includes configuration example and version info

Additional Observations:

  • Package passes elastic-package lint
  • Changelog properly references this PR
  • Dashboard screenshots look well-organized with appropriate sections for Memory, Connections, Replication, and Persistence
  • Alert rules and SLO templates are well-defined with appropriate thresholds
  • README includes Redis receiver v0.145.0 and Redis 6.x/7.x compatibility

Why is Claude responding? | Type @claude to interact further

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

@ishleenk17

Copy link
Copy Markdown
Member

@Linu-Elias : Why is the keyspace hit ration percentage above 1100%. Please check
Include yaml files

| **[Redis OTel] Primary has no connected replicas** | Primary instance has zero connected replicas | High |

## SLO templates

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note for SLO dependency on stack

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix the nits and then good to merge @Linu-Elias

@strawgate

strawgate commented Mar 16, 2026

Copy link
Copy Markdown
Contributor

To make this compatible with kb-dashboard 0.4.0 (released 3/17), run the automated upgrade and recompile:

# 1. Upgrade YAML files in-place (handles all schema renames automatically)
uvx kb-dashboard-cli upgrade --write --input-dir packages/<PACKAGE>/_dev/shared/kibana

# 2. Recompile
uvx kb-dashboard-cli compile \
  --input-dir packages/<PACKAGE>/_dev/shared/kibana \
  --output-dir packages/<PACKAGE>/kibana/dashboard \
  --format json

The upgrade command automatically handles:

  • dimensionsbreakdowns (pie, treemap, datatable)
  • dimensionbreakdown (waffle)
  • dimensions_bymetrics_split_by (datatable)
  • titles_and_textappearance fields (pie, mosaic, waffle, XY)
  • legend.sizelegend.width
  • appearance.shape camelCase → snake_case (gauge)
  • color.stopscolor.thresholds with stopup_to (gauge)
  • Static numeric minimum/maximum/goal → EVAL expressions (ESQL gauge)

Review the diff after upgrading to confirm the changes look correct, then recompile and commit.

@strawgate

Copy link
Copy Markdown
Contributor

I ran kb-dashboard 0.4.0 upgrade validation on this PR in an isolated worktree.

Results

  • packages/redis_otel/_dev/shared/kibana
    • upgrade --fail-on-change exit: 2
    • upgrade --write exit: 0
    • post-upgrade compile --format elastic-integrations exit: 0

Upgrade and post-upgrade compile succeeded with 0.4.0.
Please apply these commands in your branch and commit both YAML + regenerated JSON artifacts.

Suggested commands:

uvx --from kb-dashboard-cli==0.4.0 kb-dashboard upgrade --input-dir packages/redis_otel/_dev/shared/kibana --write
uvx --from kb-dashboard-cli==0.4.0 kb-dashboard compile --input-dir packages/redis_otel/_dev/shared/kibana --output-dir packages/redis_otel/kibana/dashboard --format elastic-integrations
@ishleenk17

Copy link
Copy Markdown
Member

/test

@elasticmachine

Copy link
Copy Markdown

💚 Build Succeeded

History

@Linu-Elias
Linu-Elias merged commit 8fc5255 into elastic:main Mar 19, 2026
9 checks passed
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Package redis_otel - 0.1.0 containing this change is available at https://epr.elastic.co/package/redis_otel/0.1.0/

@andrewkroh andrewkroh added the Integration:redis_otel Redis OpenTelemetry Assets label Mar 19, 2026
srilumpa pushed a commit to srilumpa/elastic-integrations that referenced this pull request Mar 23, 2026
* add package

* changelog

* manifest

* fix lint

* add yaml

* kb-dashboard compatibility

* kb-dashboard compatibility

* Revert "kb-dashboard compatibility"

This reverts commit 261ff7c.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dashboard Relates to a Kibana dashboard bug, enhancement, or modification. documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. Integration:redis_otel Redis OpenTelemetry Assets New Integration Issue or pull request for creating a new integration package.

7 participants