📘

LogDNA is now Mezmo

LogDNA has recently become Mezmo. As you access technical resources like our API, Code Libraries, and GitHub repositories, you will continue to see references to LogDNA for a short time as we update our new name across all our resource channels.

Follow the Cloud Monitor Implementation Guide to configure Akamai Cloud Monitor to forward logs to Mezmo. Use the parameters listed here to set the configuration options.

Cloud Monitor Data Delivery

Dynamic Site Accelerator

In your Dynamic Site Accelerator configuration, set the Cloud Monitor Instrumentation behavior with the these parameters:

📘

Optional Querystring Parameters

Use querystring parameters to override hostname, app, or to add tags:

/akamai/ingest/<Ingestion Key>?hostname=newHost&app=newTest;
/akamai/ingest/<Ingestion Key>?tags=akamai,logdna&app=newTest;
/akamai/ingest/<Ingestion Key>?tags=tag1&hostname=host1, etc.

How Akamai Logs are Parsed

You can find information for each of your datasets in these log entries:

The information about each dataset and the definition of each field can be found in Appendix A: Cloud Monitor Default Connectors section of Cloud Monitor Implementation Guide.

Unless specified, hostname is always http.reqPath and app is always AkamaiCloudMonitor.

The log line is formatted using some http.* fields as in this example:
cliIP reqMethod reqPath?reqQuery proto/protoVer status bytes reqCT reqLen respCT respLen UA

Notes:

• - is used if the optional field is missing;
• Just reqPath is used if there is no reqQuery;
• In order to format the line, the fields are joined together using whitespace delimiter in this order:
  • http.cliIP;
  • http.reqMethod;
  • http.reqPath?http.reqQuery or just http.reqPath;
  • http.proto/http.protoVer;
  • http.status;
  • http.bytes;
  • http.reqCT;
  • http.reqLen;
  • http.respCT;
  • http.respLen;
  • http.UA.