You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This release contains 6 new features, 1 bug fix and 10 documentation improvements.
🆕 Features
Add OpenTelemetry tracing and metrics with basic configuration (#5175)
Jina now supports OpenTelemetry Tracing and Metrics libraries for increased observability and instrumentation of Jina Runtimes. Read the docs (#5291) for details. We also provide a migration guide for a smooth transition from the previously-supported Prometheus-only based metrics instrumentation.
You can integrate Jaeger or other distributed tracing tools to collect and visualize request-level and application level service operation attributes. This helps you analyze request-response lifecycle, application behavior and performance.
Use the list sub command to list the locations of local Hub Executors:
jina hub list
Dump to Statefulset in K8s when volumes are passed to Executor (#5265)
Jina will generate a Kubernetes Statefulset manifest for Executors if you provide volumes to the Flow.to_kubernets_yaml() method. Executors can persist data on mounted volumes and correctly scale horizontally if required.
Theclient.post() method was not raising an exception if any of the underlying async requests raised an exception.
The new version correctly raises the exception raised by any async request. The user can now correctly catch any exceptions and act upon the exception.
Release Note
This release contains 6 new features, 1 bug fix and 10 documentation improvements.
🆕 Features
Add OpenTelemetry tracing and metrics with basic configuration (#5175)
Jina now supports OpenTelemetry Tracing and Metrics libraries for increased observability and instrumentation of Jina
Runtimes
. Read the docs (#5291) for details. We also provide a migration guide for a smooth transition from the previously-supported Prometheus-only based metrics instrumentation.You can integrate Jaeger or other distributed tracing tools to collect and visualize request-level and application level service operation attributes. This helps you analyze request-response lifecycle, application behavior and performance.
Record existing prometheus metrics into opentelemetry histograms (#5275)
Prometheus-only based metrics are also available as OpenTelemetry supported metrics. You can switch to OpenTelemetry metrics with little effort.
Add default tracing interceptors to head grpc connection pool (#5271)
Head
Runtime
supports default traces when forwarding requests to the shard replica.Add grpc metadata to executors and gateway deployments (#5221)
You can now provide HTTP header access tokens as client metadata for accessing external and authentication protected services.
Show local location of Executors in Hub (#5282)
Use the
list
sub command to list the locations of local Hub Executors:Dump to Statefulset in K8s when volumes are passed to Executor (#5265)
Jina will generate a Kubernetes
Statefulset
manifest for Executors if you providevolumes
to theFlow.to_kubernets_yaml()
method. Executors can persist data on mounted volumes and correctly scale horizontally if required.🐞 Bug Fixes
Invalid input raise exception (#5141)
client.post()
method was not raising an exception if any of the underlying async requests raised an exception.📗 Documentation Improvements
🤟 Contributors
We would like to thank all contributors to this release:
The text was updated successfully, but these errors were encountered: