Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
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
2 changes: 1 addition & 1 deletion gdi/get-data-in/connect/aws/aws-connect-ms.rst
Original file line number Diff line number Diff line change
Expand Up @@ -100,7 +100,7 @@ After creating an AWS IAM policy and assigning it to a particular role through t
Modify the scope of data collection
--------------------------------------------------

By default, Splunk Observability Cloud brings in data from all supported AWS services associated with your account, with :ref:`certain limitations <aws-data-limits>`.
By default Splunk Observability Cloud brings in data from all supported AWS services associated with your account, with :ref:`certain limitations <aws-data-limits>`. See :ref:`Supported integrations in Splunk Observability Cloud <aws-integrations>`. Splunk Observability Cloud also brings in 5 default stats per service: SampleCount (``count`` in Splunk Observability Cloud), Average (``mean``), Sum (``sum``), Minimum (``lower``), and Maximum (``upper``).

Use the check box options in the guided setup to limit the scope of your data collection. These are the available options:

Expand Down
7 changes: 1 addition & 6 deletions gdi/get-data-in/connect/aws/aws-connect-polling.rst
Original file line number Diff line number Diff line change
Expand Up @@ -101,10 +101,7 @@ After creating an AWS IAM policy and assigning it to a particular role through t
Modify the scope of data collection
--------------------------------------------------

By default, Splunk Observability Cloud brings in:

* Data from all supported AWS services associated with your account, with :ref:`certain limitations <aws-data-limits>`.
* 5 default stats per service: SampleCount (``count`` in Splunk Observability Cloud), Average (``mean``), Sum (``sum``), Minimum (``lower``), and Maximum (``upper``).
By default Splunk Observability Cloud brings in data from all supported AWS services associated with your account, with :ref:`certain limitations <aws-data-limits>`. See :ref:`Supported integrations in Splunk Observability Cloud <aws-integrations>`. Splunk Observability Cloud also brings in 5 default stats per service: SampleCount (``count`` in Splunk Observability Cloud), Average (``mean``), Sum (``sum``), Minimum (``lower``), and Maximum (``upper``).

Use the check box options in the guided setup to limit the scope of your data collection. These are the available options:

Expand All @@ -113,8 +110,6 @@ Use the check box options in the guided setup to limit the scope of your data co
* Select which :ref:`AWS regions <aws-regions>` to fetch data from.
* Select which AWS services to fetch data from.

.. note:: You can also choose to import recommended stats. Learn more at :ref:`aws-recommended-stats`.

To limit data collection, you can also:

- Manage the amount of data to import. See :ref:`aws-infra-import`.
Expand Down
6 changes: 3 additions & 3 deletions gdi/get-data-in/connect/aws/aws-recommended-stats.rst
Original file line number Diff line number Diff line change
@@ -1,15 +1,15 @@
.. _aws-recommended-stats:

************************************************************
AWS recommended stats (polling only)
AWS recommended stats (API only)
************************************************************

.. meta::
:description: List of recommended stats used in the AWS integration.

If you're polling data, by default Splunk Observability Cloud only polls these 5 statistics: SampleCount (``count`` in Splunk Observability Cloud), Average (``mean``), Sum (``sum``), Minimum (``lower``), and Maximum (``upper``).
If you connect your AWS services using the UI, Splunk Observability Cloud brings in 5 default stats per service: SampleCount (``count`` in Splunk Observability Cloud), Average (``mean``), Sum (``sum``), Minimum (``lower``), and Maximum (``upper``).

If you chose to import recommended stats, instead of default stats Splunk Observability Cloud imports a set of recommended stats which are based on AWS' own recommended stats and vary with service.
If you connect your services :new-page:`using the API <https://dev.splunk.com/observability/docs/integrations/aws_integration_overview#Specify-AWS-statistics>` you can choose to import certain stats only. These stats are based on AWS' own recommended stats and vary with each service.

List of recommended stats
==================================================
Expand Down
12 changes: 4 additions & 8 deletions gdi/get-data-in/connect/aws/get-awstoc.rst
Original file line number Diff line number Diff line change
Expand Up @@ -141,27 +141,23 @@ CloudWatch Metric Streams supports filtering by namespace and metric name but do
<h2>Imported data<a name="aws-imported-data" class="headerlink" href="#aws-imported-data" title="Permalink to this headline">¶</a></h2>
</embed>

By default, Splunk Observability Cloud brings in data from all supported AWS services associated with your account. See :ref:`Supported integrations in Splunk Observability Cloud <aws-integrations>` for a complete list of the services supported by default.
By default Splunk Observability Cloud brings in data from all supported AWS services associated with your account, with :ref:`certain limitations <aws-data-limits>`. See :ref:`Supported integrations in Splunk Observability Cloud <aws-integrations>` for a complete list of the services supported by default.

To manage the amount of data to import, see :ref:`aws-infra-import`.

.. raw:: html

<embed>
<h3>Custom services<a name="aws-custom-services" class="headerlink" href="#aws-custom-services" title="Permalink to this headline">¶</a></h3>
</embed>

You can also collect data from any custom service you've created in AWS, or from any namespace defined by AWS that Splunk Observability Cloud doesn't support by default. You can select which custom services to monitor at the Splunk Observability Cloud UI or :new-page:`configure them using the API <https://dev.splunk.com/observability/docs/integrations/aws_integration_overview#Specify-AWS-namespaces>`.

.. raw:: html

<embed>
<h3>Recommended stats<a name="aws-recstats" class="headerlink" href="#aws-recstats" title="Permalink to this headline">¶</a></h3>
</embed>
<h3>Imported stats<a name="aws-recstats" class="headerlink" href="#aws-recstats" title="Permalink to this headline">¶</a></h3>

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 connect your AWS services using the UI, Splunk Observability Cloud brings in 5 default stats per service: SampleCount (``count`` in Splunk Observability Cloud), Average (``mean``), Sum (``sum``), Minimum (``lower``), and Maximum (``upper``).

If you're using Metric Streams, by default Splunk Observability Cloud streams all stats.
If you connect your services :new-page:`using the API <https://dev.splunk.com/observability/docs/integrations/aws_integration_overview#Specify-AWS-statistics>` you can choose to import certain stats only. These stats 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.

.. _aws-data-availability:

Expand Down