calling PropertiesV2 as library consumer
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- operating-systems
Research direction
Start with container.go around lines 169-170 and trace the internal function referenced in the issue. Determine the public API needed for external consumers to call PropertiesV2 and review how the existing v1 call exposes container metrics. Done means a v2 entry point is available to library consumers and supports the functionality missing from the legacy call.
Written by the indexing model from the issue text.
Description
The windows_exporter embeds Microsoft's hcsshim library to fetch container metrics.
Currently, only the legacy v1 call can be used by other programs, as they do not have access to the internal package. For example, in hcsshim, the relevant function is defined internally and not exposed for external use.
However, there is no v2 function available that supports the new functionality.
The v1 legacy call has some limitations: If containerd is used, network statistics are no longer available, and Host/Job Containers are not exposed.
- Dominant language
- Go
- Stars
- 694
- Forks
- 304
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 28
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from microsoft/hcsshim
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
microsoft/hcsshim#2831 · 3 comments ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
microsoft/hcsshim#2823 · 8 comments ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 62/100
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
Maintainers usually reply within 2 days
All issues in microsoft/hcsshim
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
volodya-lombrozo/aidy#333 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
rossoctl/context-guru#314 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
OwO-Network/DLX#236 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100