Authorization

Follow this guide to create a new DataSet / Scalyr credential that will allow Nexla to authenticate to and exchange data with your DataSet / Scalyr account.

DataSet / Scalyr

Prerequisites

Before creating a DataSet / Scalyr credential, you need to obtain your API keys from your DataSet / Scalyr account. DataSet / Scalyr uses API key authentication for all API requests, with different API keys for different access levels. The API key is sent in the Authorization header with the Bearer prefix.

To obtain your DataSet / Scalyr API keys, follow these steps:

1. Sign in to your DataSet / Scalyr account using your administrator credentials.

2. Navigate to your account settings or API management section in the DataSet / Scalyr interface.

3. Look for the API Keys or API section in your account settings, or navigate to Settings > API Keys or Account > API Keys.

4. If you don't have API keys yet, look for the option to generate or view your API keys.

5. Click Generate API Key or Create API Key to create a new API key.

6. Configure your API key settings:

   • Enter a name for the API key (e.g., "Nexla Integration")
   • Select the access level for the API key:
     • Configuration Write Access Key: Provides access to all methods available to Log Read Access and Configuration Read Access, plus methods to write configuration files
     • Log Write Access Key: Provides access to all methods available to Log Write Access
   • Review and select the permissions or scopes for the key (if applicable)

7. Click Generate or Create to create the API key.

8. Copy the API key immediately after it's generated, as it may not be accessible again after you navigate away from the page.

9. Store the API key securely, as you will need it to configure your Nexla credential. The API key is sensitive information and should be kept confidential.

The API key is sent in the Authorization: Bearer {key} header for all API requests to the DataSet / Scalyr API. Different API keys provide different levels of access to DataSet / Scalyr resources. The Configuration Write Access Key is necessary for accessing all methods available to Log Read Access and Configuration Read Access, plus methods to write configuration files. The Log Write Access Key is necessary for accessing all methods available to Log Write Access. If your API key is compromised, you should immediately revoke it in your DataSet / Scalyr account settings and generate a new one. For detailed information about obtaining API keys, API authentication, and available endpoints, refer to the DataSet / Scalyr API documentation.

Create a DataSet / Scalyr Credential

• To create a new DataSet / Scalyr credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – DataSet / Scalyr

Credential Name & Description

1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

   Resource descriptions are recommended but are not required. They should be used provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

API Key Authentication

DataSet / Scalyr uses API key authentication for all API requests. Different API keys provide different levels of access to DataSet / Scalyr resources. The API key is sent in the Authorization header with the Bearer prefix to authenticate API requests to the DataSet / Scalyr API.

DataSet / Scalyr Authentication Methods

Configuration Access Key

This key is necessary for accessing all methods available to Log Read Access and Configuration Read Access, plus methods to write configuration files. Use this method for data sources and destinations that require configuration access.

1. Enter your DataSet / Scalyr Configuration Write Access Key in the **Configuration Write Access Keys** field. This is the API key you obtained from your DataSet / Scalyr account settings (Settings > API Keys or Account > API Keys). The Configuration Write Access Key is sent in the `Authorization: Bearer {key}` header for all API requests to the DataSet / Scalyr API. The API key is sensitive information and must be kept confidential.

Log Write Access Key

This key is necessary for accessing all methods available to Log Write Access. Use this method for destinations that require log write access to add events to your DataSet / Scalyr account.

1. Enter your DataSet / Scalyr Log Write Access Key in the **Log Write Access Keys** field. This is the API key you obtained from your DataSet / Scalyr account settings (Settings > API Keys or Account > API Keys). The Log Write Access Key is sent in the `Authorization: Bearer {key}` header for all API requests to the DataSet / Scalyr API. The API key is sensitive information and must be kept confidential.

Your DataSet / Scalyr API keys can be found in your DataSet / Scalyr account settings under Settings > API Keys or Account > API Keys. The Configuration Write Access Key is necessary for accessing all methods available to Log Read Access and Configuration Read Access, plus methods to write configuration files. The Log Write Access Key is necessary for accessing all methods available to Log Write Access.

If your API key is compromised, you should immediately revoke it in your DataSet / Scalyr account settings and generate a new one. The API key provides access to your DataSet / Scalyr account data and should be treated as sensitive information. Keep your API key secure and do not share it publicly.

For detailed information about obtaining API keys, API authentication, and available endpoints, see the DataSet / Scalyr API documentation.

Save the Credential

1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.