Trace Storage is a storage option for Zipkin distributed traces on your account. It functions as both a collector and a span store.

This integration requires API access. The API is available for Pro and Enterprise accounts.


When you use the Zipkin UI to find traces stored in, there are a couple limitations. For most users, these won’t be an issue, but they’re still good to know:

  • Lookback must be 2 days or less
  • Limit must be 1000 traces or less

To integrate Zipkin server and

Download Zipkin server and Trace Storage

Download Zipkin server.

curl -sSL | bash -s

Download the latest Trace Storage jar to the same directory.

curl -sSL > logzio.jar
Run Zipkin server with the extension

You can configure the extension with shell variables or environment variables.

For a complete list of options, see the parameters below the code block.👇

java -Dloader.path='zipkin-logzio.jar,zipkin-logzio.jar!lib' -cp zipkin.jar org.springframework.boot.loader.PropertiesLauncher

You can optionally run two discrete Zipkin-Logzio Trace Storage instances if you want to separate shipping and reading of your traces.

If you do, then the required fields change a bit from what’s shown in the Parameters list:
• The shipping instance uses STORAGE_TYPE=logzio, LOGZIO_ACCOUNT_TOKEN, and LOGZIO_LISTENER_HOST.
• The reading instance uses STORAGE_TYPE=logzio, LOGZIO_API_TOKEN, and LOGZIO_API_HOST.

Parameter Description
STORAGE_TYPE=logzio (Required) We wish there was a way to include this as a default. Alas, Zipkin requires it, so you’ll need to include this bit.
LOGZIO_ACCOUNT_TOKEN (Required) Required when using as a collector to ship logs to Replace <<LOG-SHIPPING-TOKEN>> with the token of the account you want to ship to.
LOGZIO_API_TOKEN (Required) Required to read back traces from
Replace <<API-TOKEN>> with an API token from the account you want to use.
LOGZIO_LISTENER_HOST Replace <<LISTENER-HOST>> with the host for your region. For example, if your account is hosted on AWS US East, or if hosted on Azure West Europe.
LOGZIO_API_HOST Required to read back spans from
Replace <<API-URL>> with your region’s base API URL. For more information on finding your account’s region, see Account region.
STRICT_TRACE_ID true Use false if your version of Zipkin server generates 64-bit trace IDs (version 1.14 or lower). If false, spans are grouped by the rightmost 16 characters of the trace ID. For version 1.15 or later, we recommend leaving the default.
SENDER_DRAIN_INTERVAL 5 Time interval, in seconds, to send the traces accumulated on the disk.
CLEAN_SENT_TRACES_INTERVAL 30 Time interval, in seconds, to clean sent traces from the disk.
Check for your traces

Give your traces some time to get from your system to ours, and then open your Zipkin UI.