Add new TLS field for mTLS support for server based sources

[tessneau]

What does this PR do? What is the motivation?

We've addded support for mTLS by adding a new boolean tls field tls.verify_certifcate to most server based sources: fluent (fluentbit and fluentd), http_server, logstash, opentelemetry, socket, splunk_hec, splunk_tcp, syslog (rsyslog and syslog-ng).

This new field was already released in OPW v 2.16.0.

Client based sources do not need this for establishing mTLS and certain server based sources which do not yet support TLS in general are not included either.

Merge instructions

Merge readiness:

• Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

AI assistance

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/tessneau/add-new-mtls-field-for-multiple-sources/observability_pipelines/sources/fluent
• https://docs-staging.datadoghq.com/tessneau/add-new-mtls-field-for-multiple-sources/observability_pipelines/sources/http_server
• https://docs-staging.datadoghq.com/tessneau/add-new-mtls-field-for-multiple-sources/observability_pipelines/sources/logstash
• https://docs-staging.datadoghq.com/tessneau/add-new-mtls-field-for-multiple-sources/observability_pipelines/sources/opentelemetry
• https://docs-staging.datadoghq.com/tessneau/add-new-mtls-field-for-multiple-sources/observability_pipelines/sources/socket
• https://docs-staging.datadoghq.com/tessneau/add-new-mtls-field-for-multiple-sources/observability_pipelines/sources/splunk_hec
• https://docs-staging.datadoghq.com/tessneau/add-new-mtls-field-for-multiple-sources/observability_pipelines/sources/splunk_tcp
• https://docs-staging.datadoghq.com/tessneau/add-new-mtls-field-for-multiple-sources/observability_pipelines/sources/syslog

[maycmlee]

Just a couple of small suggestions!

[maycmlee]

Suggested change

	Optionally, after you enable TLS, toggle **Verify certificate** to require connecting clients to present a valid client certificate. This enforces mutual TLS (mTLS), where the Worker verifies the identity of each connecting client.
	-(Optional) Toggle **Verify certificate** to require connecting clients to present a valid client certificate. This enforces mutual TLS (mTLS), where the Worker verifies the identity of each connecting client.