ipfs/ipfs-desktop

Feature Request: Add NO_DAEMON_START count metric

Open

#2145 opened on May 16, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (5,632 stars) (912 forks)batch import
P2area/go-ipfsarea/webuieffort/hoursexp/beginnergood first issuekind/enhancementstatus/ready

Description

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.

Contributor guide

Tech stack
javascriptnodejs
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with IPFS Desktop codebaseUnderstanding of existing DAEMON START metric
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Find where the DAEMON START metric is defined and emitted in the codebase (likely in the daemon startup logic). Add a new metric called NO DAEMON START that is emitted when a user already has an IPFS daemon running, indicating they could be redirected to the web UI. Ensure the metric is counted appropriately and follows the same pattern as the existing metric.