diff --git a/_includes/gdi/available-aws.rst b/_includes/gdi/available-aws.rst index ec3f72c54..6fb41e412 100644 --- a/_includes/gdi/available-aws.rst +++ b/_includes/gdi/available-aws.rst @@ -88,7 +88,7 @@ You can collect data from the following AWS services: - :strong:`X` - - - - + - :strong:`X` * - AWS/CloudFront - AWS CloudFront diff --git a/admin/references/data-retention.rst b/admin/references/data-retention.rst index 0cfd5597f..9a2dff715 100644 --- a/admin/references/data-retention.rst +++ b/admin/references/data-retention.rst @@ -88,14 +88,6 @@ The following table shows the retention time period for each data type in APM. - * 8 days -.. _log-observer-data-retention: - -Data retention in Log Observer -============================================ - -The retention period for indexed logs in Splunk Log Observer is 30 days. - - .. _oncall-data-retention: Data retention in Splunk On-Call diff --git a/admin/subscription-usage/subscription-usage-overview.rst b/admin/subscription-usage/subscription-usage-overview.rst index e1d6ddf90..5b31482d8 100644 --- a/admin/subscription-usage/subscription-usage-overview.rst +++ b/admin/subscription-usage/subscription-usage-overview.rst @@ -5,7 +5,7 @@ Monitor and manage subscription usage and billing ********************************************************************* .. meta:: - :description: Monitor your Infrastructure Monitoring, APM, and Log Observer subscription usage. + :description: Monitor your Splunk Observability Cloud subscription usage. .. toctree:: :hidden: diff --git a/apm/db-query-perf/db-perf-troubleshooting.rst b/apm/db-query-perf/db-perf-troubleshooting.rst index aff471069..e298d8c22 100644 --- a/apm/db-query-perf/db-perf-troubleshooting.rst +++ b/apm/db-query-perf/db-perf-troubleshooting.rst @@ -55,7 +55,7 @@ If you are seeing database latency, but the query itself is not causing the issu * :ref:`microsoft-sql-server` * :ref:`postgresql` -You can also use the Related Content tiles to pivot to Infrastructure Monitoring or Log Observer and further analyze database issues. See :ref:`get-started-relatedcontent` to learn more about Related Content. +You can also use the Related Content tiles to pivot to Infrastructure Monitoring to further analyze database issues. See :ref:`get-started-relatedcontent` to learn more about Related Content. .. _disable-db-normalization: diff --git a/apm/profiling/get-data-in-profiling.rst b/apm/profiling/get-data-in-profiling.rst index 2497c8a10..487f11f8b 100644 --- a/apm/profiling/get-data-in-profiling.rst +++ b/apm/profiling/get-data-in-profiling.rst @@ -20,14 +20,12 @@ To get data into Splunk APM AlwaysOn Profiling, you need the following: AlwaysOn Profiling is activated for all host-based subscriptions. For subscriptions based on traces analyzed per minute (TAPM), check with your Splunk support representative. -.. note:: You don't need Log Observer to get data into Splunk APM AlwaysOn Profiling. See :ref:`exclude-log-data` for more information. - .. _profiling-setup-helm: Helm chart deployments --------------------------------------------------------------- -If you're deploying the Splunk Distribution of OpenTelemetry Collector using Helm, pass the following value when installing the chart: +If you're deploying the Splunk Distribution of the OpenTelemetry Collector using Helm, pass the following value when installing the chart: .. code-block:: bash @@ -43,7 +41,7 @@ You can also edit the parameter in the values.yaml file itself. For example: # If you don't use AlwaysOn Profiling for Splunk APM, you can disable it. profilingEnabled: false -If you don't have a Log Observer entitlement and are using a version of the OTel Collector lower than 0.78.0, make sure to turn off logs collection: +If you are using a version of the OTel Collector lower than 0.78.0, make sure to turn off logs collection: .. code-block:: yaml diff --git a/data-visualization/dashboards/view-dashboards.rst b/data-visualization/dashboards/view-dashboards.rst index 06c02ecc9..125248b41 100644 --- a/data-visualization/dashboards/view-dashboards.rst +++ b/data-visualization/dashboards/view-dashboards.rst @@ -109,7 +109,7 @@ From the :strong:`Chart actions` menu, you can perform the following tasks: * Select :strong:`Troubleshoot from this Time Window (RUM)` to explore related data in Splunk RUM. (This option only exists if RUM contains data related to data in the logs chart.) -* Select :strong:`Delete` to remove your logs chart from the dashboard. Deleting it from the dashboard does not impact the query you used to create your logs chart in Log Observer. +* Select :strong:`Delete` to remove your logs chart from the dashboard. Deleting it from the dashboard does not impact the query you used to create it. Not all actions are available for all chart types. diff --git a/gdi/get-data-in/connect/aws/aws-cloudformation.rst b/gdi/get-data-in/connect/aws/aws-cloudformation.rst index 17e5601bf..021e9b6a0 100644 --- a/gdi/get-data-in/connect/aws/aws-cloudformation.rst +++ b/gdi/get-data-in/connect/aws/aws-cloudformation.rst @@ -9,6 +9,8 @@ Available CloudFormation and Terraform templates To create Splunk-managed Metric Streams resources you can either use :ref:`CloudFormation ` or a :ref:`Terraform template `. +.. note:: To collect logs, see :ref:`aws-logs`. + .. _aws-cloudformation-use: Use CloudFormation to connect to Splunk Observability Cloud @@ -24,8 +26,6 @@ To use CloudFormation to connect to Splunk Observability Cloud follow these step 3. Select the QuickLink for your chosen template. The QuickLink automatically opens the AWS Management Console in the last region you used, but you can select any other region in the AWS Management Console. -.. caution:: Splunk Log Observer is no longer available for new users. You can continue to use Log Observer if you already have an entitlement. To collect logs, see :ref:`aws-logs`. - .. _aws-cloudformation-templates: Prepopulated CloudFormation templates diff --git a/gdi/get-data-in/connect/aws/aws-logs.rst b/gdi/get-data-in/connect/aws/aws-logs.rst index 0dae1b099..dbd5bd10c 100644 --- a/gdi/get-data-in/connect/aws/aws-logs.rst +++ b/gdi/get-data-in/connect/aws/aws-logs.rst @@ -11,5 +11,4 @@ Log collection is not available in Splunk Observability Cloud. Instead, you can use the Data Manager to send your AWS logs to Splunk Platform. Learn how at :new-page:`Onboard AWS in Data Manager `. To query logs, use Log Observer Connect. See more at :ref:`logs-intro-logconnect`. -If you have a Log Observer entitlement, you must transition to Splunk Cloud Platform or Splunk Enterprise. Read more at :ref:`lo-transition`. diff --git a/gdi/get-data-in/connect/aws/aws-post-install.rst b/gdi/get-data-in/connect/aws/aws-post-install.rst index 9696c1d42..c77e08f15 100644 --- a/gdi/get-data-in/connect/aws/aws-post-install.rst +++ b/gdi/get-data-in/connect/aws/aws-post-install.rst @@ -35,7 +35,7 @@ Locate your metrics See your logs ------------------------------------------------------ -Splunk Log Observer is no longer available for new users. You can continue to use Log Observer if you already have an entitlement. To collect logs, see :ref:`aws-logs`. +To collect and visualize your logs, see :ref:`aws-logs`. Use Dashboards and Related Content ------------------------------------------------------ diff --git a/gdi/get-data-in/connect/azure/azure-logs-ingestion.rst b/gdi/get-data-in/connect/azure/azure-logs-ingestion.rst index 38c25fc73..26a8d3d1c 100644 --- a/gdi/get-data-in/connect/azure/azure-logs-ingestion.rst +++ b/gdi/get-data-in/connect/azure/azure-logs-ingestion.rst @@ -12,5 +12,4 @@ Log collection is not available in Splunk Observability Cloud. Instead, you can use the Data Manager to send your Azure logs to Splunk Platform. Learn how at :new-page:`Onboarding for Azure data in Data Manager `. To query logs, use Log Observer Connect. See more at :ref:`logs-intro-logconnect`. -If you have a Log Observer entitlement, you must transition to Splunk Cloud Platform or Splunk Enterprise. Read more at :ref:`lo-transition`. diff --git a/gdi/get-data-in/connect/gcp/gcp-logs.rst b/gdi/get-data-in/connect/gcp/gcp-logs.rst index 2d635195d..0c8dbf376 100644 --- a/gdi/get-data-in/connect/gcp/gcp-logs.rst +++ b/gdi/get-data-in/connect/gcp/gcp-logs.rst @@ -12,7 +12,6 @@ Log collection is not available in Splunk Observability Cloud. Instead, you can use the Data Manager to send your GCP logs to Splunk Platform. Learn how at :new-page:`Onboard GCP in Data Manager `. To query logs, use Log Observer Connect. See more at :ref:`logs-intro-logconnect`. -If you have a Log Observer entitlement, you must transition to Splunk Cloud Platform or Splunk Enterprise. Read more at :ref:`lo-transition`. diff --git a/gdi/get-data-in/gdi-guide/apm/instrument-back-end.rst b/gdi/get-data-in/gdi-guide/apm/instrument-back-end.rst index 2da6ebd58..8a04a2033 100644 --- a/gdi/get-data-in/gdi-guide/apm/instrument-back-end.rst +++ b/gdi/get-data-in/gdi-guide/apm/instrument-back-end.rst @@ -35,7 +35,7 @@ After you've instrumented your application, you can access your data in the foll * The APM landing page * APM explorer view * Metric finder -* Splunk Log Observer +* Splunk Log Observer Connect Use one of these methods to make sure that your application data is reaching Splunk Observability Cloud. diff --git a/gdi/get-data-in/gdi-guide/infrastructure/send-server-cluster-data.rst b/gdi/get-data-in/gdi-guide/infrastructure/send-server-cluster-data.rst index 24b2d3e46..fdae0b119 100644 --- a/gdi/get-data-in/gdi-guide/infrastructure/send-server-cluster-data.rst +++ b/gdi/get-data-in/gdi-guide/infrastructure/send-server-cluster-data.rst @@ -10,7 +10,7 @@ Part 2: Install the OpenTelemetry Collector to send server and cluster data Install the :ref:`Splunk Distribution of OpenTelemetry Collector ` on any hosts or clusters you're using as a part of your infrastructure, such as servers running in your data center or on a virtual machine running in the cloud to: - Send metrics to Infrastructure Monitoring -- Send logs to Log Observer +- Query logs in Log Observer Connect - Set up your environment to receive logs and traces from applications instrumented in :ref:`instrument-back-end-services-apm`. .. image:: /_images/infrastructure/k8s-nav-pivot.gif @@ -87,10 +87,10 @@ You can find your infrastructure metrics by using the Splunk metric finder. For .. _query-logs-inframon: -Query logs in Log Observer +Query logs in Log Observer Connect ---------------------------------------------------------------------------------------------- -If you chose to ingest logs, you can query them in the Splunk Log Observer. For more information, see :ref:`logs-timeline`. +If you chose to ingest logs, you can query them in the Splunk Log Observer Connect. See more at :ref:`logs-intro-logconnect`. Next steps ========================================= diff --git a/gdi/opentelemetry/automatic-discovery/linux/linux-backend.rst b/gdi/opentelemetry/automatic-discovery/linux/linux-backend.rst index aae3d0ddc..d9460f3c2 100644 --- a/gdi/opentelemetry/automatic-discovery/linux/linux-backend.rst +++ b/gdi/opentelemetry/automatic-discovery/linux/linux-backend.rst @@ -91,7 +91,7 @@ Using the installer script, you can install and activate automatic discovery for curl -sSL https://dl.signalfx.com/splunk-otel-collector.sh > /tmp/splunk-otel-collector.sh && \ sudo sh /tmp/splunk-otel-collector.sh --with-instrumentation --realm -- - .. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. + .. note:: If you wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. The system-wide automatic discovery method automatically adds environment variables to ``/etc/splunk/zeroconfig/java.conf``. @@ -127,7 +127,7 @@ Using the installer script, you can install and activate automatic discovery for The ``systemd`` instrumentation automatically adds environment variables to ``/usr/lib/systemd/system.conf.d/00-splunk-otel-auto-instrumentation.conf``. - .. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. + .. note:: If you wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. To automatically define the optional ``deployment.environment`` resource attribute at installation time, run the installer script with the ``--deployment-environment `` option. Replace ```` with the desired attribute value, for example, ``prod``, as shown in the following example: @@ -232,7 +232,7 @@ Using the installer script, you can install and activate automatic discovery for curl -sSL https://dl.signalfx.com/splunk-otel-collector.sh > /tmp/splunk-otel-collector.sh && \ sh /tmp/splunk-otel-collector.sh --with-instrumentation --realm -- - .. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. + .. note:: If you wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. The system-wide automatic discovery method automatically adds environment variables to ``/etc/splunk/zeroconfig/node.conf``. @@ -259,7 +259,7 @@ Using the installer script, you can install and activate automatic discovery for The ``systemd`` automatic discovery method automatically adds environment variables to ``/usr/lib/systemd/system.conf.d/00-splunk-otel-auto-instrumentation.conf``. - .. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. + .. note:: If you wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. You can activate AlwaysOn Profiling for CPU and memory, as well as metrics, using additional options, as in the following example: @@ -311,7 +311,7 @@ Using the installer script, you can install and activate automatic discovery for curl -sSL https://dl.signalfx.com/splunk-otel-collector.sh > /tmp/splunk-otel-collector.sh && \ sudo sh /tmp/splunk-otel-collector.sh --with-instrumentation --realm -- - .. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. + .. note:: If you wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. The system-wide automatic discovery method automatically adds environment variables to ``/etc/splunk/zeroconfig/dotnet.conf``. @@ -347,7 +347,7 @@ Using the installer script, you can install and activate automatic discovery for The ``systemd`` instrumentation automatically adds environment variables to ``/usr/lib/systemd/system.conf.d/00-splunk-otel-auto-instrumentation.conf``. - .. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. + .. note:: If you wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance by specifying the ``--with-fluentd`` option. To automatically define the optional ``deployment.environment`` resource attribute at installation time, run the installer script with the ``--deployment-environment `` option. Replace ```` with the desired attribute value, for example, ``prod``, as shown in the following example: @@ -563,9 +563,9 @@ Update automatic discovery and configuration To manually upgrade the package: - 1. Download the ``splunk-auto-auto-instrumentation`` Debian or RPM package for the target system from the :new-page:`GitHub Releases page `. + 3. Download the ``splunk-auto-auto-instrumentation`` Debian or RPM package for the target system from the :new-page:`GitHub Releases page `. - 2. Run the following commands to install the package. Replace ```` with the local path to the downloaded package: + 4. Run the following commands to install the package. Replace ```` with the local path to the downloaded package: .. tabs:: diff --git a/gdi/opentelemetry/collector-kubernetes/kubernetes-config-logs.rst b/gdi/opentelemetry/collector-kubernetes/kubernetes-config-logs.rst index 4859f09f6..9e09a44d4 100644 --- a/gdi/opentelemetry/collector-kubernetes/kubernetes-config-logs.rst +++ b/gdi/opentelemetry/collector-kubernetes/kubernetes-config-logs.rst @@ -202,7 +202,7 @@ Collect Kubernetes events To see Kubernetes events as part of the :strong:`Events Feed` section in charts, set ``splunkObservability.infrastructureMonitoringEventsEnabled`` to ``true``. The cluster receiver will be configured with a Smart Agent receiver using the ``kubernetes-events`` monitor to send custom events. -To collect Kubernetes events as logs for Log Observer or Log Observer Connect using the Collector, you need to add ``clusterReceiver.k8sObjects`` to your configuration file, and set ``logsEnabled`` to ``true`` in either ``splunkObservability`` or ``splunkPlatform``. Events are processed in the ``logs`` pipeline. +To collect Kubernetes events as logs for Log Observer Connect using the Collector, you need to add ``clusterReceiver.k8sObjects`` to your configuration file, and set ``logsEnabled`` to ``true`` in either ``splunkObservability`` or ``splunkPlatform``. Events are processed in the ``logs`` pipeline. ``clusterReceiver.k8sObjects`` has the following fields: diff --git a/gdi/opentelemetry/collector-linux/linux-config-logs.rst b/gdi/opentelemetry/collector-linux/linux-config-logs.rst index 369cbd2c3..cb87cac59 100644 --- a/gdi/opentelemetry/collector-linux/linux-config-logs.rst +++ b/gdi/opentelemetry/collector-linux/linux-config-logs.rst @@ -18,7 +18,7 @@ Fluentd is turned off by default. If you already installed Fluentd on a host, re Collect Linux logs with Fluentd =========================================================================== -If you have a Log Observer entitlement or want to collect logs for the target host with Fluentd, use the ``--with-fluentd`` option to also install Fluentd when installing the Collector. For example: +If you want to collect logs for the target host with Fluentd, use the ``--with-fluentd`` option to also install Fluentd when installing the Collector. For example: .. code-block:: bash diff --git a/gdi/opentelemetry/collector-windows/install-windows-msi.rst b/gdi/opentelemetry/collector-windows/install-windows-msi.rst index 4ac957b6b..d832672e7 100644 --- a/gdi/opentelemetry/collector-windows/install-windows-msi.rst +++ b/gdi/opentelemetry/collector-windows/install-windows-msi.rst @@ -163,7 +163,7 @@ Learn more about advanced configuration options (including Service Logging) usin Install Fluentd MSI for log collection ================================================== -If you have a Log Observer entitlement or wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance. +If you have a wish to collect logs for the target host, make sure Fluentd is installed and enabled in your Collector instance. .. note:: You need to be an Admin to configure log collection with Fluentd. diff --git a/gdi/opentelemetry/collector-windows/install-windows.rst b/gdi/opentelemetry/collector-windows/install-windows.rst index b4eb21b57..05b4a90bb 100644 --- a/gdi/opentelemetry/collector-windows/install-windows.rst +++ b/gdi/opentelemetry/collector-windows/install-windows.rst @@ -179,7 +179,7 @@ Use the Universal Forwarder to send logs to the Splunk platform. See more at :re Collect Windows logs with Fluentd --------------------------------------- -If you have a Log Observer entitlement or wish to collect logs for the target host with Fluentd, use the ``with_fluentd = 1`` option to install and enable Fluentd when installing the Collector. For example: +If you wish to collect logs for the target host with Fluentd, use the ``with_fluentd = 1`` option to install and enable Fluentd when installing the Collector. For example: .. code-block:: PowerShell diff --git a/gdi/opentelemetry/components/fluentd-receiver.rst b/gdi/opentelemetry/components/fluentd-receiver.rst index fcead782a..578e8100d 100644 --- a/gdi/opentelemetry/components/fluentd-receiver.rst +++ b/gdi/opentelemetry/components/fluentd-receiver.rst @@ -69,4 +69,4 @@ For troubleshooting Fluentd, see: * :ref:`fluentd-collector-troubleshooting` * :ref:`otel-linux-uninstall-both-otel-and-tdagent` -.. caution:: If you have a Log Observer entitlement or wish to collect logs for the target host with Fluentd, make sure Fluentd is installed and turned on in your Collector instance. +.. caution:: If you wish to collect logs for the target host with Fluentd, make sure Fluentd is installed and turned on in your Collector instance. diff --git a/gdi/opentelemetry/components/splunk-hec-exporter.rst b/gdi/opentelemetry/components/splunk-hec-exporter.rst index ae198aabd..0af80027b 100644 --- a/gdi/opentelemetry/components/splunk-hec-exporter.rst +++ b/gdi/opentelemetry/components/splunk-hec-exporter.rst @@ -15,8 +15,6 @@ The exporter also sends AlwaysOn Profiling data to Splunk Observability Cloud. F For information about the HEC receiver, see :ref:`splunk-hec-receiver`. -.. caution:: Splunk Log Observer is no longer available for new users. You can continue to use Log Observer if you already have an entitlement. - Get started ====================== @@ -239,7 +237,7 @@ To turn off log collection for Splunk Observability Cloud while preserving Alway sourcetype: "otel" log_data_enabled: false -If you need to turn off log data export to Splunk Observability Cloud, for example because you're using Log Observer Connect or because you don't have Log Observer in your organization, set ``log_data_enabled`` to ``false`` in the ``splunk_hec`` exporter of your Collector configuration file: +If you need to turn off log data export to Splunk Observability Cloud, for example because you're using Log Observer Connect, set ``log_data_enabled`` to ``false`` in the ``splunk_hec`` exporter of your Collector configuration file: .. code-block:: yaml :emphasize-lines: 6 diff --git a/gdi/opentelemetry/install-the-collector.rst b/gdi/opentelemetry/install-the-collector.rst index afb4acead..be6f6ae53 100644 --- a/gdi/opentelemetry/install-the-collector.rst +++ b/gdi/opentelemetry/install-the-collector.rst @@ -170,7 +170,7 @@ To collect logs with the Splunk Distribution of the OpenTelemetry Collector: * In Kubernetes environments, native OpenTelemetry log collection is supported by default. See more at :ref:`kubernetes-config-logs`. * For Linux and Windows environments (physical hosts and virtual machines), use the Universal Forwarder to send logs to the Splunk platform. See more at :ref:`collector-with-the-uf`. -.. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, install and enable Fluentd in your Collector instance. +.. note:: If you wish to collect logs for the target host, install and enable Fluentd in your Collector instance. .. raw:: html diff --git a/gdi/opentelemetry/opentelemetry.rst b/gdi/opentelemetry/opentelemetry.rst index f9bb4987f..65becf81a 100644 --- a/gdi/opentelemetry/opentelemetry.rst +++ b/gdi/opentelemetry/opentelemetry.rst @@ -152,7 +152,7 @@ To collect logs with the Splunk Distribution of the OpenTelemetry Collector: * In Kubernetes environments, native OpenTelemetry log collection is supported by default. See more at :ref:`kubernetes-config-logs`. * For Linux and Windows environments (physical hosts and virtual machines), use the Universal Forwarder to send logs to the Splunk platform. See more at :ref:`collector-with-the-uf`. -.. note:: If you have a Log Observer entitlement or wish to collect logs for the target host, install and enable Fluentd in your Collector instance. +.. note:: If you wish to collect logs for the target host, install and enable Fluentd in your Collector instance. .. _otel-intro-enterprise: diff --git a/gdi/opentelemetry/smart-agent/smart-agent-migration-process.rst b/gdi/opentelemetry/smart-agent/smart-agent-migration-process.rst index e70f191b0..39daa1fbf 100644 --- a/gdi/opentelemetry/smart-agent/smart-agent-migration-process.rst +++ b/gdi/opentelemetry/smart-agent/smart-agent-migration-process.rst @@ -167,7 +167,7 @@ Check for the following errors: * 429 (TOO MANY REQUESTS): Org is not provisioned for the amount of traffic being sent; reduce traffic or request increase in capacity - * 503 (SERVICE UNAVAILABLE): If using the Log Observer, this is the same as 429 (because that is how HECv1 responds). Otherwise, check the status page. + * 503 (SERVICE UNAVAILABLE): Check the status page. To confirm that a specific receiver is fetching metrics exposed by an application, update the configuration file, as shown in the following example. @@ -198,7 +198,7 @@ If you are unable to determine the issue from logs, see :ref:`support`. Gather a .. _locate-sa-config-file: -3. Locate your existing Smart Agent configuration file +1. Locate your existing Smart Agent configuration file ================================================================ The Smart Agent can be configured by editing the agent.yaml file. By default, the configuration is installed at ``/etc/signalfx/agent.yaml`` on Linux and ``\ProgramData\SignalFxAgent\agent.yaml`` on Windows. If you override the location while installing the Smart Agent using the ``-config`` command line flag, the configuration file is stored at the location that you specify. diff --git a/gdi/opentelemetry/splunk-collector-troubleshooting.rst b/gdi/opentelemetry/splunk-collector-troubleshooting.rst index 86bd2604d..cc1be7185 100644 --- a/gdi/opentelemetry/splunk-collector-troubleshooting.rst +++ b/gdi/opentelemetry/splunk-collector-troubleshooting.rst @@ -234,7 +234,7 @@ If an HTTP request is not successfully completed, you might see the following HT * - ``429 (TOO MANY REQUESTS)`` - Organization is not provisioned for the amount of traffic being sent. Reduce traffic or request increase in capacity. * - ``503 (SERVICE UNAVAILABLE)`` - - If using the Log Observer, this is the same as the ``429 (TOO MANY REQUESTS)`` error code, due to how HECv1 responds. Otherwise, check the status page. + - Check the status page. Trace collection issues ================================ diff --git a/get-started/o11y.rst b/get-started/o11y.rst index d934ea737..df1a4e901 100644 --- a/get-started/o11y.rst +++ b/get-started/o11y.rst @@ -7,7 +7,7 @@ Get started with Splunk Observability Cloud .. meta:: :description: Learn how to get started with Splunk Observability Cloud in five steps. -This topic covers five high-level steps you can follow to get started with Splunk Observability Cloud and its products, which include Splunk Infrastructure Monitoring, Splunk Application Performance Monitoring (APM), Splunk Real User Monitoring (RUM), and Splunk Log Observer. +This topic covers five high-level steps you can follow to get started with Splunk Observability Cloud and its products, which include Splunk Infrastructure Monitoring, Splunk Application Performance Monitoring (APM), Splunk Real User Monitoring (RUM), and Splunk Log Observer Connect. For an introduction to Splunk Observability Cloud products, see :ref:`welcome`. @@ -29,7 +29,7 @@ Follow these steps to set up and make the most of Splunk Observability Cloud: - Cloud services, Servers, Server applications, Clusters, Applications, Serverless functions, User interfaces * - :ref:`get-started-explore` using: - - Infrastructure Monitoring, Real User Monitoring, Log Observer, Application Performance Monitoring, Related Content + - Infrastructure Monitoring, Real User Monitoring, Log Observer Connect, Application Performance Monitoring, Related Content * - :ref:`get-started-customize`: - Detectors and alerts, Custom dashboards, Span tags, Business workflows, Logs pipeline, Custom data @@ -75,7 +75,7 @@ Once you have data coming into Splunk Observability Cloud, it's time to do some - Use :ref:`Log Observer Connect ` to pinpoint interesting log events and troubleshoot issues with your infrastructure and cloud services. -- As described in step :ref:`get-started-gdi`, if you turned on :ref:`get-started-relatedcontent` when setting up your data integrations, you can select options in the Related Content bar to seamlessly navigate between APM, Log Observer, and Infrastructure Monitoring with your selected filters and context automatically applied to each view. +- As described in step :ref:`get-started-gdi`, if you turned on :ref:`get-started-relatedcontent` when setting up your data integrations, you can select options in the Related Content bar to seamlessly navigate between APM, Log Observer Connect, and Infrastructure Monitoring with your selected filters and context automatically applied to each view. - Use the :ref:`mobile app ` to check system critical metrics in Splunk Observability Cloud on the go, access real-time alerts with visualizations, and view mobile-friendly dashboards. diff --git a/logs/keyword.rst b/logs/keyword.rst index eedb96bd5..1e521804d 100644 --- a/logs/keyword.rst +++ b/logs/keyword.rst @@ -14,4 +14,4 @@ You can search for keywords, field names, or field values. To search your logs, .. include:: /_includes/logs/query-logs.rst -When you add keywords, field names, or field values to the filters, Log Observer narrows the results in the Timeline and the Logs table so that only records containing the selected fields and values appear. To learn how you can reuse a productive search in the future, see :ref:`logs-save-share`. +When you add keywords, field names, or field values to the filters, Log Observer Connect narrows the results in the Timeline and the Logs table so that only records containing the selected fields and values appear. To learn how you can reuse a productive search in the future, see :ref:`logs-save-share`.