docs/en/changes/changes-9.2.0.md
SW_STORAGE_ES_FLUSH_INTERVAL) since 8.8.0 -
9.1.0 releases.VIRTUAL detect type to Process for Network Profiling.LocalSpan in the trace.forEach, processRelation function to MAL expression.expPrefix, initExp in MAL config.percentile functions, p99, p95, p90, p75, p50 func(s)._mGet and physical index name rather than alias in these
scenarios, (a) Metrics aggregation (b) Zipkin query (c) Metrics query (d) Log queryNETWORK type of eBPF Profiling task.sumHistogram in MAL.ebpf_profiling_task is required to be re-created when bump up from previous releases.SUM_PER_MIN downsampling in MAL.sumHistogramPercentile in MAL.VIRTUAL_CACHE to Layer, to fix conjectured Redis server, which icon can't show on the topology.metrics-all and records-all on the default setting.
Provide system environment variable(SW_STORAGE_ES_LOGIC_SHARDING) to shard metrics/meter indices into
multi-physical indices as the previous versions(one index template per metric/meter aggregation function).
In the current one index mode, users still could choose to adjust ElasticSearch's shard
number(SW_STORAGE_ES_INDEX_SHARDS_NUMBER) to scale out.
More details please refer to New ElasticSearch storage option explanation in 9.2.0
and backend-storage.mdebpf_profiling_schedule added a new column ebpf_profiling_schedule_id,
the H2/Mysql/Tidb/Postgres storage users are required to re-created it when bump up from previous releases.tls and https component IDs for Network Profiling.SW_STORAGE_ES_QUERY_MAX_SIZE > 10000.otel-oc-rules to otel-rules.enabledOcRules to enabledOtelRules and
environment variable name from SW_OTEL_RECEIVER_ENABLED_OC_RULES to SW_OTEL_RECEIVER_ENABLED_OTEL_RULES.segment,segment_tag, logs, logs_tag, alarms, alarms_tag, zipkin_span, zipkin_query before OAP starts.@SQLDatabase.ExtraColumn4AdditionalEntity to support add an extra column from parent to an additional table.event menu.FaaS-Root document link and topology service relation dashboard link.Mesh-Instance metric Throughput.Mesh-Service-Relation metric Throughput
and Proxy Sidecar Internal Latency in Nanoseconds (Client Response).Mesh-Instance-Relation metric Throughput.All issues and pull requests are here