Add Apache HTTP Server status OpenTelemetry input package by perk · Pull Request #16970 · elastic/integrations

perk · 2026-01-15T12:46:26Z

This package implements an Apache input using the OpenTelemetry Collector's Apache Receiver, following the pattern established in PR #15739

Key features:

Type: integration with otelcol input (not content package)
Configurable collection interval, endpoint
Comprehensive field definitions for container metrics
Full documentation and system and test policies added

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

Content package is installed when there are documents ingested into apachereceiver.otel dataset.

How to test this PR locally

Related issues

Closes Create Input Package: Apache receiver #17130

Screenshots

Using the server name from the system test svc-apache_input_otel:

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

strawgate · 2026-01-29T06:02:04Z

@claude please do a thorough review -- pay careful attention to the receiver upstream and at our other input packages

github-actions · 2026-01-29T06:04:26Z

Claude finished @strawgate's task in 5m 6s —— View job

Review Complete

I've submitted a review with request for changes.

Critical Issue Found:

🔴 TLS Configuration Logic Bug - The TLS block in input.yml.hbs is wrapped in {{#if tls_insecure}}, but insecure: true means TLS is disabled. This inverted logic prevents users from configuring TLS certificates or skip-verification when TLS is actually enabled.

Medium Priority:

🟡 Duration fields (collection_interval, initial_delay) should use type: duration instead of type: text to match the pattern in nginx_input_otel

What looks good:

Endpoint default matches upstream exactly
Docker test setup properly configures mod_status
Documentation is comprehensive
Correct CODEOWNERS assignment

See the review for detailed suggestions on fixing the TLS logic.

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

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

github-actions

TLS Configuration Logic Bug (High Priority)

The TLS configuration in agent/input/input.yml.hbs has inverted logic. Currently, the entire TLS block is wrapped in {{#if tls_insecure}}, meaning TLS settings (including ca_file, cert_file, key_file, insecure_skip_verify, server_name_override) are only rendered when tls_insecure=true.

However, insecure: true in OTel configuration means TLS is disabled (plain HTTP). So when users want to use TLS with custom certificates or skip verification, they would set tls_insecure=false, but then none of the TLS settings would be rendered.

Expected behavior: The TLS block should be rendered when TLS settings are provided, not when tls_insecure is true. The insecure field controls whether to use TLS at all, while other TLS fields configure how TLS works when enabled.

Suggested fix for input.yml.hbs lines 31-49:

{{#if tls_ca_file}}
    tls:
      ca_file: {{tls_ca_file}}
{{#if tls_cert_file}}
      cert_file: {{tls_cert_file}}
{{/if}}
{{#if tls_key_file}}
      key_file: {{tls_key_file}}
{{/if}}
{{#if tls_insecure_skip_verify}}
      insecure_skip_verify: {{tls_insecure_skip_verify}}
{{/if}}
{{#if tls_server_name_override}}
      server_name_override: {{tls_server_name_override}}
{{/if}}
{{else if tls_insecure_skip_verify}}
    tls:
      insecure_skip_verify: {{tls_insecure_skip_verify}}
{{/if}}

Additionally, the tls_insecure variable as a way to "disable TLS" is confusing - consider removing it since the upstream receiver doesn't have this field directly; TLS is controlled by protocol in the endpoint URL (http:// vs https://).

Medium Priority Issues

1. Duration fields should use `type: duration` not `type: text`

The reference package nginx_input_otel correctly uses type: duration for collection_interval and initial_delay. This PR uses type: text which doesn't provide the same validation benefits.

Files affected: manifest.yml lines 47, 54

2. Missing TLS settings from test policy

The test-default.yml includes tls_insecure: false and tls_insecure_skip_verify: false but the expected output in test-default.expected doesn't show any TLS configuration, which is correct given the current (broken) logic, but should be updated once TLS logic is fixed.

Low Priority / Nitpicks

1. Consider consistency with nginx_input_otel naming

The nginx package uses nginx_otel_input as the directory name, while this uses apache_otel_input. While both are valid, consistency across packages improves discoverability.

2. Documentation mentions "container metrics"

In the PR description: "Comprehensive field definitions for container metrics" - but this package doesn't include field definitions (no fields/ directory) and Apache server-status metrics are not container metrics. Consider updating the PR description.

3. Package type consistency

The nginx_input_otel package has the internal name nginx_otel_input (manifest line 2), matching the PR's naming. Good consistency here.

What Looks Good

The endpoint default http://localhost:8080/server-status?auto matches the upstream default exactly
Docker test setup correctly enables mod_status with ExtendedStatus On
CODEOWNERS entry correctly assigns to @elastic/obs-infraobs-integrations
Documentation is comprehensive with configuration tables
Reference to upstream metrics documentation is appropriate
The httpd.conf test configuration is complete with proper server-status endpoint setup

The TLS logic bug is the critical issue that should be addressed before merge, as it would prevent users from configuring TLS properly.

ishleenk17 · 2026-02-03T11:33:57Z

+- The `mod_status` module must be enabled and accessible
+
+
+## Configuration Options


For configuration options, we're currently pointing to the upstream config page to maintain a single source of truth. Otherwise, we'd need to ensure consistency across both documentation sources. Assuming the config parameters are the same in the input packages and upstream receivers, I'd recommend referencing the upstream config directly.

Documentation has been updated as in other input packages with a reference to the upstream documentation.

ishleenk17 · 2026-02-03T11:35:10Z

+{{/if}}
+processors:
+  resourcedetection/system:
+    detectors: ["system"]


Do we need to provide a yaml box after this to get in the other non default resource attributes enabled if required.
Or do we need this process or at all here ?

Any suggestion here @ishleenk17 , should then this processor be removed ? Or should we add a new variable to be able to customize the attributes like it was done in hostmetrics_input_otel package ?

Right now, this PR follows the same approach as the nginx_input_otel package, adding just the resource detection system

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]

Should we leave it as it is defined in the nginx_input_otel for now?

mrodm · 2026-02-10T17:19:41Z

Converting to draft this PR for now to apply some changes.

github-actions

The package structure looks good and follows the established pattern from nginx_input_otel.

Existing unresolved review threads address the key issues:

Logo needs OTel branding to match other input packages
Resource attribute configuration question at line 70 of input.yml.hbs
Documentation configuration discussion

The TLS configuration template handles various combinations correctly, and the package passes elastic-package validation.

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

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

github-actions

Two existing unresolved threads need to be addressed:

_dev/build/docs/README.md:17 - Configuration options documentation approach
agent/input/input.yml.hbs:70 - Resource attributes handling

Additionally:

Minor: The PR description references "Comprehensive field definitions for container metrics" which appears to be copy-pasted from a different package. This is an Apache HTTP Server status package, not a container metrics 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 follows the established OTel input package pattern. A few items to consider:

Missing TLS policy test (medium): There's no policy test to validate the TLS configuration template renders correctly. Similar packages (prometheus_input_otel) include a test-tls.yml test case.
Unresolved question: There's an existing thread about whether the resourcedetection processor should be configurable via a YAML variable (similar to system_config in hostmetrics_input_otel). This decision affects users who need non-default resource attributes.

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

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

github-actions

The test-tls-config.expected file has incorrect values that don't match the test-tls-config.yml input:

Endpoint mismatch: Input specifies https://localhost:8080/server-status?auto but expected shows http://localhost:8080/server-status?auto
TLS insecure mismatch: Input specifies tls_insecure: false but expected shows insecure: true

These discrepancies suggest the expected file was not regenerated after updating the test input, or there's a bug in the template rendering. Please regenerate the expected file using elastic-package test policy to ensure it matches the actual output.

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

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

mrodm · 2026-02-12T11:15:07Z

@claude related to this #16970 , is the comment related to the documentation still applicable with the latest changes?

github-actions · 2026-02-12T11:16:57Z

Claude finished @mrodm's task in 42s —— View job

Checking Documentation Review Comment

Gather repository context
Review the referenced review comment (PR review #3786160629)
Check the current state of documentation files
Determine if the comment is still applicable

Answer

No, the documentation comment is no longer applicable - it has been addressed.

The referenced review comment from ishleenk17 suggested:

"For configuration options, we're currently pointing to the upstream config page to maintain a single source of truth. Otherwise, we'd need to ensure consistency across both documentation sources. Assuming the config parameters are the same in the input packages and upstream receivers, I'd recommend referencing the upstream config directly."

Looking at the current state of packages/apache_input_otel/_dev/build/docs/README.md (lines 17-19), the documentation now follows this recommendation:

## Configuration

For the full list of settings exposed for the receiver and examples, refer to the [configuration](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/apachereceiver#configuration) section.

This approach:

✅ Points directly to the upstream configuration documentation
✅ Maintains a single source of truth
✅ Follows the same pattern as the nginx_input_otel package (which doesn't have a separate Configuration section at all)

The documentation is appropriately referencing the upstream Apache Receiver configuration page rather than duplicating configuration details locally.

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

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

…er-status-input-package

elasticmachine · 2026-02-13T20:26:55Z

💚 Build Succeeded

Buildkite Build
Commit: 1d773c5

History

💚 Build #38108 succeeded 347467d
💚 Build #38082 succeeded 255e571
💚 Build #38026 succeeded 71551a8
💚 Build #38021 succeeded f35ec62
💚 Build #37995 succeeded 65e4d20
💚 Build #37988 succeeded 789e01d

cc @mrodm

teresaromero

👍🏻 lgtm

teresaromero · 2026-02-16T12:51:51Z

+            - context: datapoint
+              statements:
+                - set(attributes["data_stream.type"], "metrics")
+                - set(attributes["data_stream.dataset"], "apache_input_otel.apachereceiver")


this will be updated after elastic/elastic-package#3285

elastic-vault-github-plugin-prod · 2026-02-16T17:36:15Z

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

) This PR adds a new OTel input package that uses the OpenTelemetry Collector's Apache Receiver through the EDOT (Elastic Distribution of OpenTelemetry). --------- Co-authored-by: Marcin "Perk" Stożek <perk@elastic.co> Co-authored-by: Bill Easton <bill.easton@elastic.co> Co-authored-by: Mario Rodriguez Molins <mario.rodriguez@elastic.co>

perk changed the title ~~[wip] Add Apache HTTP Server status OpenTelemetry input package~~ Jan 28, 2026

perk marked this pull request as ready for review January 28, 2026 14:08

perk requested a review from a team as a code owner January 28, 2026 14:08

andrewkroh added New Integration Issue or pull request for creating a new integration package. documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. labels Jan 28, 2026

elastic deleted a comment from github-actions Bot Jan 29, 2026

github-actions Bot requested changes Jan 29, 2026

View reviewed changes

perk and others added 4 commits January 29, 2026 09:59

feat: add Apache HTTP Server status OTel input package

d5a5b13

fix: TLS configuration options were not rendered properly

5f797d4

fix: change the time variables from text to duration type

fdc8052

Merge branch 'main' into add-apache-web-server-status-input-package

56c8e3b

strawgate mentioned this pull request Jan 29, 2026

Debug: Test workflow condition without author_association check #17122

Closed

kpollich linked an issue Jan 29, 2026 that may be closed by this pull request

Create Input Package: Apache receiver #17130

Closed

12 tasks

teresaromero reviewed Feb 3, 2026

View reviewed changes

Comment thread .github/CODEOWNERS Outdated

teresaromero reviewed Feb 3, 2026

View reviewed changes

Comment thread packages/apache_otel_input/manifest.yml Outdated

teresaromero reviewed Feb 3, 2026

View reviewed changes

Comment thread packages/apache_input_otel/img/logo_apache.svg Outdated

mrodm reviewed Feb 3, 2026

View reviewed changes

Comment thread packages/apache_otel_input/manifest.yml Outdated

Comment thread .github/CODEOWNERS Outdated

ishleenk17 reviewed Feb 3, 2026

View reviewed changes

mrodm self-assigned this Feb 10, 2026

refactor: rename package name to be apache_input_otel

a20f2b2

mrodm marked this pull request as draft February 10, 2026 17:19

github-actions Bot reviewed Feb 11, 2026

View reviewed changes

Comment thread packages/apache_input_otel/LICENSE.txt Outdated

Update license.txt from licenses/Elastic-2.0.txt

789e01d

github-actions Bot approved these changes Feb 11, 2026

View reviewed changes

Update package logo to include OTel logo too

65e4d20

github-actions Bot approved these changes Feb 11, 2026

View reviewed changes

Add a minimum of documents to be ingested in system tests

f35ec62

github-actions Bot reviewed Feb 11, 2026

View reviewed changes

Comment thread packages/apache_input_otel/_dev/test/system/test-default-config.yml Outdated

mrodm added 3 commits February 11, 2026 18:13

Update variables defined in manifest

52d5936

Update docs

98acfbd

Set tls_enabled as false in default policy test

71551a8

github-actions Bot reviewed Feb 11, 2026

View reviewed changes

Comment thread packages/apache_input_otel/_dev/test/policy/test-default.yml

github-actions Bot mentioned this pull request Feb 11, 2026

Add a doc/guide for creating OTel Input Packages #17381

Closed

github-actions Bot requested changes Feb 12, 2026

View reviewed changes

Comment thread packages/apache_input_otel/_dev/test/policy/test-tls-config.expected Outdated

Comment thread packages/apache_input_otel/_dev/test/policy/test-tls-config.expected Outdated

Comment thread packages/apache_input_otel/_dev/test/policy/test-tls-config.yml

Add test policy for tls parameters

255e571

github-actions Bot approved these changes Feb 12, 2026

View reviewed changes

mrodm added the claude-plz-triage label Feb 12, 2026

github-actions Bot approved these changes Feb 12, 2026

View reviewed changes

Merge remote-tracking branch 'upstream/main' into add-apache-web-serv…

347467d

…er-status-input-package

github-actions Bot approved these changes Feb 12, 2026

View reviewed changes

mrodm requested review from ishleenk17 and teresaromero February 12, 2026 17:20

mrodm marked this pull request as ready for review February 12, 2026 17:21

Merge branch 'main' into add-apache-web-server-status-input-package

1d773c5

github-actions Bot approved these changes Feb 13, 2026

View reviewed changes

teresaromero approved these changes Feb 16, 2026

View reviewed changes

mrodm merged commit a37dd8f into elastic:main Feb 16, 2026
12 checks passed

andrewkroh added the Integration:apache_input_otel Apache HTTP Server (OpenTelemetry) label Feb 17, 2026

github-actions Bot approved these changes Feb 17, 2026

View reviewed changes

perk deleted the add-apache-web-server-status-input-package branch March 6, 2026 07:39

Navigation Menu

Uh oh!

Add Apache HTTP Server status OpenTelemetry input package - #16970

Add Apache HTTP Server status OpenTelemetry input package#16970
mrodm merged 15 commits into
elastic:mainfrom
perk:add-apache-web-server-status-input-package

perk commented Jan 15, 2026 •

edited

Loading

strawgate commented Jan 29, 2026

github-actions Bot commented Jan 29, 2026 •

edited

Loading

github-actions Bot left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

ishleenk17 Feb 3, 2026

mrodm Feb 12, 2026

ishleenk17 Feb 3, 2026

mrodm Feb 12, 2026

mrodm Feb 12, 2026 •

edited

Loading

mrodm commented Feb 10, 2026

github-actions Bot left a comment

Uh oh!

github-actions Bot left a comment

Uh oh!

github-actions Bot left a comment

Uh oh!

github-actions Bot left a comment

Uh oh!

Uh oh!

Uh oh!

mrodm commented Feb 12, 2026 •

edited

Loading

github-actions Bot commented Feb 12, 2026 •

edited

Loading

elasticmachine commented Feb 13, 2026

teresaromero left a comment

teresaromero Feb 16, 2026

Uh oh!

elastic-vault-github-plugin-prod Bot commented Feb 16, 2026

Labels

7 participants

		- The `mod_status` module must be enabled and accessible


		## Configuration Options

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

Uh oh!

Conversation

perk commented Jan 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Checklist

Author's Checklist

How to test this PR locally

Related issues

Screenshots

strawgate commented Jan 29, 2026

github-actions Bot commented Jan 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review Complete

github-actions Bot left a comment

Choose a reason for hiding this comment

TLS Configuration Logic Bug (High Priority)

Medium Priority Issues

1. Duration fields should use type: duration not type: text

2. Missing TLS settings from test policy

Low Priority / Nitpicks

1. Consider consistency with nginx_input_otel naming

2. Documentation mentions "container metrics"

3. Package type consistency

What Looks Good

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

ishleenk17 Feb 3, 2026

Choose a reason for hiding this comment

mrodm Feb 12, 2026

Choose a reason for hiding this comment

ishleenk17 Feb 3, 2026

Choose a reason for hiding this comment

mrodm Feb 12, 2026

Choose a reason for hiding this comment

mrodm Feb 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

mrodm commented Feb 10, 2026

github-actions Bot left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

mrodm commented Feb 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

github-actions Bot commented Feb 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Checking Documentation Review Comment

Answer

elasticmachine commented Feb 13, 2026

💚 Build Succeeded

History

teresaromero left a comment

Choose a reason for hiding this comment

teresaromero Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

elastic-vault-github-plugin-prod Bot commented Feb 16, 2026

Labels

7 participants

perk commented Jan 15, 2026 •

edited

Loading

github-actions Bot commented Jan 29, 2026 •

edited

Loading

1. Duration fields should use `type: duration` not `type: text`

mrodm Feb 12, 2026 •

edited

Loading

mrodm commented Feb 12, 2026 •

edited

Loading

github-actions Bot commented Feb 12, 2026 •

edited

Loading