All Versions
15
Latest Version
Avg Release Cycle
23 days
Latest Release
754 days ago
Changelog History
Page 1
Changelog History
Page 1
-
v1.2.0 Changes
November 08, 2022- ➕ Added ability to filter spans using facets.
- ➕ Added ability to select multiple systems.
- ➕ Added 2 quick filters by
deployment.environment
andservice.name
attributes on the Overview page. - ➕ Added support for creating metrics from spans so they can be monitored like usual metrics, for example:
-
v1.1.0 Changes
October 01, 2022➕ Added additional ways to authenticate users via Keycloak, Google Cloud, and Cloudflare. Contributed by @aramperes.
➕ Added gauges support to Metrics UI. Only used in Redis Enterprise [example](example/redis-enterprise) for now.
🚚 Renamed Logs tab to Events and moved all events there.
➕ Added support for PostgreSQL database instead of SQLite. This requires resetting SQLite database with:
uptrace db reset
- ⚡️ [Docker example](example/docker) is updated to work on Windows.
- ➕ Added [Redis Enterprise](example/redis-enterprise) example and metrics dashboards.
-
v1.0.2 Changes
September 08, 2022- 📇 Rename
alertmanager
YAML section toalertmanager_client
so users don't get confused.
- 📇 Rename
-
v1.0.0 Changes
September 06, 2022➕ Added
- Accept and store OpenTelemetry Metrics in ClickHouse.
- ➕ Added metrics monitoring using alerting rules.
- ➕ Added ability to send notifications via email/Slack/PagerDuty using AlertManager.
- ➕ Added ability to configure TLS.
- Expand env vars in the YAML config, for example:
ch: dsn: 'clickhouse://${CLICKHOUSE_USER}:@${CLICKHOUSE_HOST}:${CLICKHOUSE_PORT}/${CLICKHOUSE_DB}?sslmode=disable'
⬆️ Upgrading
⬆️ To upgrade, grab the latest uptrace.yml config, reset ClickHouse database, and restart Uptrace:
uptrace ch reset sudo systemctl restart uptrace
-
v0.2.15 Changes
June 08, 2022💡 Enhancements 💡
- ➕ Added support for accepting Zipkin spans at
http://uptrace:14318/api/v2/spans
. - ➕ Added support for accepting Vector logs. See the [example](example/vector-logs).
- Uptrace can be integrated to work together with Grafana Loki or cLoki docs
- Uptrace can be used as a Tempo data source in Grafana docs
- ➕ Added "Slowest groups" to the Overview tab
- ➕ Added new config option
ch_schema.compression
. You can now set ClickHouse compression via Uptrace config. - ➕ Added new config option
ch_schema.replicated
if you want to use ClickHouse replication. - 📇 Renamed the config option
retention.ttl
toch_schema.ttl
. - ➕ Added new config option
spans.buffer_size
. - ➕ Added new config option
spans.batch_size
.
- ➕ Added support for accepting Zipkin spans at
-
v0.2.14 Changes
April 19, 2022- 🛠 Fix incorrect
ORDER BY
when focusing on spans. - 📜 Parse HTTP user agent into smaller parts.
- Always show
service.name
attribute when viewing traces.
- 🛠 Fix incorrect
-
v0.2.13 Changes
April 07, 2022- 🛠 Fix incorrect
ORDER BY
when viewing spans. - 👌 Improve config file auto-discovery.
- ⚡️ Update msgpack library.
- 🛠 Fix incorrect
-
v0.2.12 Changes
March 30, 2022- Automatically run ClickHouse migrations when Uptrace is started.
- ➕ Added 15 and 30 minutes periods.
-
v0.2.11 Changes
March 29, 2022- ➕ Added ability to filter spans by clicking on a chip.
- ➕ Added explore menu for each span attribute.
- 👍 Better handle situations when
service.name
orhost.name
attributes are not available. - 👌 Support ZSTD and snappy decompression in OTLP.
-
v0.2.8 Changes
March 15, 2022- 🛠 Fixed duration filter.
- ➕ Added chart resizing when window size is changed.
- ➕ Added GRPC metrics stub to remove errors from logs.