From 251b0eec83d904326c50c64ccd6e7926ad2beb3d Mon Sep 17 00:00:00 2001 From: Anna Urbiztondo Date: Mon, 9 Sep 2024 06:14:30 +0200 Subject: [PATCH 1/2] OOTB content --- .../components/mssql-server-receiver.rst | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/gdi/opentelemetry/components/mssql-server-receiver.rst b/gdi/opentelemetry/components/mssql-server-receiver.rst index db2eab066..1b2a181cb 100644 --- a/gdi/opentelemetry/components/mssql-server-receiver.rst +++ b/gdi/opentelemetry/components/mssql-server-receiver.rst @@ -9,8 +9,6 @@ Microsoft SQL server receiver The Microsoft SQL Server receiver queries and retrieves metrics from Microsoft SQL Server instances. The receiver works by either using the Windows Performance Counters, or by directly connecting to the instance and querying it. The supported pipeline type is ``metrics``. See :ref:`otel-data-processing` for more information. -.. note:: Out-of-the-box dashboards and navigators aren't supported for the Microsoft SQL server receiver yet, but are planned for a future release. - The following applies: * Windows Performance Counters are only available when running on Windows. @@ -94,6 +92,15 @@ The following are Windows-specific optional options: * ``computer_name``. The computer name identifies the SQL Server name or IP address of the computer being monitored. If specified, ``instance_name`` is also required. This option is ignored in non-Windows environments. +.. _mssql-server-receiver-ootb: + +Enable built-in content +==================================== + +Splunk Observability Cloud provides built-in dashboards with charts that give you immediate visibility into the technologies and services being used in your environment. Learn more at :ref:`collector-builtin-dashboard`. + +For the MS SQL Server receiver out-of-the-box content to work properly, you need to explicitly enable and disable specific metrics in your configuration file. See the configuration that enables built-in content at :new-page:`SQL Server discovery yaml ` in GitHub. + .. _mssql-server-receiver-settings: Settings From dc1da3bc49701d5f6c995d582b1957deb053114d Mon Sep 17 00:00:00 2001 From: trangl Date: Wed, 18 Sep 2024 13:49:02 +0200 Subject: [PATCH 2/2] Add ServiceNow endpoints for clarification --- admin/notif-services/servicenow.rst | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/admin/notif-services/servicenow.rst b/admin/notif-services/servicenow.rst index d6411f6ef..8b29d70cd 100644 --- a/admin/notif-services/servicenow.rst +++ b/admin/notif-services/servicenow.rst @@ -35,15 +35,19 @@ Before you set up the integration, choose a ServiceNow issue type from the follo :width: 100 * - Issue type - - Role needed + - Role required + - ServiceNow endpoint * - Problem - ``user_admin``, ``itil`` + - ``/api/now/v2/table/problem`` * - Incident - ``user_admin``, ``itil`` + - ``/api/now/v2/table/incident`` * - Event - None + - ``/api/global/em/jsonv2`` -Make note of the role that corresponds to your issue type before proceeding with :ref:`servicenow2`. +Make note of the role and receiving endpoint that corresponds to your issue type before proceeding with :ref:`servicenow2`. .. note:: The ``user_admin`` role is used to verify that ServiceNow has successfully created a Problem or Incident. The ``itil`` role is used to create Problems and Incidents when alerts are sent.