Merge pull request #1779 from splunk/theletterf-o11ydocs-5991-php-otel-docs

Add OTel PHP docs

Author: theletterf

_includes/gdi/zero-conf-reqs.rst

@@ -6,5 +6,5 @@
 
    - To get an access token, see :ref:`admin-api-access-tokens`.
 
-   - To find the realm name of your account, open the navigation menu in Splunk Observability Cloud. Select :menuselection:`Settings`, and then select your username. The realm name appears in the :guilabel:`Organizations` section.
+   - To find the realm name of your account, see :ref:`Note about realms <about-realms>`.
 

_includes/realm-note.rst

@@ -1,6 +1,5 @@
 .. note:: Note about realms
 
-   A realm is a self-contained deployment of Splunk Observability Cloud in which your organization is hosted. Different realms have different API endpoints. For example, the endpoint for sending data in the ``us1`` realm is ``https://ingest.us1.signalfx.com``, while the endpoint for sending data in the ``eu0`` realm is
-   ``https://ingest.eu0.signalfx.com``.
+   A realm is a self-contained deployment of Splunk Observability Cloud in which your organization is hosted. Different realms have different API endpoints. For example, the endpoint for sending data in the ``us1`` realm is ``https://ingest.us1.signalfx.com``, while the endpoint for sending data in the ``eu0`` realm is ``https://ingest.eu0.signalfx.com``.
 
-   When you see a placeholder realm name in the documentation, such as ``<YOUR_REALM>``, replace it with your actual realm name. To find your realm name, open the left navigation menu in Observability Cloud, select :menuselection:`Settings`, and select your username. The realm name appears in the :guilabel:`Organizations` section. If you don't include the realm name when specifying an endpoint, Observability Cloud defaults to the ``us0`` realm.
+   When you see a placeholder realm name in the documentation, such as ``<YOUR_REALM>``, replace it with your actual realm name. To find your realm name, open the navigation menu in Splunk Observability Cloud, select :menuselection:`Settings`, and select your username. The realm name appears in the :guilabel:`Organizations` section. If you don't include the realm name when specifying an endpoint, Splunk Observability Cloud defaults to the ``us0`` realm.

_includes/requirements/php.rst

@@ -1,9 +1,3 @@
-The SignalFx Tracing Library for PHP supports PHP version 7.0 or higher running on the Zend engine.
+The OpenTelemetry instrumentation for PHP supports PHP version 8.0 or higher.
 
-Supported web servers are:
-
-- Apache
-- php-fpm
-- php-cli
-
-.. note:: The library is not compatible with Windows environments.
+.. note:: The library is not supported for Windows environments.

admin/authentication/SSO/sso.rst

@@ -12,9 +12,9 @@ Configure SSO integrations for Splunk Observability Cloud
 Splunk Observability Cloud provides SSO login service integrations that let your users log in using a third-party
 identity provider (IdP) that uses SAML SSO. Observability Cloud supports SSO initiated by the IdP.
 
-Observability Cloud also supports SSO initiated by Observability Cloud, and this option lets your users log in to Infrastructure Monitoring using a custom URL you specify.
+Splunk Observability Cloud also supports SSO initiated by Observability Cloud, and this option lets your users log in to Infrastructure Monitoring using a custom URL you specify.
 
-Observability Cloud supports the following SSO integrations:
+Splunk Observability Cloud supports the following SSO integrations:
 
 -  :ref:`Splunk Cloud Platform<unified-id-unified-identity>`
 -  :ref:`Microsoft Active Directory Federation Services (ADFS)<sso-adfs>`

apm/set-up-apm/apm-gdi.rst

@@ -119,7 +119,7 @@ In the following table, follow the instrumentation steps for the language that e
      - :ref:`get-started-ruby`
 
    * - PHP
-     - SignalFx Tracing Library for PHP
+     - OpenTelemetry instrumentation for PHP
      - :ref:`get-started-php`
 
 After you instrument your applications, you're ready to verify that your data is coming in.

gdi/get-data-in/application/go/instrumentation/instrument-go-application.rst

@@ -174,13 +174,7 @@ If you need to send data directly to Splunk Observability Cloud, set the followi
 
 To obtain an access token, see :ref:`admin-api-access-tokens`.
 
-In the ingest endpoint URL, ``realm`` is the Splunk Observability Cloud realm, for example, ``us0``. To find the realm name of your account, follow these steps: 
-
-#. Open the navigation menu in Splunk Observability Cloud.
-#. Select :menuselection:`Settings`.
-#. Select your username. 
-
-The realm name appears in the :guilabel:`Organizations` section. 
+To find your Splunk realm, see :ref:`Note about realms <about-realms>`. 
 
 For more information on the ingest API endpoints, see :new-page:`Send APM traces <https://dev.splunk.com/observability/docs/apm/send_traces/>` and :new-page:`Send data points <https://dev.splunk.com/observability/docs/datamodel/ingest#Send-data-points>`.
 

gdi/get-data-in/application/java/instrumentation/instrument-java-application.rst

@@ -262,13 +262,7 @@ If you need to send data directly to Splunk Observability Cloud, set the followi
 
 To obtain an access token, see :ref:`admin-api-access-tokens`.
 
-In the ingest endpoint URL, ``realm`` is the Splunk Observability Cloud realm, for example, ``us0``. To find the realm name of your account, follow these steps:
-
-#. Open the navigation menu in Splunk Observability Cloud.
-#. Select :menuselection:`Settings`.
-#. Select your username.
-
-The realm name appears in the :guilabel:`Organizations` section.
+To find your Splunk realm, see :ref:`Note about realms <about-realms>`.
 
 For more information on the ingest API endpoints, see :new-page:`Send APM traces <https://dev.splunk.com/observability/docs/apm/send_traces/>`.
 

gdi/get-data-in/application/nodejs/instrumentation/instrument-nodejs-application.rst

@@ -280,13 +280,7 @@ If you need to send data directly to Splunk Observability Cloud, set the followi
 
 To obtain an access token, see :ref:`admin-api-access-tokens`.
 
-In the ingest endpoint URL, ``realm`` is the Splunk Observability Cloud realm, for example, ``us0``. To find the realm name of your account, follow these steps:
-
-#. Open the navigation menu in Splunk Observability Cloud.
-#. Select :menuselection:`Settings`.
-#. Select your username.
-
-The realm name appears in the :guilabel:`Organizations` section.
+To find your Splunk realm, see :ref:`Note about realms <about-realms>`.
 
 For more information on the ingest API endpoints, see :new-page:`Send APM traces <https://dev.splunk.com/observability/docs/apm/send_traces/>`.
 

gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst

@@ -343,13 +343,7 @@ To bypass the OTel Collector and send data directly to Splunk Observability Clou
 
 To obtain an access token, see :ref:`admin-api-access-tokens`.
 
-In the ingest endpoint URL, ``realm`` is the Splunk Observability Cloud realm, for example, ``us0``. To find the realm name of your account, follow these steps:
-
-#. Open the navigation menu in Splunk Observability Cloud.
-#. Select :menuselection:`Settings`.
-#. Select your username.
-
-The realm name appears in the :guilabel:`Organizations` section.
+To find your Splunk realm, see :ref:`Note about realms <about-realms>`.
 
 Specify the source host 
 ----------------------------------------------

gdi/get-data-in/application/otel-dotnet/instrumentation/manual-dotnet-instrumentation.rst

@@ -43,6 +43,8 @@ To create custom spans and traces, follow these steps:
 
 4. Register your ``ActivitySource`` by setting the ``OTEL_DOTNET_AUTO_TRACES_ADDITIONAL_SOURCES`` environmental variable. You can set the value to either ``Examples.ManualInstrumentations.Registered`` or to ``Examples.ManualInstrumentations.*``, which registers the entire prefix.
 
+See the :new-page:`OpenTelemetry official documentation <https://opentelemetry.io/docs/languages/net/instrumentation/#traces>` for additional information and examples.
+
 .. _custom-metrics-otel-dotnet:
 
 Create custom metrics
@@ -79,3 +81,5 @@ To create custom metrics, follow these steps:
    .. code:: bash
 
       OTEL_DOTNET_AUTO_METRICS_ADDITIONAL_SOURCES=My.Application
+
+See the :new-page:`OpenTelemetry official documentation <https://opentelemetry.io/docs/languages/net/instrumentation/#metrics` for additional information and examples.