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 all Enterprise accounts. If you’re on a Pro account, reach out to your account manager or the Sales team to request API access.


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

  1. 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
  2. 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.👇

    STORAGE_TYPE=logzio \
    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.


    We wish there was a way to include this as a default. Alas, Zipkin needs it, so you’ll need to include this bit.
    Required when using as a collector to ship logs to
    Replace <<SHIPPING-TOKEN>> with the token of the account you want to ship to.
    Required to read back traces from
    Replace <<API-TOKEN>> with an API token from the account you want to use.
    Replace <<LISTENER-HOST>> with your region’s listener host (for example, For more information on finding your account’s region, see Account region.
    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.
    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.
    Time interval, in seconds, to send the traces accumulated on the disk.
    Time interval, in seconds, to clean sent traces from the disk.
  3. Check for your traces

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

    If you still don’t see your logs, see log shipping troubleshooting.