argoproj/argo-events

Possibility to change log level for Sensor of HTTP trigger

Open

#2,988 opened on Jan 23, 2024

View on GitHub
 (5 comments) (3 reactions) (0 assignees)Go (829 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (2,679 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem? Please describe. Right now sensors with http triggers generate logs on each event. If you have a lot of them - then it becomes issue.

Describe the solution you'd like Provide possibility to set log level for Sensor of HTTP trigger. So we can set for example warn instead of default info.

Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

Contributor guide

Research direction
Investigate the Sensor codebase to locate where HTTP trigger logs are generated at info level. Then modify the logging to use configurable log level, likely via a new field in the sensor spec (e.g., `logLevel`). Follow existing patterns for configuration in the Argo Events project (e.g., similar to other triggers).
Tech stack
go
Domain
backendapidevops
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.
Mostly clear
Prerequisites
GoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30