1.2.0

Layers

Features

The OTLP gateway layer is hidden from the sidebar by default, like the agent one. OAP 11.2.0 draws a gateway listed in its gateways.yml under OTLP_VIRTUAL_GATEWAY when the gateway’s callers and callees report OTLP traces, where it used VIRTUAL_GATEWAY. The layer has no dashboard, so layers.excluded now hides it by default, next to FAAS and VIRTUAL_GATEWAY; the gateway still shows as a node in the topology. A horizon.yaml that sets its own layers.excluded list keeps it: add OTLP_VIRTUAL_GATEWAY there to hide the layer too. See Configuration File.

The OAP layer’s alarm delivery widgets show the gRPC alarm hook. OAP 11.2.0 also counts the deliveries of its gRPC alarm hook, as the channel gRPC, so Alarm Delivery / min and Alarm Delivery Latency (ms) show it as one more line without a template change. gRPC has no HTTP status, so Alarm Delivery Responses / min now shows only once an HTTP hook has answered, and stays hidden on a node that only uses the gRPC hook. An OAP that already stores this layer’s template and translations keeps the old Responses condition and tips; to adopt them, open Dashboard setup → Layer dashboards → OAP, choose Reset to → Bundled and Check diff & push, then do the same for each language on the Translations page.

Traces, logs and events

Features

The Zipkin and TraceQL trace tabs take tags the way the native Traces tab does. The Zipkin tab’s Annotations field and the TraceQL builder’s Tag field are now the same field as the native tab’s Tag: type key=value (on Zipkin, also a bare annotation such as error), pick from the suggestion list, press Enter, and the term joins a row of removable chips under the form — Active tags, or Active annotations on Zipkin. Only the chips reach the query. On Zipkin, several terms typed at once with and become one chip each. The TraceQL builder’s key and value box pairs and the + Tag button are gone. The field comes last on both, on a row of its own with its chips under it: on Zipkin, Limit and Time range now share the duration row.

The tag field says when something you typed did not make it into the query. On the native, Zipkin and TraceQL builder trace tabs, pressing Enter on text that is not key=value (or, on Zipkin, a bare annotation) leaves it in the field and covers the field with a red note saying so, where it used to be dropped or added without a value. Clicking Run query with a tag still in the field runs without it and covers the field with a note for five seconds: press Enter to add it. Typing, or clicking the note, takes it away.

Fixes

The tag fields on the Traces, Logs, Trace inspect and Log inspect pages leave input-method keys to the input method. Confirming a Chinese, Japanese or Korean candidate with Enter used to add the half-composed text as a tag, and the arrow keys moved through the tag suggestions instead of the candidates.

A tag value holding a comma keeps its suggestions on the Traces and Logs tabs. Typing db.statement=SELECT a, b used to switch the suggestions back to tag keys after the comma, as if a second tag had started; the field now completes the whole text as one tag. Trace inspect and Log inspect, whose field takes a comma-separated list, are unchanged.