docs/en/changes/changes-9.0.0.md
-Dlog4j2.formatMsgNoLookups=true or setting
the LOG4J_FORMAT_MSG_NO_LOOKUPS=”true” environment variable also avoids CVEs../mvnw compile not work if ./mvnw install is not executed at least once.JD_PRESERVE_LINE_FEEDS=true in official code style file.Can't split endpoint id into 2 parts bug for endpoint ID. In the TCP in service mesh observability, endpoint
name doesn't exist in TCP traffic.ValueColumnMetadata.Layer and removed NodeType. More details refer
to v9-version-upgrade.GCPhrase -> GCPhase.FAAS to SpanLayer.normal to V9 service meta query.scope=ALL catalog for metrics.normal field to Service.SelfRemoteClient self observing metrics.SW_CLUSTER_INTERNAL_COM_HOST and SW_CLUSTER_INTERNAL_COM_PORT for cluster selectors zookeeper
,consul,etcd and nacos.configuration-vocabulary,backend-cluster about env variables SW_CLUSTER_INTERNAL_COM_HOST
and SW_CLUSTER_INTERNAL_COM_PORT.responseTimeout of ES client.alarm_record.tags_raw_data of binary type in ElasticSearch storage.gzip.possibility) in LAL.receiver_zipkin to receiver-zipkin, remove receiver_jaeger from application.yaml.metadataQueryBatchSize to configure scrolling page size.metadataQueryMaxSize from 5000 to 10000BasicToken.of with AuthToken.ofBasic.Health check fails. reason: No healthy endpoint.event generated metrics to SERVICE_CATALOG_NAME catalog.All from OAL source.SRC_ALL: 'All' from OAL grammar tree.all_heatmap and all_percentile metrics.receiver-otel#enabledOcRules receiver with k8s-node,oap,vm rules on default.satellite,spring-sleuth for agent-analyzer#meterAnalyzerActiveFiles on default.receiver-zabbix receiver with agent rule on default.restAcceptorPriorityDelta (env var: SW_RECEIVER_SHARING_JETTY_DELTA
, SW_CORE_REST_JETTY_DELTA).graphql/path (env var: SW_QUERY_GRAPHQL_PATH).indexOnly, support ElasticSearch only index and not store some fields.indexOnly=true to SegmentRecord.tags, AlarmRecord.tags, AbstractLogRecord.tags, to reduce unnecessary
storage.restMinThreads (env var: SW_CORE_REST_JETTY_MIN_THREADS
, SW_RECEIVER_SHARING_JETTY_MIN_THREADS).Column.shardingKeyIdx for column definition for BanyanDB.Sharding key is used to group time series data per metric of one entity in one place (same sharding and/or same
row for column-oriented database).
For example,
ServiceA's traffic gauge, service call per minute, includes following timestamp values, then it should be sharded by service ID
[ServiceA(encoded ID): 01-28 18:30 values-1, 01-28 18:31 values-2, 01-28 18:32 values-3, 01-28 18:32 values-4]
BanyanDB is the 1st storage implementation supporting this. It would make continuous time series metrics stored closely and compressed better.
NOTICE, this sharding concept is NOT just for splitting data into different database instances or physical files.
properties parameters and _source update.isNotNormal service requirement when use alias to merge service topology from client side. All RPCs' peer
services from client side are always normal services. This cause the topology is not merged correctly.EventType.TOTAL always.Aggregation and GC Count metrics for oap self observabilitymultiGet could query without tag value in the InfluxDB storage plugin.DatabaseSlowStatement.Error Prone Annotations dependency to suppress warnings, which are not errors.SW_ENABLE_UPDATE_UI_TEMPLATE to control user edit UI template.All source relative document and examples.k8s-monitoring, backend-telemetry and v9-version-upgrade doc for v9.All issues and pull requests are here