2.6 KiB
2.6 KiB
9.5.0
Project
- Fix
Duplicate class founddue to thedelombokgoal.
OAP Server
- Fix wrong layer of metric
user errorin DynamoDB monitoring. - ElasticSearch storage does not check field types when OAP running in
no-initmode. - Support to bind TLS status as a part of component for service topology.
- Fix component ID priority bug.
- Fix component ID of topology overlap due to storage layer bugs.
- [Breaking Change] Enhance JDBC storage through merging tables and managing day-based table rolling.
- [Breaking Change] Sharding-MySQL implementations and tests get removed due to we have the day-based rolling mechanism by default
- Fix otel k8s-cluster rule add namespace dimension for MAL aggregation calculation(Deployment Status,Deployment Spec Replicas)
- Support continuous profiling feature.
- Support collect process level related metrics.
- Fix K8sRetag reads the wrong k8s service from the cache due to a possible namespace mismatch.
- [Breaking Change] Support cross-thread trace profiling. The data structure and query APIs are changed.
- Fix PromQL HTTP API
/api/v1/labelsresponse missingservicelabel. - Fix possible NPE when initialize
IntList. - Support parse PromQL expression has empty labels in the braces for metadata query.
- Support alarm metric OP
!=. - Support metrics query indicates whether value == 0 represents actually zero or no data.
- Fix
NPEwhen query the not exist series indexes in ElasticSearch storage. - Support collecting memory buff/cache metrics in VM monitoring.
- PromQL: Remove empty values from the query result, fix
/api/v1/metadataparamlimitcould cause out of bound. - Support monitoring the total number metrics of k8s StatefulSet and DaemonSet.
- Support Amazon API Gateway monitoring.
- Bump up graphql-java to fix cve.
- Bump up Kubernetes Java client.
UI
- Revert: cpm5d function. This feature is cancelled from backend.
- Fix: alerting link breaks on the topology.
- Refactor Topology widget to make it more hierarchical.
- Choose
Useras the first node. - If
Usernode is absent, choose the busiest node(which has the most calls of all). - Do a left-to-right flow process.
- At the same level, list nodes from top to bottom in alphabetical order.
- Choose
- Fix filter ID when ReadRecords metric associates with trace.
- Add AWS API Gateway menu.
- Change trace profiling protocol.
- Add Redis menu.
Documentation
- Add Profiling related documentations.
- Add
SUM_PER_MINto MAL documentation.
All issues and pull requests are here