Merge pull request #1594 from splunk/repo-sync

Pulling refs/heads/main into main

Author: aurbiztondo-splunk

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

@@ -39,19 +39,19 @@ Spans and traces form the backbone of application monitoring in Splunk APM. Use
 
 
 .. raw:: html
+  
+    <embed>
+      <h2>What are services?<a name="what-are-services" class="headerlink" href="#what-are-services" title="Permalink to this headline">¶</a></h2>
+    </embed>
 
-  <embed>
-    <h2>What are services?</h2>
-  </embed>
 
 Services are the key components of the systems you can monitor with Splunk APM. 
 
-
 .. raw:: html
-
-  <embed>
-    <h2>What are traces and spans?</h2>
-  </embed>
+  
+    <embed>
+      <h2>What are traces and spans?<a name="what-are-traces-spans" class="headerlink" href="#what-are-traces-spans" title="Permalink to this headline">¶</a></h2>
+    </embed>
 
 
 A trace is a collection of operations that represents a unique transaction handled by an application and its constituent services. A span represents a single operation within a trace. 
@@ -66,13 +66,11 @@ The following image illustrates the relationship between traces and spans:
 
 A span might refer to another span as its parent, indicating a relationship between operations involved in the trace. In the preceding image, span A is a parent span, and span B is a child span. This relationship might indicate that, for example, span A makes a service call that triggers the operation captured by span B. In this image, span C is also a child of span B, and so on. 
 
-
 .. raw:: html
-
-  <embed>
-    <h2>Span metadata</h2>
-  </embed>
-
+  
+    <embed>
+      <h2>Span metadata<a name="span-metadata" class="headerlink" href="#span-metadata" title="Permalink to this headline">¶</a></h2>
+    </embed>
 
 Each span contains metadata about the operation captured by the span and the service in which the operation took place. 
 
@@ -117,12 +115,11 @@ Each span contains the following basic metadata:
      -  Delay between the start of the parent trace and the start of this particular span
 
 
-
 .. raw:: html
-
-  <embed>
-    <h2>Span tags</h2>
-  </embed>
+  
+    <embed>
+      <h2>Span tags<a name="span-tags" class="headerlink" href="#span-tags" title="Permalink to this headline">¶</a></h2>
+    </embed>
 
 
 Span tags are key-value pairs that provide additional information and context about the operations a span represents. Both the keys and values are strings, and span tag keys for a single span must be unique. You can use span tags to query and filter traces, or to get information about the spans of a trace during troubleshooting.
@@ -131,47 +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</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

gdi/get-data-in/connect/aws/get-awstoc.rst

@@ -137,7 +137,9 @@ To manage the amount of data to import, see :ref:`aws-infra-import`.
     <h3>Recommended stats<a name="aws-metricstreams" class="headerlink" href="#aws-metricstreams" title="Permalink to this headline">¶</a></h3>
   </embed>
 
-If you're polling data, by default Splunk Observability Cloud only imports certain stats, which are based on AWS' own recommended stats and vary with service. See the :ref:`list of recommended stats <aws-recommended-stats>` used by Splunk Observability Cloud.
+If you're polling data, by default Splunk Observability Cloud only imports certain stats, which are based on AWS' own recommended stats and vary with each service. See the :ref:`list of recommended stats <aws-recommended-stats>` used by Splunk Observability Cloud.
+
+If you're using Metric Streams, by default Splunk Observability Cloud streams all stats.
 
 .. _aws-data-availability:
 

gdi/opentelemetry/components/kubernetes-objects-receiver.rst

@@ -9,7 +9,7 @@ Kubernetes objects receiver
 
 The Kubernetes Objects receiver collects objects from the Kubernetes API server. The supported pipeline is ``logs``. See :ref:`otel-data-processing` and :ref:`kubernetes-config-logs` for more information.
 
-.. note:: This receiver supports authentication via service accounts only at the moment. 
+.. note:: This receiver supports authentication through service accounts only at the moment. 
 
 Get started
 ======================
@@ -95,11 +95,12 @@ Configure the resources for the Kubernetes deployment
 
 Follow these sections to set up the various Kubernetes resources required to deploy the Collector with the receiver.
 
-Configuration
+Manual deployment
 --------------------------------------
 
 Create a ConfigMap with the config for ``otelcontribcol``, replacing ``OTLP_ENDPOINT`` with a valid value.
 
+
 .. code-block:: yaml
 
    apiVersion: v1
@@ -129,6 +130,25 @@ Create a ConfigMap with the config for ``otelcontribcol``, replacing ``OTLP_ENDP
              receivers: [k8sobjects]
              exporters: [otlp]
 
+Chart deployment
+--------------------------------------
+
+Alternatively, use the following Helm chart deployment instead of the manual deployment:
+
+.. code-block:: yaml
+
+   clusterReceiver:
+    k8sObjects:
+      - name: pods
+        mode: pull
+        label_selector: environment in (production),tier in (frontend)
+        field_selector: status.phase=Running
+        interval: 15m
+      - name: events
+        mode: watch
+        group: events.k8s.io
+        namespaces: [default] 
+
 Service account
 --------------------------------------
 

sp-oncall/notifications/notification-types.rst

@@ -30,10 +30,10 @@ You can also configure delayed notifications for alerts that may auto-resolve wi
 
 
 .. raw:: html
-
-  <embed>
-    <h2>Push notification</h2>
-  </embed>
+  
+    <embed>
+      <h2>Push notification<a name="push-notification" class="headerlink" href="#push-notification" title="Permalink to this headline">¶</a></h2>
+    </embed>
 
 
 Push notifications are sent through the application. We use push for:
@@ -46,69 +46,67 @@ Push notifications are sent through the application. We use push for:
 When a push notification is used to deliver a page, you will have the option to acknowledge, reroute, or snooze the incident straight from the notification.
 
 .. image:: /_images/spoc/notif-types1.png
-    :width: 100%
+    :width: 35%
     :alt: Splunk On-Call push notification.
 
-
 .. raw:: html
-
-  <embed>
-    <h2>SMS</h2>
-  </embed>
+  
+    <embed>
+      <h2>SMS<a name="sms" class="headerlink" href="#sms" title="Permalink to this headline">¶</a></h2>
+    </embed>
 
 SMS notifications can be used in your personal paging policy. The message you receive is, at most, 160 characters, and it displays the
 incident number, entity_display_name, and response code if two-way SMS is supported. When you receive an SMS notification, two codes are included in the message so you can acknowledge aor resolve the alert by responding with the correct five-digit code. These response codes expire after 1 hour.
 
 .. image:: /_images/spoc/notif-types2.png
-    :width: 100%
+    :width: 35%
     :alt: Splunk On-Call SMS notification.
 
-
 .. raw:: html
-
-  <embed>
-    <h2>SMS Subscription Management</h2>
-  </embed>
+  
+    <embed>
+      <h3>SMS Subscription Management<a name="sms-subscription" class="headerlink" href="#sms-subscription" title="Permalink to this headline">¶</a></h3>
+    </embed>
 
 You may stop and start our SMS notification subscription by replying to the message with STOP or START. Although, it is best to manage your notifications from the personal profile page in Splunk On-Call.
 
 .. raw:: html
-
-  <embed>
-    <h2>WhatsApp</h2>
-  </embed>
+  
+    <embed>
+      <h2>WhatsApp<a name="whatsapp" class="headerlink" href="#whatsapp" title="Permalink to this headline">¶</a></h2>
+    </embed>
 
 You can use WhatsApp notifications in your personal paging policy. To enable WhatsApp, download and configure the WhatsApp application from the Apple App Store or Google Play Store. Next, access your user profile in Splunk On-Call and enter and verify your mobile number. After verification, an :guilabel:`Enable WhatsApp` button will appear next to the number and you'll be able to use WhatsApp in your Paging Policy.
 
 .. raw:: html
-
-  <embed>
-    <h2>Email</h2>
-  </embed>
+  
+    <embed>
+      <h2>Email<a name="email" class="headerlink" href="#email" title="Permalink to this headline">¶</a></h2>
+    </embed>
 
 Emails can be used for pages. Emails can also be used as reminders that your Splunk On-Call instance is in :ref:`maintenance-mode`, or that you have a gap in your schedule due to a :ref:`scheduled-overrides` that is not covered.
 
 .. image:: /_images/spoc/notif-types3.png
-    :width: 100%
+    :width: 75%
     :alt: Splunk On-Call email notification.
 
 Scheduled Override:
 
 .. image:: /_images/spoc/notif-types4.png
-    :width: 100%
+    :width: 75%
     :alt: Splunk On-Call scheduled override email.
 
 Maintenance Mode:
 
 .. image:: /_images/spoc/notif-types5.png
-    :width: 100%
+    :width: 75%
     :alt: Splunk On-Call scheduled maintenance override.
 
 .. raw:: html
-
-  <embed>
-    <h2>Phone</h2>
-  </embed>
+  
+    <embed>
+      <h2>Phone<a name="phone" class="headerlink" href="#phone" title="Permalink to this headline">¶</a></h2>
+    </embed>
 
 Phone calls are used for paging. The “entity_display_name” field is read
 aloud and then an option to acknowledge or resolve the alert is offered.