Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pulling refs/heads/main into main #1356

Merged
merged 19 commits into from
May 27, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added _images/apm/db-query-perf/DIP-example.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added _images/infrastructure/DIP-example.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
6 changes: 4 additions & 2 deletions alerts-detectors-notifications/view-detectors.rst
Original file line number Diff line number Diff line change
Expand Up @@ -27,15 +27,17 @@ When you are looking at the Detector menu for a chart, or in the Infrastructure
..
|openmenu| is defined in conf.py

|openmenu| The following illustration shows two related detectors for this chart. If you hover over a related detector, you see options that let you :ref:`subscribe to the detector<subscribe>` by adding a new notification, open the detector for viewing or editing, or view the alerts triggered by the detector. To learn more, see :ref:`view-alerts`.
|openmenu| The following illustration shows two related detectors for this chart. If you hover over a related detector, you see options that let you :ref:`subscribe to the detector<subscribe>` by adding a new notification, open the detector for viewing or editing, or view the alerts triggered by the detector. To learn more, go to :ref:`view-alerts`.

.. image:: /_images/images-detectors-alerts/detectors-related.png
:width: 50%

View an individual detector
-------------------------------------------------------------------

When you open a detector, the Alert Rules tab is opened, and you see a chart that represents values for the visible signals. The list of detector rules, and the number of currently active alerts for each rule, is shown. To learn more, see :ref:`view-alerts-within-detector`. For information on creating rules, see :ref:`build-rules` or :ref:`apm-alerts`, depending on which type of detector you are creating.
There are two charts in the detector view. On the right side, you can see a detailed view. It shows each datapoint at the native resolution of the detector and represents exactly the datapoints that the detector sees. On the left side, you can see a summary view. It shows a summary of the data over a longer period of time. Because it is a summary, short spikes are not visible. The yellow box controls which part of the summary chart displays in the detail chart. You can see a short-term spike in the detail view by dragging the yellow box to the area where the alert fired.

The Alert Rules tab is open when you open a detector, showing a chart that represents values for the visible signals. The list of detector rules and the number of currently active alerts for each rule are visible. To learn more, see :ref:`view-alerts-within-detector`. For information on creating rules, see :ref:`build-rules` or :ref:`apm-alerts`, depending on which type of detector you are creating.

As with charts, the resolution of data displayed is determined by the chart's time range. The detail view at right displays data at the detector's resolution, that is, the frequency at which the detector evaluates the signal. Any events that have occurred during the detector's time range are shown under the X axis.

Expand Down
23 changes: 23 additions & 0 deletions apm/db-query-perf/db-query-performance.rst
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,29 @@ You can also use Database Query Performance to identify possible opportunities t

Database Query Performance is available by default, so all you need to do is turn on the feature so that APM automatically begins indexing database-related span tags. See :ref:`turn-on-db-perf` to get started monitoring database performance in APM.

.. _db-infra-perf-sidebar:

Monitor system health with Database Infrastructure Performance
------------------------------------------------------------------------

If, as a site reliability engineer, apparent slowness in microservices has you wondering whether to investigate your infrastructure further, you can use :strong:`Database Infrastructure Performance` for help with triage of the following conditions:

- Lock contention

- Limited I/O (throughput)

- Transient effects (spikes or constant loads)

The Database Infrastructure Performance panel displays at the bottom of the navigator sidebar when from :strong:`APM` in Splunk Observability, you use :strong:`Database Query Performance` to select a MySQL, SQL Server, or Oracle database service. You can also access the Database Infrastructure Performance panel through the :strong:`Service Map` module in the APM menu.

.. image:: /_images/apm/db-query-perf/DIP-example.png
:width: 50%
:alt: Database Infrastructure Performance panel


The performance metrics display is enabled by related content correlation of databases that happens when the OpenTelemetry (OTel) Collector is connected to a database. For more information, see :ref:`get-started-relatedcontent`. Expand the Database Infrastructue Performance panel to see the relevant Infrastructure Navigator view.
You can use this panel to review key metrics without leaving Splunk APM.

.. raw:: html

<embed>
Expand Down
5 changes: 3 additions & 2 deletions gdi/integrations/cloud-aws.rst
Original file line number Diff line number Diff line change
Expand Up @@ -216,8 +216,8 @@ You can collect data from the following AWS services:

* - AWS/EKS
- Amazon Elastic Kubernetes Service (EKS)
- :strong:`X`
- :strong:`X`
- :strong:`X` (5)
- :strong:`X` (5)
- :strong:`X`
- :strong:`X`

Expand Down Expand Up @@ -689,3 +689,4 @@ The following applies to the collected logs and metadata listed in the table:
#. EC2 tags & properties only
#. Logs collected by the CloudWatch agent stored in CloudWatch Logs
#. Metadata in this context refers to AWS tags and properties
#. Collected by the :ref:`Splunk Distribution of the Collector for Kubernetes <collector-kubernetes-intro>`
2 changes: 1 addition & 1 deletion splunkplatform/unified-id/unified-identity.rst
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ Organizations that complete the integration of Splunk Cloud Platform and Splunk
How to set up Unified Identity
==========================================================================================

You can pair only one Splunk Cloud Platform instance with one Splunk Observability Cloud instance at a time. Customers with multiple Splunk Observability Cloud organizations must choose one to pair with the chosen Splunk Cloud Platform instance.
You can pair only one Splunk Cloud Platform instance with one Splunk Observability Cloud instance at a time. Only one Splunk Observability Cloud organization can pair with a single Splunk Cloud Platform search head. Customers with multiple Splunk Observability Cloud organizations must choose one to pair with the chosen Splunk Cloud Platform instance.


Prerequisites
Expand Down
Loading