Changelog History
Page 2
-
v1.16.0 Changes
December 17, 2019Backend Changes
๐ฅ Breaking Changes
List of service operations can be classified by span kinds (#1943, #1942, #1937, @guo0693)
- Endpoint changes:
- Both Http & gRPC servers now take new optional parameter
spanKind
in addition toservice
. When spanKind is absent or empty, operations from all kinds of spans will be returned. - Instead of returning a list of string, both Http & gRPC servers return a list of operation struct. Please
update your client code to process the new response. Example response:
curl 'http://localhost:6686/api/operations?service=UserService&spanKind=server' | jq { "data": [{ "name": "UserService::getExtendedUser", "spanKind": "server" }, { "name": "UserService::getUserProfile", "spanKind": "server" }], "total": 2, "limit": 0, "offset": 0, "errors": null }
- The legacy http endpoint stay untouched:
/services/{%s}/operations
- Both Http & gRPC servers now take new optional parameter
- ๐ Storage plugin changes:
- Memory updated to support spanKind on write & read, no migration is required.
- Badger & ElasticSearch
to be implemented:
For nowspanKind
will be set as empty string during read & write, onlyname
will be valid operation name. - Cassandra updated to support spanKind on write & read (#1937, @guo0693):
If you don't run the migration script, nothing will break, the system will used the old tableoperation_names
and set emptyspanKind
in the response.
Steps to get the updated functionality:- You will need to run below command on the host you can use
cqlsh
to connect the the cassandra contact pointKEYSPACE=jaeger_v1 CQL_CMD='cqlsh host 9042 -u test_user -p test_password --request-timeout=3000' bash ./v002tov003.sh
The script will create new tableoperation_names_v2
and migrate data from the old table.
spanKind
column will be empty for those data.
At the end, it will ask you whether you want to drop the old table or not. - Restart ingester & query services so that they begin to use the new table
- You will need to run below command on the host you can use
Trace and Span IDs are always padded to 32 or 16 hex characters with leading zeros (#1956, @yurishkuro)
โ Previously, Jaeger backend always rendered trace and span IDs as the shortest possible hex string, e.g. an ID with numeric value 255 would be rendered as a string
ff
. This change makes the IDs to always render as 16 or 32 ๐ป characters long hex string, e.g. the same id=255 would render as00000000000000ff
. It mostly affects how UI displays the IDs, the URLs, and the JSON returned fromjaeger-query
service.Motivation: Among randomly generated and uniformly distributed trace IDs, only 1/16th of them start with 0 followed by a significant digit, 1/256th start with two 0s, and so on in decreasing geometric progression. Therefore, trimming the leading 0s is a very modest optimization on the size of the data being transmitted or stored.
However, trimming 0s leads to ambiguities when the IDs are used as correlations with other monitoring systems, ๐ฒ such as logging, that treat the IDs as opaque strings and cannot establish the equivalence between padded and unpadded IDs. It is also incompatible with W3C Trace Context and Zipkin B3 formats, both of which include all ๐ฒ leading 0s, so an application instrumented with OpenTelemetry SDKs may be logging different trace ID strings than application instrumented with Jaeger SDKs (related issue #1657).
Overall, the change is backward compatible:
- links with non-padded IDs in the UI will still work
- data stored in Elasticsearch (where IDs are represented as strings) is still readable
However, some custom integration that rely on exact string matches of trace IDs may be broken.
๐ Change default rollover conditions to 2 days (#1963, @pavolloffay)
๐ Change default rollover conditions from 7 days to 2 days.
0๏ธโฃ Given that by default Jaeger uses daily indices and some organizations do not keep data longer than 7 days ๐ the default of 7 days seems unreasonable - it might result in a too big index and ๐ running curator would immediately remove the old index.
๐ New Features
- ๐ Support collector tags, similar to agent tags (#1854, @radekg)
- ๐ Support insecure TLS and only CA cert for Elasticsearch (#1918, @pavolloffay)
- ๐ Allow tracer config via env vars (#1919, @yurishkuro)
- ๐ Allow turning off tags/logs indexing in Cassandra (#1915, @joe-elliott)
- Blacklisting/Whitelisting tags for Cassandra indexing (#1904, @joe-elliott)
๐ Bug fixes, Minor Improvements
- ๐ Support custom basepath in HotROD (#1894, @jan25)
- ๐ Deprecate tchannel reporter flags (#1978, @objectiser)
- Do not truncate tags in Elasticsearch (#1970, @pavolloffay)
- Export SaveSpan to enable multiplexing (#1968, @albertteoh)
- ๐ Make rollover init step idempotent (#1964, @pavolloffay)
- โก๏ธ Update python urllib3 version required by curator (#1965, @pavolloffay)
- ๐ Allow changing max log level for gRPC storage plugins (#1962, @yyyogev)
- ๐ Fix the bug that operation_name table can not be init more than once (#1961, @guo0693)
- ๐ Improve migration script (#1946, @guo0693)
- ๐ Fix order of the returned results from badger backend. (#1939, @burmanm)
- โก๏ธ Update python pathlib to pathlib2 (#1930, @objectiser)
- ๐ง Use proxy env vars if they're configured (#1910, @zoidbergwill)
๐ป UI Changes
- ๐ UI pinned to version 1.6.0. The changelog is available here v1.6.0
- Endpoint changes:
-
v1.15.1 Changes
November 07, 2019๐ Bug fixes, Minor Improvements
- ๐ Build platform binaries as part of CI (#1909, @yurishkuro)
- โฌ๏ธ Upgrade and fix dependencies (#1907, @yurishkuro)
-
v1.15.0 Changes
November 07, 2019Backend Changes
๐ฅ Breaking Changes
0๏ธโฃ The default value for the Ingester's flag
ingester.deadlockInterval
has been changed to0
(#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 to1m
.๐ 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
- ๐ Support TLS for Kafka (#1414, @MichaHoffmann)
- โ Add ack and compression parameters for Kafka #1359 (#1712, @chandresh-pancholi)
- ๐ Propagate the bearer token to the gRPC plugin server (#1822, @radekg)
- โ Add Truncate and ReadOnly options for badger (#1842, @burmanm)
๐ Bug fixes, Minor Improvements
- ๐ Use correct context on ES search methods (#1850, @rubenvp8510)
- ๐ Handling of expected error codes coming from grpc storage plugins #1741 (#1814, @chandresh-pancholi)
- ๐ Fix ordering of indexScanKeys after TraceID parsing (#1809, @burmanm)
- Small memory optimizations in badger write-path (#1771, @burmanm)
- 0๏ธโฃ Set an empty value when a default env var value is missing (#1777, @jpkrohling)
- Decouple storage dependencies and bump Go to 1.13.x (#1886, @yurishkuro)
- โก๏ธ Update gopkg.in/yaml.v2 dependency to v2.2.4 (#1865, @objectiser)
- โฌ๏ธ Upgrade jaeger-client 2.19 and jaeger-lib 2.2 and prom client 1.x (#1810, @yurishkuro)
- Unpin grpc version and use serviceConfig to set the load balancer (#1786, @guanw)
๐ป UI Changes
- ๐ป The changelog is available here v1.5.0
-
v1.14.0 Changes
September 02, 2019Backend 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 JaegerX-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
- ๐ Fix gRPC over cmux and add unit tests (#1758, @yurishkuro)
- โ Add CA certificates to agent image (#1764, @yurishkuro)
- ๐ Fix badger merge-join algorithm to correctly filter indexes (#1721, @burmanm)
- ๐ Change Zipkin CORS origins and headers to comma separated list (#1556, @JonasVerhofste)
- โ Added null guards to 'Process' when processing an incoming span (#1723, @jpkrohling)
- Export expvar metrics of badger to the metricsFactory (#1704, @burmanm)
- Pass TTL as int, not as float64 (#1710, @yurishkuro)
- ๐ Use find by regex for archive index in index cleaner (#1693, @pavolloffay)
- ๐ Allow token propagation if token type is not specified (#1685, @rubenvp8510)
- ๐ Fix duplicated spans when querying Elasticsearch (#1677, @pavolloffay)
- ๐ Fix the threshold precision issue (#1665, @guanw)
- ๐ Badger filter duplicate results from a single indexSeek (#1649, @burmanm)
- ๐ Badger make default dirs work in Windows (#1653, @burmanm)
๐ป UI Changes
- ๐ UI pinned to version 1.4.0. The changelog is available here v1.4.0
-
v1.13.1 Changes
June 28, 2019 -
v1.13.0 Changes
June 27, 2019Backend Changes
๐ฅ Breaking Changes
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
.- โ Remove deprecated index prefix separator
:
from Elastic (#1620, @pavolloffay)
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
- Passthrough OAuth bearer token supplied to Query service through to ES storage (#1599, @rubenvp8510)
- ๐ Kafka kerberos authentication support for collector/ingester (#1589, @rubenvp8510)
- ๐ Allow Cassandra schema builder to use credentials (#1635, @PS-EGHornbostel)
- โ Add docs generation command (#1572, @pavolloffay)
๐ Bug fixes, Minor Improvements
- ๐ Fix data race between
Agent.Run()
andAgent.Stop()
(#1625, @tigrannajaryan) - ๐ Use json number when unmarshalling data from ES (#1618, @pavolloffay)
- ๐ Define logs as nested data type (#1622, @pavolloffay)
- ๐ Fix archive storage not querying old spans older than maxSpanAge (#1617, @pavolloffay)
- ๐ฒ Query service: fix logging errors on SIGINT (#1601, @jan25)
- ๐ Direct grpc logs to Zap logger (#1606, @yurishkuro)
- ๐ Fix sending status to health check channel in Query service (#1598, @jan25)
- โ Add tmp-volume to all-in-one image to fix badger storage (#1571, @burmanm)
- Do not fail es-cleaner if there are no jaeger indices (#1569, @pavolloffay)
- Automatically set
GOMAXPROCS
(#1560, @rubenvp8510) - โ Add CA certs to all-in-one image (#1554, @chandresh-pancholi)
๐ป UI Changes
- ๐ UI pinned to version 1.3.0. The changelog is available here v1.3.0
- โ Remove deprecated index prefix separator
-
v1.12.0 Changes
May 16, 2019Backend Changes
๐ฅ Breaking Changes
๐ The
kafka
flags were removed in favor ofkafka.producer
andkafka.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
- โ Add gRPC resolver using external discovery service (#1498, @guanw)
- ๐ gRPC storage plugin framework (#1461, @chvck)
- ๐ Supports customized kafka client id (#1507, @newly12)
- ๐ Support gRPC for query service (#1307, @annanay25)
- ๐ฆ Expose tls.InsecureSkipVerify to es.tls.* CLI flags (#1473, @stefanvassilev)
- Return info msg for
/health
endpoint (#1465, @stefanvassilev) - โ Add pprof endpoint to admin endpoint (#1375, @konradgaluszka)
- โ Add inbound transport as label to collector metrics #1446 (guanw)
- ๐ Sorted key/value store
badger
backed storage plugin (#760, @burmanm) - โ Add Admin port and group all ports in one file (#1442, @yurishkuro)
- โ Adds support for agent level tag (#1396, @annanay25)
- โ Add a Downsampling writer that drop a percentage of spans (#1353, @guanw)
๐ Bug fixes, Minor Improvements
- Sort traces in memory store to return most recent traces (#1394, @jacobmarble)
- โ Add span format tag for jaeger-collector (#1493, @guo0693)
- โฌ๏ธ Upgrade gRPC to 1.20.1 (#1492, @guanw)
- Switch from counter to a gauge for partitions held (#1485, @bobrik)
- โ Add CORS handling for Zipkin collector service (#1463, @JonasVerhofste)
- Check elasticsearch nil response (#1467, @YEXINGZHE54)
- Disable sampling in logger -
zap
(#1460, @psinghal20) - ๐ New layout for proto definitions and generated files (#1427, @annanay25)
- โฌ๏ธ Upgrade Go to 1.12.1 (#1437 ,@yurishkuro)
๐ป UI Changes
- ๐ UI pinned to version 1.2.0. The changelog is available here v1.2.0
-
v1.11.0 Changes
March 07, 2019Backend Changes
๐ฅ Breaking Changes
Introduce
kafka.producer
andkafka.consumer
flags to replacekafka
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
- ๐ Make
esRollover.py init
idempotent (#1407 and #1408, @pavolloffay) - ๐ Allow thrift reporter if grpc hosts are not provided (#1400, @pavolloffay)
- ๐ Deprecate colon in index prefix in ES dependency store (#1386, @pavolloffay)
- 0๏ธโฃ Make grpc reporter default and add retry (#1384, @pavolloffay)
- ๐ Use
CQLSH_HOST
in final call tocqlsh
(#1372, @funny-falcon)
๐ป UI Changes
- ๐ UI pinned to version 1.1.0. The changelog is available here v1.1.0
-
v1.10.1 Changes
February 21, 2019Backend Changes
- Discover dependencies table version automatically (#1364, @black-adder)
๐ฅ Breaking Changes
๐ New Features
๐ Bug fixes, Minor Improvements
- Separate query-service functionality from http handler (#1312, @annanay25)
๐ป UI Changes
-
v1.10.0 Changes
February 15, 2019Backend Changes
๐ฅ Breaking Changes
- โ Remove cassandra SASI indices (#1328, @black-adder)
Migration Path:
- Run
plugin/storage/cassandra/schema/migration/v001tov002part1.sh
which will copy dependencies into a csv, update thedependency UDT
, create a newdependencies_v2
table, and write dependencies from the csv into thedependencies_v2
table. - 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 newdependencies_v2
table. โก๏ธ 3. Update spark job to write to the newdependencies_v2
table. The feature will be done in #58. ๐ 4. Runplugin/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 thedependencies_v2
table. In the future, we will remove support for v1 completely.๐ New Features
- ๐ Support certificates in elasticsearch scripts (#1339, @pavolloffay)
- โ Add ES Rollover support to main indices (#1309, @pavolloffay)
- Load ES auth token from file (#1319, @pavolloffay)
- โ Add username/password authentication to ES index cleaner (#1318, @gregoryfranklin)
- โ Add implementation of FindTraceIDs function for Elasticsearch reader (#1280, @vlamug)
- ๐ Support archive traces for ES storage (#1197, @pavolloffay)
๐ 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