wu-sheng opened a new pull request, #879:
URL: https://github.com/apache/skywalking-website/pull/879

   Part 12 of the **Meet Horizon UI** series — continuing Act 3 (operate). The 
Inspect family: three cross-layer query power-tools under Operate that drop the 
layer-first step.
   
   ### Content
   - **Metrics inspect** — the unique one (no per-layer equivalent): a catalog 
of every metric OAP computes, grouped by the **OAL/MAL rule that defines it** 
(the rule attribution from the previous post), plus an MQE **board** to chart 
any metric across any entity (with foreign-metric support). Needs OAP 11's 
admin host + `inspect` module; shows a clean banner when absent.
   - **Trace inspect** — the Trace Explorer with the layer removed: optional 
Target (pick / type / **blank = all services**), full conditions, distribution 
scatter, the shared waterfall, and a resolved-query transparency line. Standard 
query protocol (works on OAP 10.x).
   - **Log inspect** — layer-less logs with one **Source** switch over three 
worlds: Raw stored logs, Browser JS errors (with source-map de-obfuscation), 
and Kubernetes Pod-log live tail. Standard query protocol.
   - **Where it runs** — all three share `inspect:read`; Trace/Log inspect are 
the cross-layer counterparts to the per-layer Trace Explorer (P6) / Log 
Explorer (P7).
   
   ### Figures (4, WebP)
   1. The Metrics inspect catalog grouped by defining rule source
   2. A metric charted on the Inspect board (with its OAL/Service attribution)
   3. Trace inspect — blank target, one trace crossing five services
   4. Log inspect — the Raw / Browser / Kubernetes Pod-logs source switch
   
   Render-verified against the Inspect code and adversarially fact-checked 
(ship-as-is). Screenshots captured live from the demo backend.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to