envoyproxy/envoy

Document WASM extension metrics

Open

#13,426 opened on Oct 7, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/docsarea/wasmhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Title: Document WASM extension metrics

Description:

We see these coming in but do not know which parts (if any) are tags and what they represent:

wasm.envoy.wasm.runtime.null.active
wasm.envoy.wasm.runtime.null.created
wasm_vm.envoy.wasm.runtime.null.active
wasm_vm.envoy.wasm.runtime.null.cloned
wasm_vm.envoy.wasm.runtime.null.created

Relevant Links:

https://github.com/envoyproxy/envoy/issues/10734

Contributor guide

Research direction
Investigate the WASM extension metrics listed in the issue (e.g., wasm.envoy.wasm.runtime.null.active) by looking at the Envoy source code or existing documentation to determine which parts are tags and what each metric represents. Then update the documentation to clarify these metrics.
Tech stack
None
Domain
documentationobservability
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Gitbasic understanding of Envoy proxy and WASM extensions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65