支持函数调用链的上报

Open
#18 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
observability

Research direction

Start by reading the tracer's existing SQL call-chain instrumentation and the project entry points that create reporting spans. Define which function calls should be reported and how their timing and nesting should appear, then document a measurable completion criterion and tests for complex interfaces.

Written by the indexing model from the issue text.

Description

现在源码里没看到函数调用的上报,这个我认为很重要,现在分析接口,只能看到SQL调用链,但不知道代码的执行链路,是哪个函数的耗时旧,只根据SQL,想要在一些非常复杂的接口中(可能涉及几千行代码)快速分析耗时,还是比较麻烦

Dominant language
PHP
Stars
11
Forks
21
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hyperf/tracer

All issues in hyperf/tracer

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.