eclipse-theia/theia

batch logging of plugins' state changes

Open

#7,594 opened on Apr 17, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (18,676 stars) (2,478 forks)batch import
help wantedloggingplug-in system

Description

Currently we log for each plugin when it gets deployed, loaded, contributed, activated and so on. It is useful but too noisy. Usually such state changes happen for batch of plugins it would be better to create one string for the whole batch then.

Contributor guide

Tech stack
typescript
Domain
developer experienceobservability
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.
half day
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.
clear
Prerequisites
TypeScriptlogging concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the plugin lifecycle logging in the Theia codebase. Look for files related to plugin deployment, loading, activation, and contribution. The goal is to batch multiple state change logs into a single log string. Check existing logging patterns and identify where individual logs are emitted for each plugin event.