Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Process trace not displaying #79

Open
HugoJP1 opened this issue Oct 16, 2024 · 4 comments
Open

Process trace not displaying #79

HugoJP1 opened this issue Oct 16, 2024 · 4 comments

Comments

@HugoJP1
Copy link

HugoJP1 commented Oct 16, 2024

Hi I have added this action with the following configuration:

      - name: Collect Workflow Telemetry
        uses: catchpoint/workflow-telemetry-action@v2
        with:
          theme: "dark"
          comment_on_pr: "false"
          proc_trace_chart_max_count: 50

And the job executes well and displays in the workflow summary. However the process trace doesn't display at all:

image

Any ideas on what I can try to fix? I have already tried setting a lower proc_trace_chart_max_count, but with no difference in result.

@borissmidt
Copy link

borissmidt commented Nov 2, 2024

I'm having a look into why this isn't working
https://github.com/catchpoint/workflow-telemetry-action/tree/master/dist/proc-tracer.
The projects binaries seem to be broken with the current github runner.

I was looking into it this weekend and it seems the binaries use eBPF to plug into the linux kernel using something like this:
https://eunomia.dev/tutorials/8-exitsnoop/#exitsnoop

I'll see if i can make a working ebpf based snooper and i will opensource it when i succeed and fork this project to use them. But i can't really give a deadline for this since its purely out of curiosity i try to implement this.

I suspect ideally in a CI/CD platform something like Pyroscope or parca should be build in to do the profiling.

But sadly the metrics out of github actions is very limited and its even hard to trace if your builds are slowing down.

@borissmidt
Copy link

I've now made a process tracer which logs the commands in json to the output:

https://github.com/borissmidt/proc-tracer

But now i still have to test this thing on a github actions runner and update this repo to parse the output of the command.
I'm not sure how much work that will be.

@borissmidt
Copy link

@Piedone
Copy link

Piedone commented Nov 9, 2024

Duplicate of: #71

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants