Merge pull request #2441 from splunk/bhillmer-O11YDOCS-5095-remove-identities

[O11YDOCS-5095] remove identities

Author: sheilattran8

apm/apm-spans-traces/traces-spans.rst

@@ -128,48 +128,4 @@ You can add custom span tags through the OpenTelemetry Collector, or when you in
 
 Span tags are most useful when they follow a simple, dependable system of naming conventions. See :ref:`span-tag-naming` to learn about OpenTelemetry naming conventions for span tags. 
 
-.. note:: Span tags in Splunk APM are distinct from metadata tags in Splunk Infrastructure Monitoring, which are searchable labels or keywords you can assign to metric dimensions in the form of strings rather than as key-value pairs. To learn more about metadata tags, see :ref:`metadata-infra-tags`.
-
-
-.. raw:: html
-  
-    <embed>
-      <h2>Identities<a name="identities" class="headerlink" href="#identities" title="Permalink to this headline">¶</a></h2>
-    </embed>
-
-An identity represents a unique set of indexed span tags for a Splunk APM object, and always includes at least one service. 
-
-APM objects can generate multiple identities that correspond to the same APM object. If a set of indexed span tags for a span that corresponds to a certain APM object is unique, the APM object generates a new identity for the unique set of indexed span tags. 
-
-For example, a service ``myService`` reports a tenant span tag ``something`` for its endpoint ``/foo/bar``, and doesn't report a tenant span tag for its endpoint ``/another/endpoint``. Because ``myService`` reports a tenant span tag for one endpoint and not another, it forces the endpoint without a specified tenant span tag to have a tenant span tag value of ``unknown``. As a result, the service has two unique sets of span tags, and two identities. 
-
-An identity can represent any one of these APM objects:
-
-.. list-table::
-   :header-rows: 1
-   :widths: 20, 40, 40
-
-   * - :strong:`APM object`
-     - :strong:`Example`
-     - :strong:`Description`
-   
-   * - Service
-     - ``Service-1``
-     - The name of a service you instrumented and are collecting traces from.
-
-   * - Endpoint
-     - ``Service-1.Endpoint-1``
-     - The first span for a service.
-
-   * - Operation
-     - ``Service-1.Operation-1``
-     - A span within a single service.
-
-   * - Edge
-     - ``Service-1.Endpoint-1->Service-2.Endpoint-2``
-     - The span between two services.
-
-   * - Workflow
-     - ``Service-1.InitEndpoint-1``
-     - The endpoint where traces initiate.
-
+.. note:: Span tags in Splunk APM are distinct from metadata tags in Splunk Infrastructure Monitoring, which are searchable labels or keywords you can assign to metric dimensions in the form of strings rather than as key-value pairs. To learn more about metadata tags, see :ref:`metadata-infra-tags`.

apm/key-concepts.rst

@@ -28,9 +28,6 @@ Splunk APM is an Application Performance Monitoring solution that collects every
    * - :ref:`environment<environment-concept>`
      - A distinct deployment of your application that doesn't interact directly with other deployments of the same application.  
 
-   * - :ref:`identity<identity-concept>`
-     - A unique set of indexed span tags that corresponds to a Splunk APM object. 
-
    * - :ref:`indexed span tag<indexed-tag-concept>`
      - A span tag for which Splunk generates Troubleshooting MetricSets.
 
@@ -102,16 +99,6 @@ A special type of operation where the root span's ``span.kind = SERVER``. A give
 
 The term “environment” refers to the deployment environment, which is a distinct deployment in Splunk APM that doesn't interact directly with other deployments of the same application. Separate deployment environments are often used for different stages of the development process, such as development, staging, and production. For more information, see :ref:`apm-environments`. 
 
-.. _identity-concept:
-
-.. raw:: html
-
-  <embed>
-    <h3>identity<a name="identity-concept" class="headerlink" href="#identity-concept" title="Permalink to this headline">¶</a></h3>
-  </embed>
-
-A unique set of indexed span tags that corresponds to a Splunk APM object. An identity can represent a service, endpoint, operation, edge, or workflow, and is always related to at least one service. For more information, see :ref:`apm-traces-spans`.
-
 .. _inf-service-concept:
 
 .. raw:: html