feat(dsl): the meter-analyzer-config catalog, and stored-log content search

[wu-sheng]

Why

Two capabilities the backend has and Horizon did not reach.

Agent-reported meter rules. OAP c59f7b4 (apache/skywalking#13969) brought meter-analyzer-config to parity with otel-rules: its rules load through the same pipeline, hot-update, and attach to a DSL debug session. Horizon's catalog list was three names, hardcoded in the debugger, the router, the sidebar and the BFF's attribution index — so the rule set analysing every agent's self-observability meters, the language runtimes, connection and thread pools was invisible.

Stored-log content search. The BFF already accepted keywordsOfContent and forwarded it to OAP; the Logs tab hardwired it to []. The comment justifying that named the stock H2 store, but the protocol answers the question directly — supportQueryLogsByKeywords, computed by the storage — and Horizon never asked. booster-ui does, and shows the field accordingly.

What

meter-analyzer-config is now a catalog like the others: a MAL · Meter page under DSL management with the same browse / edit / override / inactivate / revert flow, its rules in the live debugger's MAL picker, and Inspect attributing metrics to their rule file as MAL·Meter.

The catalog list is static, so the menu entry is always present. An OAP that doesn't know the catalog answers with its own reason, and the page now shows it — 400 invalid_catalog — catalog must be one of [lal, telegraf-rules, otel-rules, log-mal-rules] instead of a bare "could not load", which is the difference between "my backend is too old" and "the request failed". Everything around it degrades rather than breaking: the debugger's picker keeps offering the three catalogs that resolve, and Inspect's attribution fan-out drops the one that 400s. Verified by running this build against the previous pin.

The Logs tab gains a Content field — space-separated words the line must contain, AND-joined — that appears only on a storage backend that can answer it. On one that can't, the field is absent rather than disabled: OAP accepts the condition there and returns the unfiltered stream, so a search box would answer every query with "everything matched". The capability is read once per OAP and cached with the existing probe; asking is guarded by schema introspection so an older backend never sees an unknown field.

The fixture turns the Java agent's meter sender on (SW_METER_ACTIVE), which is what gives core a live MAL rule to sample. Three rule files in that catalog have a producer there — java-agent, plus HikariCP's datasource and Tomcat's thread_pool.

Validation

Cases run locally against the final tree: core 10/10, es 3/3, deployment 4/4. core and es both share the modified fixture, so both were re-run.

New e2e, each on the deployment that can prove it:

• core — a MAL capture on meter-analyzer-config/java-agent through to the metric its output step materialised and a service=e2e-service-(provider|consumer) label off the opened sample group; and the Logs tab asserted to have no Content field on BanyanDB.
• es — the Content field present, a needle no line carries emptying the stream, and clearing it bringing the rows back. A backend ignoring the condition returns the same page and cannot pass this.
• a readiness check ahead of the browser proving MAL actually ran, so the project never opens a persistence cycle early.

Hand-checked in a browser against both the fixture and the public demo (which runs this exact OAP commit): the menu entry, 11 of 11 loaded rule files on the page and in the picker, a real capture, and honest degradation with the meter stream off — rules still browsable, session still installs, capture ends in "no MAL records from this node".

Preflight: type-check (6 packages), both builds, lint, unit tests (99 + 758 + 440, including 5 new for the capability probe), license 0 invalid, i18n complete across all 8 locales, bundled-template catalogs validated.

Note for review

specs/deployment/mal-debug.spec.ts is kept, with its header corrected — core now covers the same debugger path with value assertions, so whether that presence-only run still earns its place on the slowest stack is worth a second opinion.

[Copilot]

Pull request overview

Adds Horizon support for OAP’s meter-analyzer-config catalog and storage-aware stored-log content search, aligned with apache/skywalking#13969.

Changes:

• Integrates agent meter rules across DSL management, live debugging, Inspect, routing, and permissions.
• Probes OAP storage capability and conditionally exposes log-content filtering.
• Adds documentation, translations, unit tests, and backend-specific E2E coverage.

Reviewed changes

Copilot reviewed 43 out of 43 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
test/e2e/script/env	Pins the supporting OAP commit.
test/e2e/script/docker-compose/base-compose.yml	Enables Java agent meter reporting.
test/e2e/playwright/specs/ui/signals.spec.ts	Verifies BanyanDB hides content search.
test/e2e/playwright/specs/ui/dsl-debug.spec.ts	Tests agent-meter MAL capture.
test/e2e/playwright/specs/es/log-content-search.spec.ts	Tests Elasticsearch content filtering.
test/e2e/playwright/specs/deployment/mal-debug.spec.ts	Updates collector-path coverage context.
test/e2e/cases/core/expected/has-agent-meter.yml	Adds meter-readiness expectation.
test/e2e/cases/core/e2e.yaml	Waits for analyzed agent meter data.
README.md	Lists MAL Meter attribution support.
packages/api-client/src/types.ts	Registers the new catalog.
packages/api-client/src/types.test.ts	Verifies catalog membership.
packages/api-client/src/oap-info.ts	Adds log-keyword capability typing.
packages/api-client/src/dsl-debugging.ts	Enables the catalog for debugging.
packages/api-client/src/dsl-debugging.test.ts	Verifies debugging vocabulary.
docs/operate/runtime-rules.md	Documents the new runtime-rule catalog.
docs/operate/logs.md	Documents conditional content search.
docs/operate/live-debugger.md	Documents meter-rule debugging.
docs/operate/inspect.md	Documents MAL Meter attribution.
docs/changelog/1.0.0.md	Records both operator-facing features.
apps/ui/src/shell/useSidebarMenu.ts	Adds the MAL Meter menu entry.
apps/ui/src/shell/useOapInfo.ts	Exposes the capability to views.
apps/ui/src/shell/router/index.ts	Routes the new catalog page.
apps/ui/src/layer/logs/LayerLogsView.vue	Adds capability-gated content input.
apps/ui/src/i18n/locales/zh-CN.json	Adds Chinese strings.
apps/ui/src/i18n/locales/pt.json	Adds Portuguese strings.
apps/ui/src/i18n/locales/ko.json	Adds Korean strings.
apps/ui/src/i18n/locales/ja.json	Adds Japanese strings.
apps/ui/src/i18n/locales/fr.json	Adds French strings.
apps/ui/src/i18n/locales/es.json	Adds Spanish strings.
apps/ui/src/i18n/locales/en.json	Adds source English strings.
apps/ui/src/i18n/locales/de.json	Adds German strings.
apps/ui/src/features/operate/live-debug/DebugMal.vue	Loads meter rules into the MAL picker.
apps/ui/src/features/operate/inspect/inspectTypes.ts	Defines the MAL Meter source.
apps/ui/src/features/operate/inspect/InspectCatalogDrawer.vue	Displays and filters MAL Meter rules.
apps/ui/src/features/operate/dsl/DslCatalogView.vue	Surfaces detailed OAP catalog errors.
apps/ui/src/features/operate/dsl/catalog-labels.ts	Adds the catalog display label.
apps/ui/src/features/admin/roles/RolesView.vue	Includes the route in role coverage.
apps/ui/src/features/admin/roles/menuVisibility.test.ts	Tests menu permission coverage.
apps/ui/src/api/client.ts	Extends Inspect response typing.
apps/bff/src/logic/oap/capabilities.ts	Probes storage keyword support.
apps/bff/src/logic/oap/capabilities.test.ts	Tests capability detection and fallback.
apps/bff/src/logic/inspect/attribution.ts	Attributes agent metrics to meter rules.
.github/workflows/e2e.yaml	Updates E2E coverage documentation.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.