quarkusio/quarkus

Allow default exporter with additional Quarkiverse exporters

Open

#36500 opened on Oct 16, 2023

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Java (12,967 stars) (2,464 forks)batch import
area/tracinggood first issuekind/enhancement

Description

Description

Currently, when an exporter is present the default exporter in not instantiated. A list of exporters through CDI is possible with Quarkiverse exporters because users can activate and deactivate each one individually, however, we need a new property to activate the default exporter, even if other ones are present. This way we can have many different exporters and the default, working together with CDI.

Contributor guide

Tech stack
java
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-2 days
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
JavaCDIQuarkus extension system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine the current exporter instantiation logic in Quarkus core, likely within the 'quarkus core' module. Look for how the default exporter is created and conditionally disabled when other exporters are present. The issue suggests adding a new configuration property (e.g., 'quarkus.exporter.default.enabled') to force enable the default exporter. Investigate the Quarkus configuration layer and CDI bean registration to implement the toggle. Check if any similar patterns exist in Quarkiverse exporter extensions.