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

Scoped dockerd does not produce events, it only produces metrics. #1424

Open
seanvaleo opened this issue Apr 11, 2023 · 3 comments
Open

Scoped dockerd does not produce events, it only produces metrics. #1424

seanvaleo opened this issue Apr 11, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@seanvaleo
Copy link
Collaborator

Steps To Reproduce

root@precision:/home/sean/sandbox# scope attach dockerd
WARNING: Session history will be stored in /root/.scope/history and owned by root
Attaching to process 3029
root@precision:/home/sean/sandbox# scope metrics
NAME             VALUE              TYPE     UNIT           PID     TAGS
proc.start       1                  Count    process        3029    args: /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.s…
proc.cpu         3.990642489e+09    Count    microsecond    3029    host: precision,proc: dockerd
proc.cpu_perc    39906.42489        Gauge    percent        3029    host: precision,proc: dockerd
proc.mem         3.905616e+06       Gauge    kibibyte       3029    host: precision,proc: dockerd
proc.thread      42                 Gauge    thread         3029    host: precision,proc: dockerd
proc.fd          25                 Gauge    file           3029    host: precision,proc: dockerd
proc.child       41                 Gauge    process        3029    host: precision,proc: dockerd
root@precision:/home/sean/sandbox# scope events
Empty event file.

Environment

- AppScope: 1.3.1
- OS: ubuntu 22.04
- Architecture: x86
- Kernel: 5.19.0-38-generic

Requested priority

None

Relevant log output

No response

@seanvaleo seanvaleo added the bug Something isn't working label Apr 11, 2023
@iapaddler
Copy link
Contributor

iapaddler commented Apr 18, 2023

Refer to #1416. This is resolved there.

Note that interposition fails when attaching to dockerd because runtime/internal/syscall.Syscall6 cannot be resolved. It does locate runtime/internal/syscall.Syscall6.abi0. Will need to determine why and if the abi0 version can be used in all cases.

@jrcheli
Copy link
Contributor

jrcheli commented Apr 18, 2023

I think the syscall.Syscall6 describes why we aren't seeing any events, and why we can see metrics. (metrics don't depend on the syscall.Syscall6 instrumentation)

On my system (an aarch64 ubuntu 20.04) I also saw this log message from the time of attach:

Scope: dockerd(pid:776): [2023-04-18T20:41:21.609+0000] /usr/bin/dockerd was compiled with go version `go1.16.12`.  AppScope can only instrument go1.19 or newer on ARM64.  Continuing without AppScope.

We are continuing to get metrics, so I'm not exactly sure what to make of the log message.

@abetones
Copy link
Contributor

Documented as a Known Issue in AppScope 1.3.2: https://appscope.dev/docs/known-issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants