Access Log Service Stats

gm-control can be configured to parse Envoy access logs and send them to a number of stats backends, including:

For every request, both upstream and downstream, gm-control will send to each configured stats backend:

  • the upstream request and upstream response, including:

    • timestamp

    • zone

    • proxy name (of the proxy the request was sent to)

    • proxy version

    • node name

    • HTTP method

    • domain

    • route key

    • rule

    • shared rule

    • header constraint

    • upstream cluster (that the request will be sent to)

    • instance of gm-control

    • response code (for responses)

  • the upstream latency, including all previously listed information

  • the request event, if the stats backend supports it

For example, below is a screenshot of all upstream requests in the prometheus dashboard:

prom_dashboard

Example Configuration

Setting:

will set up a Prometheus client on localhost:9102 that Prometheus can be configured to scrape from.

Log Access Logs

Additionally, gm-control can be configured to log access logs to stdout before they are processed by the ALS. To enable, set

The resulting logs (in gm-control) will look like this:

See the Envoy docsarrow-up-right for more information on the log format.

Configuration Options

See the gm-control command optionsarrow-up-right for full configuration options.

Last updated

Was this helpful?