elastic / elastic/elastic-agent-client
diagnostics action timeouts
- Dominant language
- Go
- Stars
- 5
- Forks
- 33
- Avg merge
- 5h 18m
- Merged PRs (30d)
- 3
Description
The fleet-server issue https://github.com/elastic/fleet-server/issues/3648 will add a new duration attribute to REQUEST_DIAGNOSTICS actions.
The client proto should support specifying this duration for actions (perhaps with `google/protobuf/duration.proto`) and support passing it to diagnostics hooks.
The (optional) CPU trace hook should use the duration specified, and user defined hooks should also be able to access the value.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with fleet-server issue 3648, then locate the client proto definitions for REQUEST_DIAGNOSTICS actions and the diagnostics hooks, including the optional CPU trace hook and user-defined hooks. Check how action fields currently reach those hooks and run the relevant existing diagnostics tests; done means the optional duration is supported and available to each specified hook.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100