DUNE-DAQ / DUNE-DAQ/integrationtest
Implement logging best practices
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Integrationtest and the daqconf scripts it uses should use the DUNE-DAQ logging service, and allow for user configurability of log levels. This may require a command-line parameter to be added to integrationtest.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how integrationtest invokes the daqconf scripts it uses and how those scripts currently emit logs. Identify the existing command-line handling before deciding where user-configurable log levels belong. Done means both integrationtest and its daqconf scripts use the DUNE-DAQ logging service and allow the log level to be configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100