All Versions
30
Latest Version
Avg Release Cycle
32 days
Latest Release
31 days ago

Changelog History
Page 1

  • v1.15.1

    November 07, 2019
    🐛 Bug fixes, Minor Improvements

  • v1.15.0

    November 07, 2019

    Backend Changes

    💥 Breaking Changes

    0️⃣ The default value for the Ingester's flag ingester.deadlockInterval has been changed to 0 (#1868, @jpkrohling)

    ⏪ With the new default, the ingester won't panic if there are no messages for the last minute. To restore the previous behavior, set the flag's value to 1m.

    🗄 Mark --collector.grpc.tls.client.ca flag as deprecated for jaeger-collector. (#1840, @yurishkuro)

    🚚 The deprecated flag will still work, but will be removed removed in the future, it's recommended to use --collector.grpc.tls.client-ca instead.

    🆕 New Features
    🐛 Bug fixes, Minor Improvements

    💻 UI Changes

    • 💻 The changelog is available here v1.5.0

  • v1.14.0

    September 02, 2019

    Backend Changes

    💥 Breaking Changes

    Create ES index templates instead of indices (#1627, @pavolloffay)

    🚀 This can break existing Elasticsearch deployments if security policies are applied.
    For instance Jaeger X-Pack configuration now requires permission to create index templates - manage_index_templates.

    🆕 New Features

    ➕ Add Elasticsearch version configuration to rollover script (#1769, @pavolloffay)

    ➕ Add Elasticsearch version flag (#1753, @pavolloffay)

    ➕ Add Elasticsearch 7 support (#1690, @gregoryfranklin)

    The index mappings in Elasticsearch 7 are not backwards compatible with the older versions.
    Therefore using Elasticsearch 7 with data created with older version would not work.
    ⬆️ Elasticsearch 6.8 supports 7.x, 6.x, 5.x compatible mappings. The upgrade has to be done
    🚚 first to ES 6.8, then apply data migration or wait until old daily indices are removed (this requires
    to start Jaeger with --es.version=7 to force using ES 7.x mappings for newly created indices).

    0️⃣ Jaeger by default uses Elasticsearch ping endpoint (/) to derive the version which is used
    for index mappings selection. The version can be overridden by flag --es.version.

    👌 Support for Zipkin Protobuf spans over HTTP (#1695, @jan25)

    ➕ Added support for hot reload of UI config (#1688, @jpkrohling)

    ➕ Added base Grafana dashboard and Alert rules (#1745, @jpkrohling)

    ➕ Add the jaeger-mixin for monitoring (#1668, @gouthamve)

    ➕ Added flags for driving cassandra connection compression through config (#1675, @sagaranand015)

    👌 Support index cleaner for rollover indices and add integration tests (#1689, @pavolloffay)

    ➕ Add client TLS auth to gRPC reporter (#1591, @tcolgate)

    Collector kafka producer protocol version config (#1658, @marqc)

    🔧 Configurable kafka protocol version for msg consuming by jaeger ingester (#1640, @marqc)

    🏗 Use credentials when describing keyspaces in cassandra schema builder (#1655, @MiLk)

    ➕ Add connect-timeout for Cassandra (#1647, @sagaranand015)

    🐛 Bug fixes, Minor Improvements

    💻 UI Changes

    • 📌 UI pinned to version 1.4.0. The changelog is available here v1.4.0

  • v1.13.1

    June 28, 2019

    Backend Changes

    💥 Breaking Changes
    🆕 New Features
    🐛 Bug fixes, Minor Improvements
    • 🔄 Change default for bearer-token-propagation to false (#1642, @wsoula)

    💻 UI Changes

  • v1.13.0

    June 27, 2019

    Backend Changes

    💥 Breaking Changes
    • The traces related metrics on collector now have a new tag sampler_type (#1576, @guanw)

    This might break some existing metrics dashboard (if so, users need to update query to aggregate over this new tag).

    The list of metrics affected: traces.received, traces.rejected, traces.saved-by-svc.

    In Jaeger 1.9.0 release the Elasticsearch index separator was changed from : to -. To keep backwards compatibility the query service kept querying indices with : separator, however the new indices were created only with -. This release of Jaeger removes the query capability for indices containing :, therefore it's recommended to keep using older version until indices containing old separator are not queried anymore.

    🆕 New Features
    🐛 Bug fixes, Minor Improvements

    💻 UI Changes

    • 📌 UI pinned to version 1.3.0. The changelog is available here v1.3.0

  • v1.12.0

    May 16, 2019

    Backend Changes

    💥 Breaking Changes

    • 🚚 The kafka flags were removed in favor of kafka.producer and kafka.consumer flags (#1424, @ledor473)

      The following flags have been removed in the Collector and the Ingester:

      --kafka.brokers
--kafka.encoding
--kafka.topic
--ingester.brokers
--ingester.encoding
--ingester.topic
--ingester.group-id

      In the Collector, they are replaced by:

      --kafka.producer.brokers
--kafka.producer.encoding
--kafka.producer.topic

      In the Ingester, they are replaced by:

      --kafka.consumer.brokers
--kafka.consumer.encoding
--kafka.consumer.topic
--kafka.consumer.group-id

    • ➕ Add Admin port and group all ports in one file (#1442, @yurishkuro)

      This change fixes issues #1428, #1332 and moves all metrics endpoints from API ports to admin ports. It requires re-configuring Prometheus scraping rules. Each Jaeger binary has its own admin port that can be found under --admin-http-port command line flag by running the ${binary} help command.

    🆕 New Features
    🐛 Bug fixes, Minor Improvements

    💻 UI Changes

    • 📌 UI pinned to version 1.2.0. The changelog is available here v1.2.0

  • v1.11.0

    March 07, 2019

    Backend Changes

    💥 Breaking Changes

    • Introduce kafka.producer and kafka.consumer flags to replace kafka flags (#1360, @ledor473)

      The following flags have been deprecated in the Collector and the Ingester:

      --kafka.brokers
--kafka.encoding
--kafka.topic

      In the Collector, they are replaced by:

      --kafka.producer.brokers
--kafka.producer.encoding
--kafka.producer.topic

      In the Ingester, they are replaced by:

      --kafka.consumer.brokers
--kafka.consumer.encoding
--kafka.consumer.group-id
      🆕 New Features

    • 👌 Support secure gRPC channel between agent and collector (#1391, @ghouscht, @yurishkuro)

    • 👍 Allow to use TLS with ES basic auth (#1388, @pavolloffay)

    🐛 Bug fixes, Minor Improvements

    💻 UI Changes

    • 📌 UI pinned to version 1.1.0. The changelog is available here v1.1.0

  • v1.10.1

    February 21, 2019

    Backend Changes

    💥 Breaking Changes
    🆕 New Features
    🐛 Bug fixes, Minor Improvements
    • Separate query-service functionality from http handler (#1312, @annanay25)

    💻 UI Changes

  • v1.10.0

    February 15, 2019

    Backend Changes

    💥 Breaking Changes

    Migration Path:

    1. Run plugin/storage/cassandra/schema/migration/v001tov002part1.sh which will copy dependencies into a csv, update the dependency UDT, create a new dependencies_v2 table, and write dependencies from the csv into the dependencies_v2 table.
    2. Run the collector and query services with the cassandra flag cassandra.enable-dependencies-v2=true which will instruct jaeger to write and read to and from the new dependencies_v2 table. ⚡️ 3. Update spark job to write to the new dependencies_v2 table. The feature will be done in #58. 🔌 4. Run plugin/storage/cassandra/schema/migration/v001tov002part2.sh which will DELETE the old dependency table and the SASI index.

    🚚 Users who wish to continue to use the v1 table don't have to do anything as the cassandra flag cassandra.enable-dependencies-v2 will default to false. Users may migrate on their own timeline however new features will be built solely on the dependencies_v2 table. In the future, we will remove support for v1 completely.

    • ✂ Remove ErrorBusy metric, it essentially duplicates SpansDropped (#1091, @cstyan)

    🆕 New Features

    🐛 Bug fixes, Minor Improvements

    • 👉 Use Zipkin annotations if the timestamp is zero (#1341, @geobeau)
    • 👉 Use GRPC round robin balancing even if only one hostname (#1329, @benley)
    • Tolerate whitespaces in ES servers and kafka brokers (#1305, @verma-varsha)
    • Let cassandra servers contain whitespace in config (#1301, @karlpokus)

    💻 UI Changes

  • v1.9.0

    January 21, 2019

    Backend Changes

    💥 Breaking Changes

    🔄 Changed index prefix separator from : to - because Elasticsearch 7 does not allow : in index name.
    🔧 Jaeger query still reads from old indices containing - as a separator, therefore no configuration or migration changes are required.

    • ➕ Add CLI configurable es.max-num-spans while retrieving spans from ES (#1283, @annanay25)

    0️⃣ The default value is set to 10000. Before no limit was applied.

    • ♻️ Update to jaeger-lib 2 and latest sha for jaeger-client-go, to pick up refactored metric names (#1282, @objectiser)

    ⚡️ Update to latest version of jaeger-lib, which includes a change to the naming of counters exported to
    prometheus, to follow the convention of using a _total suffix, e.g. jaeger_query_requests is now
    jaeger_query_requests_total.

    Jaeger go client metrics, previously under the namespace jaeger_client_jaeger_ are now under
    jaeger_tracer_.

    The following metrics:

    jaeger_agent_tchannel_reporter_batch_size{format="jaeger"} 0
jaeger_agent_tchannel_reporter_batch_size{format="zipkin"} 0
jaeger_agent_tchannel_reporter_batches_failures{format="jaeger"} 0
jaeger_agent_tchannel_reporter_batches_failures{format="zipkin"} 0
jaeger_agent_tchannel_reporter_batches_submitted{format="jaeger"} 0
jaeger_agent_tchannel_reporter_batches_submitted{format="zipkin"} 0
jaeger_agent_tchannel_reporter_spans_failures{format="jaeger"} 0
jaeger_agent_tchannel_reporter_spans_failures{format="zipkin"} 0
jaeger_agent_tchannel_reporter_spans_submitted{format="jaeger"} 0
jaeger_agent_tchannel_reporter_spans_submitted{format="zipkin"} 0

jaeger_agent_collector_proxy{endpoint="baggage",result="err"} 0
jaeger_agent_collector_proxy{endpoint="baggage",result="ok"} 0
jaeger_agent_collector_proxy{endpoint="sampling",result="err"} 0
jaeger_agent_collector_proxy{endpoint="sampling",result="ok"} 0

    have been renamed to:

    jaeger_agent_reporter_batch_size{format="jaeger",protocol="tchannel"} 0
jaeger_agent_reporter_batch_size{format="zipkin",protocol="tchannel"} 0
jaeger_agent_reporter_batches_failures{format="jaeger",protocol="tchannel"} 0
jaeger_agent_reporter_batches_failures{format="zipkin",protocol="tchannel"} 0
jaeger_agent_reporter_batches_submitted{format="jaeger",protocol="tchannel"} 0
jaeger_agent_reporter_batches_submitted{format="zipkin",protocol="tchannel"} 0
jaeger_agent_reporter_spans_failures{format="jaeger",protocol="tchannel"} 0
jaeger_agent_reporter_spans_failures{format="zipkin",protocol="tchannel"} 0
jaeger_agent_reporter_spans_submitted{format="jaeger",protocol="tchannel"} 0
jaeger_agent_reporter_spans_submitted{format="zipkin",protocol="tchannel"} 0

jaeger_agent_collector_proxy{endpoint="baggage",protocol="tchannel",result="err"} 0
jaeger_agent_collector_proxy{endpoint="baggage",protocol="tchannel",result="ok"} 0
jaeger_agent_collector_proxy{endpoint="sampling",protocol="tchannel",result="err"} 0
jaeger_agent_collector_proxy{endpoint="sampling",protocol="tchannel",result="ok"} 0

    The following metric:

    jaeger_http_server_errors{source="tcollector-proxy",status="5xx"}

    has been renamed to:

    jaeger_http_server_errors{source="collector-proxy",status="5xx"}

    🆕 New Features

    🐛 Bug fixes, Minor Improvements

    • ⚡️ Update exposed ports in ingester dockerfile (#1289, @objectiser)
    • ⬆️ Upgrade Shopify/Sarama for proper handling newest kafka servers 2.x by ingester (#1248, @vprithvi)
    • 🛠 Fix sampling strategies overwriting service entry when no sampling type is specified (#1244, @objectiser)
    • 🛠 Fix dot replacement for int (#1272, @pavolloffay)
    • ➕ Add C* query to error logs (#1250, @vprithvi)
    • ➕ Add locking around partitionIDToState map accesses (#1239, @vprithvi)
    • 📦 Reorganize config manager packages in agent (#1198, @pavolloffay)

    💻 UI Changes

    • 📌 UI pinned to version 1.0.0. The changelog is available here v1.0.0