Fix graphql description, apollo interceptor not released yet

[barboraplasovska]

What does this PR do? What is the motivation?

Fixes description and instructions as to how GraphQL Apollo should be setup on iOS.

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.

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/bplasovska/fix-graphql-ios-description/real_user_monitoring/application_monitoring/ios/advanced_configuration
• https://docs-staging.datadoghq.com/bplasovska/fix-graphql-ios-description/real_user_monitoring/application_monitoring/ios/integrated_libraries

[rtrieu]

Hi @barboraplasovska thank you for this PR! As a general rule, we don't suggest how any products/features/offerings may work in the future, only as it works now. I'll go ahead and put a WIP label on this, which you can remove when this update has been released, and the docs team will review it. Let me know if you have any questions. Thanks!

[barboraplasovska]

Hey @rtrieu, thanks for the review! For a bit of context, I have originally added this part of the documentation because I expected the feature to be released soon. Unfortunately, it’s still a WIP, and since the docs already mention it without saying it’s unreleased, I’ve had a customer try to use it assuming it was available.

Given the docs team’s protocol about not describing unreleased features, would it be better to temporarily remove this section entirely, or keep it and add a note clarifying that it’s not released yet?

I’m happy to adjust the PR to follow whichever option aligns best with your guidelines.

Thanks again!

[rtrieu]

Hi @barboraplasovska let's definitely remove the section until it's available :) Thanks!

[janine-c]

Thanks for working with Rosa on this one, @barboraplasovska! The removal looks great, and we'll be happy to help you get it back in the docs when it's ready 🙂