Permissions and Access
This page lists all data sources that require additional permissions to set up an Agent or Direct connection with Nobl9 or to configure alerts.
- To configure an Agent or Direct connection to Amazon Redshift, you must provide an AWS Secret ARN that is tagged with the RedshiftDataFullAccess permission.
For more information, refer to the Amazon Redshift | Nobl9 Documentation.
- The Nobl9 Agent must have firewall access to
- To connect to AppDynamics, the AppDynamics API client needs at least the Applications and Dashboards Viewer permissions.
For more information, refer to the AppDynamics | Nobl9 Documentation.
A Nobl9 Agent connection requires the following minimal set of permissions:
For more information, refer to the BigQuery | Nobl9 Documentation.
- To connect the Nobl9 Agent to Dynatrace, you need an access token with
For more information, refer to the Dynatrace | Nobl9 Documentation.
Google Cloud Monitoring
To configure an Agent or Direct connection to Google Cloud Monitoring, the user account must have access to one of the following OAuth scopes:
For more information, refer to the Google Cloud Monitoring | Nobl9 Documentation.
- Nobl9 Agent and Direct connections to Splunk require a
urlthat must point to the base API URL of the Splunk Search app. To access your Splunk Cloud Platform deployment using the Splunk REST API, you must submit a case requesting access via the Splunk Support Portal. Specifically, you should ask Splunk Support to open port
8089for REST access.
For more information, refer to the Splunk | Nobl9 Documentation.
- To configure an alert, the user must have access and permission to create an issue in a project in Jira.
For more information, refer to the Jira | Nobl9 Documentation.
- To allow ServiceNow alerts to integrate with Nobl9, you need to set up an Access Control List (ACL) for your ServiceNow users. To create a new ACL, you must have the
For more information, refer to the ServiceNow | Nobl9 Documentation.