feedback: Module metrics | Tarantool
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
<…>er of requests over time with method = "POST" (and any status).
|The total number of requests over time with status = 500 (and any method).|Configuring metrics
To configure metrics, use metrics.cfg()<…>
https://www.tarantool.io/en/doc/latest/reference/reference_lua/metrics/
The code above uses status 200, but here status 500.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the linked Tarantool metrics reference page and review the module metrics example around the request and status queries. Correct the example so the code matches the stated status 500 case, then verify the surrounding documentation remains consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100