Skip to content

blog: add post on Elastic PHP distro donation (#9434)#9435

Draft
intuibase wants to merge 3 commits intoopen-telemetry:mainfrom
intuibase:blog/elastic-php-distro-donation
Draft

blog: add post on Elastic PHP distro donation (#9434)#9435
intuibase wants to merge 3 commits intoopen-telemetry:mainfrom
intuibase:blog/elastic-php-distro-donation

Conversation

@intuibase
Copy link
Copy Markdown

  • I have read and followed the Contributing docs, especially the "First-time contributing?" section.
  • This PR has content that I did not fully write myself.
  • I used AI and I have read and followed the Generative AI Contribution Policy.
  • I have the experience and knowledge necessary to understand, review, and validate all content in this PR.1

Summary

Adds a new draft blog post about the OpenTelemetry PHP distro donation and its
community impact.

  • New file: content/en/blog/2026/otel-php-distro-donation-update.md
  • Community-focused, non-commercial tone
  • Includes rollout checklist and contribution paths

Related issue

Validation

  • npm run fix:format
  • npm run check:spelling
  • npm run check:markdown

Notes for reviewers

  • Post remains draft (draft: true) pending review/sponsorship
  • SIG in frontmatter: OpenTelemetry PHP

Footnotes

  1. Yes, I can answer maintainer questions about the content of this PR, without using AI.

@otelbot-docs otelbot-docs bot requested a review from a team March 17, 2026 14:21
@github-actions github-actions bot added the blog label Mar 17, 2026
@otelbot-docs otelbot-docs bot added the missing:docs-approval Co-owning SIG has provided approval, PR needs approval from docs maintainer label Mar 17, 2026
@intuibase
Copy link
Copy Markdown
Author

/fix:dict

@otelbot-docs
Copy link
Copy Markdown
Contributor

otelbot-docs bot commented Mar 17, 2026

fix:dict applied successfully in run 23199067568.

@intuibase
Copy link
Copy Markdown
Author

/fix:refcache

@otelbot-docs
Copy link
Copy Markdown
Contributor

otelbot-docs bot commented Mar 17, 2026

fix:refcache applied successfully in run 23211483753.

Copy link
Copy Markdown
Member

@theletterf theletterf left a comment

Choose a reason for hiding this comment

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

Couple nits!


## Why this donation matters

OpenTelemetry gives us a common observability standard, but PHP adoption can
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.

Adoption of OTel in PHP envs, or of PHP itself? It's unclear


## Relationship to existing PHP instrumentation

The distro is intended to coexist with existing OpenTelemetry PHP approaches,
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.

coexist

How?

@otelbot-docs otelbot-docs bot added ready-to-be-merged This PR is ready to be merged by a maintainer and removed missing:docs-approval Co-owning SIG has provided approval, PR needs approval from docs maintainer labels Mar 24, 2026
Copy link
Copy Markdown

@alexandra5000 alexandra5000 left a comment

Choose a reason for hiding this comment

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

Nice! It's clear and well-structured. I left some comments for your consideration, nothing major so feel free to ignore/apply as you like.


## Why this donation matters

OpenTelemetry gives us a common observability standard, but PHP adoption can
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
OpenTelemetry gives us a common observability standard, but PHP adoption can
OpenTelemetry provides a common observability standard

I would suggest avoiding "us" - unclear who it's referring to. Implied yes, and I know what you mean here, but it's not 100% clear 🙂

I also agree with Fabri that "environments with strict operational constraints" sounds a bit vague.

Comment on lines +33 to +34
The project combines native and PHP runtime components into a single deployment
path for production environments. Current capabilities include:
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Maybe “into a single deployment model” or “into a unified deployment approach”?

Comment on lines +43 to +44
For teams running PHP `8.1` through `8.4`, this can reduce adoption friction
compared with custom build pipelines.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
For teams running PHP `8.1` through `8.4`, this can reduce adoption friction
compared with custom build pipelines.
For teams running PHP `8.1` through `8.4`, this can reduce adoption overhead compared with custom build pipelines.

This is probably fine (considering the target audience), but "adoption friction" sounds a bit jargon-y to me and we could replace it with something more neutral (could also be something like "can simplify adoption").


- Distro path: package-managed, operations-first rollout with minimal code
changes.
- Composer-centric path: manual control and portability where application-level
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I think "composer-based" is a more common phrasing.


## Practical rollout checklist

Before broad production rollout, validate:
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
Before broad production rollout, validate:
Before broad production rollout, validate the following:

Comment on lines +81 to +82
- Ongoing alignment between upstream OpenTelemetry distro work and vendor
distributions built on top.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
- Ongoing alignment between upstream OpenTelemetry distro work and vendor
distributions built on top.
- Ongoing alignment between upstream OpenTelemetry distro work and vendor distributions built on top of it.

Comment on lines +89 to +90
- Report installation and runtime issues in
[`opentelemetry-php-distro`](https://github.com/open-telemetry/opentelemetry-php-distro).
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
- Report installation and runtime issues in
[`opentelemetry-php-distro`](https://github.com/open-telemetry/opentelemetry-php-distro).
- Report installation and runtime issues in
[`opentelemetry-php-distro` repository](https://github.com/open-telemetry/opentelemetry-php-distro).

@svrnm
Copy link
Copy Markdown
Member

svrnm commented Mar 26, 2026

@intuibase the PR is still in draft state, can you make it "ready for review" so we can publish it eventually?

@vitorvasc vitorvasc removed the ready-to-be-merged This PR is ready to be merged by a maintainer label Mar 27, 2026
@otelbot-docs otelbot-docs bot added the ready-to-be-merged This PR is ready to be merged by a maintainer label Mar 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

blog ready-to-be-merged This PR is ready to be merged by a maintainer

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

blog: OpenTelemetry Accepted Elastic's PHP Distro Donation

6 participants