Akamai

The following tutorial demonstrates how to collect your Akamai DataStream or Cloud Monitor logs and send them to Coralogix. Once ingested by our platform, query, archive, define alerts, and create dashboards with your data.

Akamai DataStream

Seamlessly collect Akamai DataStream logs and send them to Coralogix.

Prerequisites

A data stream created, including your Akamai data stream ID
API client for the DataStream Pull API set up, including the Client API host, client secret, access token, and client token.

Configuration

Coralogix supports logs collection from Akamai DataStream v2. To configure the logs delivery follow the next steps:

STEP 1. In your Property add “Log Request Details” behavior, switch “Include Custom Log Field” option and fill it with the content that will be recognized by Coralogix as subsystem name (the applicationName is taken from the “reqHost” field, and subsystemName is taken from the “customField”) :

STEP 2. In your Property add “DataStream” behavior, select “Stream version” to v2 and enable it:

STEP 3. Create the DataStream for your Property and on “Data Sets” step of the setup wizard select all possible fields and select “Log format” as JSON:

STEP 4. For the “Delivery” step of the setup wizard, select “Custom HTTPS” method and configure it as follows:

Endpoint URL. Input your Coralogix domain to create your endpoint URL: https://ingress./akamai/v1/datastream.
Additional options.
- Select Content type as application/json.
- Change Custom header name to basic_auth.
  - Define user as you wish.
  - Input your Coralogix Send-Your-Data API key as the secret/password.

STEP 5. Deploy the new version of your stream.

Akamai Cloud Monitor

Seamlessly integrate your Akamai Cloud Monitor logs directly into our monitoring platform.

Configuration

STEP 1. Route your Cloud monitor logs to https://ingress.//akamai/v1/cloud-monitor, after inputting your Coralogix domain.

STEP 2. Define the Content Delivery Property.

Define user as you wish.
Input your Coralogix Send-Your_Data API key as basic_auth secret/password.
In Delivery Property, the origin server port must be 443 HTTPS used.

Support

Need help?

Our world-class customer success team is available 24/7 to walk you through your setup and answer any questions that may come up.

Feel free to reach out to us via our in-app chat or by sending us an email at [email protected].

Fastly Logs via HTTPS Streaming

Next Jenkins Telemetry