Add redis otel input package

[mrodm]

Proposed commit message

This PR adds a new Redis OpenTelemetry Input Package (redis_input_otel) that enables Elastic users to collect metrics from Redis servers using the OpenTelemetry Collector's redisreceiver through the EDOT (Elastic Distribution of OpenTelemetry) collector.

New Package: redis_input_otel

The package provides:

• Connection settings: endpoint, username, password, transport (tcp/unix)
• TLS settings: insecure mode, skip verification, CA/cert/key files, server name override
• Collection settings: collection interval, initial delay

Configuration Options

Setting	Required	Default	Description
Endpoint	Yes	localhost:6379	The Redis server endpoint (host:port)
Username	No	-	Redis ACL username (requires Redis 6.0+)
Password	No	-	Redis password
Transport	No	tcp	Network to use (tcp or unix)
Disable TLS	No	true	Set to false to enable TLS
Collection Interval	No	10s	Time between metric collections
Initial Delay	No	1s	Delay before starting collection

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

• Follows Add Redis OTel input package #17097
• Closes Create Input Package: Redis receiver #17151

Screenshots

---

Generated with Claude Code
Logo generated also with the assistance of copilot.

[github-actions]

✅ 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.

[github-actions]

The SVG logo file contains embedded JavaScript (a mesh gradient polyfill, lines 129-133), which poses a security risk and differs from other OTel input packages like nginx_input_otel that use clean SVGs. Please regenerate the SVG without embedded scripts - consider exporting from the SVG editor with mesh gradients rasterized or converted to standard gradients.

---

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

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

[github-actions]

The password field uses secret: true but Fleet Server bug #6277 prevents secrets from being processed in OTel configurations. This will cause authentication failures when users configure a password. The prometheus_input_otel package uses secret: false as a workaround until the bug is resolved.

If changing to secret: false, also update _dev/test/policy/test-default.expected to reflect that the password will appear directly (not as ${SECRET_0}) and secret_references should be empty.

---

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

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

[github-actions]

Claude finished @mrodm's task in 3m 31s —— View job

---

Adding TLS Test Policy

• Gather context on existing test policy structure
• Review manifest.yml for TLS variables
• Create new test policy with TLS settings enabled
• Commit and push changes

I've added a new test policy that sets tls_insecure to false and includes all the TLS-related variables:

New files:

• _dev/test/policy/test-tls.yml - Test configuration with TLS enabled
• _dev/test/policy/test-tls.expected - Expected policy output

TLS variables included in the test:

• tls_insecure: false
• tls_insecure_skip_verify: false
• tls_ca_file: "/path/to/ca.crt"
• tls_cert_file: "/path/to/client.crt"
• tls_key_file: "/path/to/client.key"
• tls_server_name_override: "redis.example.com"
• tls_min_version: "1.2"
• tls_max_version: "1.3"
• tls_include_system_ca_certs_pool: true

Commit: 419ba94

--- | Branch add-redis-otel-input-package

---

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

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

[github-actions]

The package structure looks reasonable and follows existing OTel input package patterns. A few items to address:

1. The sample_event.json dataset doesn't match the expected policy transform - this should be reconciled to ensure documentation accuracy.

2. Minor: The boolean handling in the Handlebars template differs from similar packages like prometheus_input_otel. When tls_insecure_skip_verify is explicitly set to false, the field is omitted rather than rendered. While this may work correctly due to receiver defaults, it's worth considering consistency with other packages.

---

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

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

[teresaromero]

👍🏻 looks good

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: d7130a6

History

• 💚 Build #37881 succeeded 8f2d459
• 💚 Build #37868 succeeded cb3ffed
• 💚 Build #37867 succeeded 605c7d3
• 💚 Build #37842 succeeded 6cdb436
• 💚 Build #37734 succeeded 8bf0641
• 💔 Build #37732 failed 419ba94

cc @mrodm

[mrodm]

Hi @elastic/obs-infraobs-integrations, as you are codeowners of the redis package:

integrations/packages/redis/manifest.yml

Line 127 in ea62e17

github: elastic/obs-infraobs-integrations

Do you have any suggestions or comments for this PR that introduces a new input OTel package for the redis receiver?

Thanks in advance!

[mrodm]

@elastic/obs-infraobs-integrations should it be added here a variable to allow specify specific attributes like in hostmetrics_input_otel for this redis input package ?
Something like ?

processors:
  resourcedetection/system:
    detectors: ["system"]
    system: {{system_config}}

Or is it not needed at all to add this processor ?

As this uses an endpoint to gather the metrics from other services, I'm not totally sure this is needed. I would like to have your opinion here.

[mrodm]

Right now it follows the same approach as the nginx input otel:

integrations/packages/nginx_input_otel/agent/input/input.yml.hbs

Lines 6 to 13 in 592c26b

	processors:
	resourcedetection/system:
	detectors: ["system"]
	service:
	pipelines:
	metrics:
	receivers: [nginx]
	processors: [resourcedetection/system]

[elastic-vault-github-plugin-prod]

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