[Demo] Add info about React Native app

[jpmunz]

This updates the demo documentation to include the React Native example app that was added here: open-telemetry/opentelemetry-demo#1781

Preview: https://deploy-preview-5704--opentelemetry.netlify.app/docs/demo/services/react-native-app/

[svrnm]

thanks, looks good overall, a few comments

[chalin]

As a general comment, I don't think that the app should be documented as a part of the demo/services. Even the entry in the index page reads, "React Native mobile application that provides a UI on top of the shopping services."

How does it relate to the Collector?

Maybe we need a new Demo top-level entry?

[julianocosta89]

As a general comment, I don't think that the app should be documented as a part of the demo/services. Even the entry in the index page reads, "React Native mobile application that provides a UI on top of the shopping services."

Maybe we need a new Demo top-level entry?

I actually disagree @chalin.
The app is just another way to interact with the demo.
The user can navigate to the frontend and buy astronomy stuff, or they can open the app and do the same.
The app should be on the same level as frontend-proxy, which is the service that exposes the frontend.

How does it relate to the Collector?

As well as the other services, the reactive-native-app is instrumented with OTel and sends traces to the Collector.

[puckpuck]

I agree with @julianocosta89 here. The react-native-app could be seen similar to the frontend service. It the mobile app does route all its telemetry data through the frontend-proxy into a collector, and does similar API calls as the web tier does.

[jpmunz]

Marking this as Ready to Review now that the associated PR in the demo repo got merged: open-telemetry/opentelemetry-demo#1781 (comment)

Will updated and take a look at the check failures

[jpmunz]

I'm not quite sure how to address the failure on the "Build and Check Links" check, it appears to fail on running npm run _diff:fail which exits successfully for me locally

[tiffany76]

/fix:htmltest-config

[opentelemetrybot]

You triggered fix:htmltest-config action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/12422284976

[opentelemetrybot]

fix:htmltest-config was successful.

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

[tiffany76]

/fix:all

[opentelemetrybot]

You triggered fix:all action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/12422305906

[opentelemetrybot]

fix:all failed or was cancelled. For details, see https://github.com/open-telemetry/opentelemetry.io/actions/runs/12422305906.

[tiffany76]

I'm not quite sure how to address the failure on the "Build and Check Links" check, it appears to fail on running npm run _diff:fail which exits successfully for me locally

I think the issue is fixed, but the CI checks need to be triggered again. Maybe try a rebase?

[svrnm]

@jpmunz @tiffany76 let's ignore the build issues for now, we can fix them once the PR is approved by @open-telemetry/demo-approvers and @open-telemetry/docs-approvers and before we merge it

[julianocosta89]

LGTM 📱📱📱

[tiffany76]

LGTM with a few small copy edits.

[jpmunz]

LGTM with a few small copy edits.

hey @tiffany76 thanks for the review! I was away the last 2 weeks and just applied your suggestions now

I think everything looks good now though still seeing that failure on the build and check links check: https://github.com/open-telemetry/opentelemetry.io/actions/runs/12638371441/job/35214486467?pr=5704

[tiffany76]

/fix:htmltest-config

[tiffany76]

Hi @jpmunz, the PR action is failing for me, even on re-run, and I'm not sure why. We might need @chalin or @svrnm's expertise to fix this. Here's the error message I'm seeing:

Run gh pr comment $PR_NUM -b "fix:${PR_ACTION} failed or was cancelled. For details, see $GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID."
failed to run git: fatal: not a git repository (or any of the parent directories): .git

[svrnm]

@jpmunz as a general note, please avoid raising PRs from a fork within an ORG, as they are not editable by maintainers, so we can not use automation or any other ways of helping you to fix this.

On the issue, the entry in refcache is missing so please run npm run fix:all locally and push the changes.

Thanks

[chalin]

Thanks all for your feedback. LGTM if it LGTY, and once all checks are passing.

@jpmunz - please rebase this PR before running the fix commands locally.

[jpmunz]

@jpmunz as a general note, please avoid raising PRs from a fork within an ORG, as they are not editable by maintainers, so we can not use automation or any other ways of helping you to fix this.

On the issue, the entry in refcache is missing so please run npm run fix:all locally and push the changes.

Thanks

@svrnm ah ok I'll keep that in mind about the fork for next time

everything looks green after running npm run fix:all thanks!