From 7b8c5de6af680a808d513bbdb9af50de216fd55a Mon Sep 17 00:00:00 2001 From: asplulski Date: Tue, 29 Oct 2024 16:00:58 +0100 Subject: [PATCH 1/4] Update available-gcp.rst to update services with metadata sync --- _includes/gdi/available-gcp.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/_includes/gdi/available-gcp.rst b/_includes/gdi/available-gcp.rst index 9164693cf..ad95b1d87 100644 --- a/_includes/gdi/available-gcp.rst +++ b/_includes/gdi/available-gcp.rst @@ -28,7 +28,7 @@ You can collect data from the following GCP services out-of-the-box: * - cloudfunctions - Cloud Functions - :strong:`X` - - + - :strong:`X` * - cloudiot - Cloud Internet of Things Core @@ -38,7 +38,7 @@ You can collect data from the following GCP services out-of-the-box: * - cloudsql - Cloud SQL - :strong:`X` - - + - :strong:`X` * - cloudtasks - Cloud Tasks @@ -128,7 +128,7 @@ You can collect data from the following GCP services out-of-the-box: * - pubsub - Cloud Pub/Sub - :strong:`X` - - + - :strong:`X` * - redis - Memorystore for Redis @@ -143,7 +143,7 @@ You can collect data from the following GCP services out-of-the-box: * - run - Cloud Run - :strong:`X` - - + - :strong:`X` * - serviceruntime - Google Cloud Endpoints APIs From 507bf934c04b54af5a7078ada64ff3f22c42d6d3 Mon Sep 17 00:00:00 2001 From: asplulski Date: Wed, 30 Oct 2024 14:33:51 +0100 Subject: [PATCH 2/4] Update gcp-connect.rst to include permissions for tag sync for some newly supported services --- gdi/get-data-in/connect/gcp/gcp-connect.rst | 35 ++++++++++++++++++++- 1 file changed, 34 insertions(+), 1 deletion(-) diff --git a/gdi/get-data-in/connect/gcp/gcp-connect.rst b/gdi/get-data-in/connect/gcp/gcp-connect.rst index 1079f7879..3b70b652d 100644 --- a/gdi/get-data-in/connect/gcp/gcp-connect.rst +++ b/gdi/get-data-in/connect/gcp/gcp-connect.rst @@ -70,7 +70,7 @@ Alternatively you can create a more restrictive role using the permissions in th - Yes * - ``serviceusage.services.use`` - - Yes, if you want to activate the use of a quota from the project where metrics are stored + - Yes, if you either want to activate the use of a quota from the project where metrics are stored or sync cloud sql metadata - No, but included in ``roles/serviceusage.serviceUsageConsumer`` * - ``spanner.instances.list`` @@ -81,6 +81,39 @@ Alternatively you can create a more restrictive role using the permissions in th - Yes, if the Spanner service is activated - Yes + * - ``cloudsql.databases.list`` + - Yes, if the cloud sql service is activated + - Yes + + * - ``cloudsql.instances.list`` + - Yes, if the cloud sql service is activated + - Yes + + * - ``pubsub.topics.list`` + - Yes, if the pub/sub service is activated + - Yes + + * - ``pubsub.subscriptions.list`` + - Yes, if the pub/sub service is activated + - Yes + + * - ``run.jobs.list`` + - Yes, if the cloud run service is activated + - Yes + + * - ``run.revisions.list`` + - Yes, if the cloud run service is activated + - Yes + + * - ``cloudasset.assets.searchAllResources`` + - Yes, if the cloud run service is activated + - Yes + + * - ``cloudfunctions.functions.list`` + - Yes, if the cloud functions service is activated + - Yes + + .. _gcp-two: 2. Configure GCP From 1d886f2cdeffd4418927b7637ce88cb692272806 Mon Sep 17 00:00:00 2001 From: Bri Hillmer Date: Mon, 4 Nov 2024 10:17:50 -0700 Subject: [PATCH 3/4] move 3rd party metrics section --- get-started/get-started-guide/get-started-guide.rst | 4 ++-- get-started/get-started-guide/initial-rollout.rst | 9 +++++++++ get-started/get-started-guide/onboarding-readiness.rst | 9 --------- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/get-started/get-started-guide/get-started-guide.rst b/get-started/get-started-guide/get-started-guide.rst index 256518307..ab69115c2 100644 --- a/get-started/get-started-guide/get-started-guide.rst +++ b/get-started/get-started-guide/get-started-guide.rst @@ -75,11 +75,11 @@ The journey for getting started with Splunk Observability Cloud has 3 phases: on - * :ref:`advanced-config-custom-URL` * :ref:`advanced-config-parent-child` * :ref:`advanced-config-logs` - * :ref:`advanced-config-3rd-party` See :ref:`Phase 1 optional and advanced configurations `. - - * :ref:`phase3-network-exp` + - * :ref:`advanced-config-3rd-party` + * :ref:`phase3-network-exp` * :ref:`phase2-profiling` * :ref:`phase2-related-content` diff --git a/get-started/get-started-guide/initial-rollout.rst b/get-started/get-started-guide/initial-rollout.rst index 453f64635..0f4e4a4ef 100644 --- a/get-started/get-started-guide/initial-rollout.rst +++ b/get-started/get-started-guide/initial-rollout.rst @@ -96,6 +96,15 @@ Optional and advanced configurations Consider these optional and advanced configurations to customize your setup as they apply to your organization. +.. _advanced-config-3rd-party: + +Collect data from third-party metrics providers +-------------------------------------------------------------- + +When using the Splunk Distribution of OpenTelemetry Collector, you can use receivers to collect metrics data from third-party providers. For example, you can use the Prometheus receiver to scrape metrics data from any application that exposes a Prometheus endpoint. See :ref:`prometheus-receiver`. + +See :ref:`monitor-data-sources` for a list of receivers. + .. _phase3-network-exp: Set up Network Explorer to monitor network environment diff --git a/get-started/get-started-guide/onboarding-readiness.rst b/get-started/get-started-guide/onboarding-readiness.rst index 81b940307..49baea1c1 100644 --- a/get-started/get-started-guide/onboarding-readiness.rst +++ b/get-started/get-started-guide/onboarding-readiness.rst @@ -132,15 +132,6 @@ If your organization has an entitlement for Splunk Log Observer Connect, Splunk See :ref:`logs-set-up-logconnect` or :ref:`logs-scp`. -.. _advanced-config-3rd-party: - -Collect data from third-party metrics providers --------------------------------------------------------------- - -When using the Splunk Distribution of OpenTelemetry Collector, you can use receivers to collect metrics data from third-party providers. For example, you can use the Prometheus receiver to scrape metrics data from any application that exposes a Prometheus endpoint. See :ref:`prometheus-receiver`. - -See :ref:`monitor-data-sources` for a list of receivers. - Education resources ===================== From 458290840bbb283d7ba9aaa38f26d46d9b0831d5 Mon Sep 17 00:00:00 2001 From: gschatz Date: Mon, 4 Nov 2024 15:49:56 -0800 Subject: [PATCH 4/4] Remove extra page --- index.rst | 6 ------ synthetics/syn-troubleshoot/syn-missing-alerts.rst | 10 ---------- 2 files changed, 16 deletions(-) delete mode 100644 synthetics/syn-troubleshoot/syn-missing-alerts.rst diff --git a/index.rst b/index.rst index 9c819d21a..368648d28 100644 --- a/index.rst +++ b/index.rst @@ -770,12 +770,6 @@ To keep up to date with changes in the products, see the Splunk Observability Cl Troubleshoot tests TOGGLE - -.. toctree:: - :maxdepth: 3 - - Troubleshoot tests - .. toctree:: :caption: Splunk On-Call :maxdepth: 3 diff --git a/synthetics/syn-troubleshoot/syn-missing-alerts.rst b/synthetics/syn-troubleshoot/syn-missing-alerts.rst deleted file mode 100644 index 0dbf7eee3..000000000 --- a/synthetics/syn-troubleshoot/syn-missing-alerts.rst +++ /dev/null @@ -1,10 +0,0 @@ -.. _syn-missing-alerts: - -********************************************************* -Troubleshoot missing alerts -********************************************************* - -.. meta:: - :description: Troubleshoot broken tests - -Troubleshoot missing alerts in Synthetic tests.