Connect a Service Observability data source

Connect Service Observability to an external observability system. Service Observability displays metrics in the Service Operations Workspace (SOW) from that observability instance.

始める前に

You must enter a connection URL and credentials for your observability vendor. You can either use an existing connection or create one. Note the following for specific vendors:

表 : 1. Vendor-specific connection information

Observability Vendor	Connection information
AWS	The connection URL must be specific to the region to be monitored, for example, https://monitoring.us-east-2.amazonaws.com.
Azure	The connection URL should be https://management.azure.com.
Splunk Observability	The connection URL must include the Realm, for example, https://stream.[REALM].signalfx.com
Zabbix	The connection URL must be the IP on which the Zabbix server is hosted

If you're using existing credentials, you need the credential name. If you're creating credentials, collect the following information.

表 : 2. Vendor-specific credential requirements

Observability vendor	Credential type	Information needed
AppDynamics	OAuth 2.0	OAuth Client ID OAuth Client secret OAuth token URL AppDynamics account name
Azure	OAuth 2.0	OAuth Client ID OAuth Client secret OAuth token URL Subscription ID
AWS	AWS credentials	Access key Secret key If the user associated with this key is restricted to specific permissions, they must include the following, scoped to all resources: cloudwatch:Describe scoped to all resources cloudwatch:Get scoped to all resources cloudwatch:List scoped to all resources cloudtrail:LookupEvents tag:GetResources tag:GetTagKeys tag:GetTagValues apigateway:Get
Datadog	API	API key Application key If an application key is restricted to a specific scope, those scopes are required for the following endpoints: https://api.datadoghq.com/api/v2/catalog/entity https://api.datadoghq.com/api/v1/hosts https://api.datadoghq.com/api/v1/query https://api.datadoghq.com/api/v2/query/timeseries
Dynatrace SaaS Classic	API	API Tenant Access Token The token must have entities.read and metrics.read scope permissions.
Dynatrace SaaS Grail	API	API Platform Token The token must have storage:metrics.read and storage:bucket.read scope permissions.
Dynatrace on-premise	API	API key. The key must be an environment scoped token. The name of the MID Server your Dynatrace instance is hosted on
New Relic	API	Account ID API key
Prometheus on-premise	Basic Auth	Basic Auth credential user name Basic Auth credential password The name of the MID Server your Prometheus instance is hosted on
SolarWinds	Basic Auth	Basic Auth credential user name Basic Auth credential password The name of the MID Server your SolarWinds instance is hosted on
Splunk Enterprise	API	Bearer Token
Splunk Observability	API	Access token
ThousandEyes	API	API key
Zabbix	Basic Auth	Basic Auth credential user name Basic Auth credential password The name of the MID Server your Zabbix instance is hosted on. The MID Server must be in an active state.

Role required: sn_sow_svcobs.admin

このタスクについて

The first step to ingesting observability data is to create a connection to the observability instance.

Service Observability supports the following observability vendors:

• Amazon CloudWatch
• AppDynamics
• Cisco ThousandEyes synthetic tests
• Datadog
• DynatraceSaaS and on-premise (both Classic and Grail environments)
• Microsoft Azure Monitor
• New Relic
• Prometheus on-premise
• SolarWinds on-premise
• Splunk Observability and logs from Splunk Enterprise
• Zabbix on-premise

手順

1. Navigate based on your version of Service Observability.
   • Version 1.5.0: Navigate to All > Service Operations Workspace > Configurations, then navigate to Service Observability Management > Manage Observability > Data sources
   • Version 1.6 or later: Navigate to All > Service Operations Workspace > Configurations, then navigate to Service Observability > Data sources.
2. Select your observability vendor.
3. On the Add connection form, fill in the fields.
   You can use an existing HTTP or HTTPs connection and an existing credential or create one.
4. Select Save.

タスクの結果

A new connection appears in the list of observability data sources. You use this connection when you create a data mapping.

次のタスク

Map your connection to the services that you want to monitor in Service Observability. See Create and manage data mappings.