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.

Sign up for GitHub

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

Jump to bottom

Feature Request: Add NO_DAEMON_START count metric #2145

Open
SgtPooki opened this issue May 16, 2022 · 1 comment
Open

Feature Request: Add NO_DAEMON_START count metric #2145

SgtPooki opened this issue May 16, 2022 · 1 comment
Labels
area/go-ipfs Issues related to go-ipfs daemon (config, orchestration, features) area/webui Issues specific to interaction with ipfs-webui effort/hours Estimated to take one or several hours exp/beginner Can be confidently tackled by newcomers good first issue Good issue for new contributors kind/enhancement A net-new feature or improvement to an existing feature P2 Medium: Good to have, but can wait until someone steps up status/ready Ready to be worked

Comments

@SgtPooki
Copy link
Member

We have DAEMON_START metric which shows duration and count of times we need to start up our own daemon. However, we do not have a metric to show how often there are users who are already running an ipfs daemon.

The webui is available when running the go implementation of IPFS, so if we see a lower count for this NO_DAEMON_START metric, then we could potentially redirect any users who are already running a daemon to the webui.
@SgtPooki SgtPooki added need/triage Needs initial labeling and prioritization P2 Medium: Good to have, but can wait until someone steps up kind/enhancement A net-new feature or improvement to an existing feature exp/beginner Can be confidently tackled by newcomers effort/hours Estimated to take one or several hours status/ready Ready to be worked area/webui Issues specific to interaction with ipfs-webui area/go-ipfs Issues related to go-ipfs daemon (config, orchestration, features) good first issue Good issue for new contributors and removed need/triage Needs initial labeling and prioritization labels May 16, 2022
@Kirobi92 Kirobi92 mentioned this issue Jun 23, 2022
Open
@MarcelRaschke MarcelRaschke mentioned this issue Oct 10, 2022
Open
@SgtPooki
Copy link
Member Author

related to ipfs/ipfs-gui#117

@yng3 yng3 mentioned this issue Jan 19, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/go-ipfs Issues related to go-ipfs daemon (config, orchestration, features) area/webui Issues specific to interaction with ipfs-webui effort/hours Estimated to take one or several hours exp/beginner Can be confidently tackled by newcomers good first issue Good issue for new contributors kind/enhancement A net-new feature or improvement to an existing feature P2 Medium: Good to have, but can wait until someone steps up status/ready Ready to be worked
Projects
No open projects
IPFS-GUI (PL EngRes)
Status: Planned / Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SgtPooki