Akamai Cloud Monitor Log Parsing

The information from each selected dataset is going to show up in different nested fields as explained below:

  • Base Log Line Data: meta.*;
  • Geographic Data: geo.*;
  • HTTP 1.0 and Message Exchange Data: http.*;
  • Network Data 1.0: network.*;
  • Network Performance Data: netPerf.*;
  • Request Header Data: reqHdr.*;
  • Response Header Data: respHdr.*;
  • Web Application Firewall Data 2.0: waf_2.*.

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. Tags, hostname and app can be customized using querystring parameters in the configuration step.

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


  • - 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 the following 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.

Updated about a year ago

Akamai Cloud Monitor Log Parsing

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.