Skip to main content

Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a DataSet / Scalyr location.
scalyr_api.png

DataSet / Scalyr

Create a DataSet / Scalyr Destination​

  1. Click the + icon on the Nexset that will be sent to the DataSet / Scalyr destination, and select the Send to Destination option from the menu.

  2. Select the DataSet / Scalyr connector from the list of available destination connectors. Then, select the credential that will be used to connect to your DataSet / Scalyr account, and click Next; or, create a new DataSet / Scalyr credential for use in this flow.

  3. In Nexla, DataSet / Scalyr destinations can be created using pre-built endpoint templates, which expedite destination setup for common DataSet / Scalyr endpoints. Each template is designed specifically for the corresponding DataSet / Scalyr endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    DataSet / Scalyr destinations can also be configured manually, allowing you to send data to DataSet / Scalyr endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common DataSet / Scalyr endpoints. Each template is designed specifically for the corresponding DataSet / Scalyr endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Add Group

    This endpoint template adds a group to your DataSet / Scalyr account using records from a Nexset. Use this template when you need to create or update groups in your DataSet / Scalyr account. Please see the Scalyr API documentation for required record structure.

    • This endpoint sends data as JSON in the request body to add groups to your DataSet / Scalyr account. Each record from your Nexset will be sent as a separate API request to add a group in DataSet / Scalyr. The request body should contain the group data in the format required by the DataSet / Scalyr API.

    This endpoint sends data as JSON in the request body to add groups to your DataSet / Scalyr account. Each record from your Nexset will be sent as a separate API request to add a group in DataSet / Scalyr. The request body should contain the group data in the format required by the DataSet / Scalyr API.

    The group structure must match the DataSet / Scalyr API's expected format. For detailed information about group creation, request body formats, available group properties, and group management, see the DataSet / Scalyr API documentation.

    Add Events

    This endpoint template adds events to your DataSet / Scalyr account using records from a Nexset. Use this template when you need to send log events to your DataSet / Scalyr account. Please note that this endpoint requires a credential with Log Write Access Key.

    • Enter the batch size in the Batch Size field. This should be the maximum number of events to add per batch (default: 1000). The batch size determines how many events will be included in each API request.
    • Select the content compression from the Content Compression pulldown menu. Available options include None (send uncompressed data) and Compress with GZIP (enable GZIP compression). Compression reduces bandwidth usage and is recommended for large data volumes.

    This endpoint sends data as JSON in the request body to add events to your DataSet / Scalyr account. The endpoint uses batch mode to efficiently send multiple events in a single request. Each record from your Nexset will be included in the batch, and events will be added in batches of up to the specified batch size per request.

    This endpoint requires a credential with Log Write Access Key. The event structure must match the DataSet / Scalyr API's expected format. Each event should include the necessary event data. For detailed information about event creation, request body formats, batch processing, and available event properties, see the DataSet / Scalyr API documentation.

Configure Manually​

DataSet / Scalyr destinations can be manually configured to send data to any valid DataSet / Scalyr API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the DataSet / Scalyr API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the DataSet / Scalyr API from the Method pulldown menu. DataSet / Scalyr API typically uses POST method for creating resources and adding events.

Data Format​

  1. Select the format in which the Nexset data will be sent to the DataSet / Scalyr API from the Content Format pulldown menu. DataSet / Scalyr API expects JSON format for all requests.

API Endpoint URL​

  1. Enter the URL of the DataSet / Scalyr API endpoint to which data will be sent in the URL field. This should be the complete URL to your DataSet / Scalyr endpoint (e.g., https://app.scalyr.com/api/addGroup, https://app.scalyr.com/api/addEvents). Include any required query parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The DataSet / Scalyr API endpoint URL should point to the endpoint where you want to add groups or events. The endpoint URL should include the API path (/api/) and the resource type path. You can test the endpoint using the Test button after configuring the URL.

Request Body​

  1. Configure the request body that will be sent to the DataSet / Scalyr API. The request body should contain the resource data formatted as JSON, with field names matching the DataSet / Scalyr API's expected structure. The request body format is typically {message.json} to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings. For batch operations, you may need to format the request body to include an events array containing event data.

The request body must be valid JSON and must match the DataSet / Scalyr API's expected format for the specific endpoint you're using. DataSet / Scalyr API uses specific structures for different endpoints (groups, events, etc.). For detailed information about request body formats, available endpoints, and resource structures, see the DataSet / Scalyr API documentation.

Save the Destination​

  1. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the destination configuration for later use.