open-feature/flagd

[FEATURE] Reevaluate Logging framework and maybe switch

Open

#1,324 opened on Jun 10, 2024

View on GitHubContributor guide
 (2 comments) (5 reactions) (1 assignee)Go (118 forks)github user discovery
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (925 stars)
PR merge metrics
 (Avg merge 3d 9h) (8 merged PRs in 30d)

Description

Requirements

Currently, flagd is using ZAP as a logging framework, which works great. ZAP was chosen because no logging framework was delivered with Go. Now, there is slog, which offers all the functionality needed but is a standard library package.

One of the reasons for proposing this change is https://github.com/open-feature/go-sdk-contrib/issues/522 and https://github.com/open-feature/go-sdk/issues/260. To enable better interoperability, it would make sense to evaluate and maybe switch to slog.

Contributor guide

Research direction
Analyze the benefits and drawbacks of switching from ZAP to slog, considering interoperability with SDKs as mentioned in linked issues. Provide a comparison and recommendation.
Tech stack
go
Domain
backenddeveloper experience
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70