[VOL-2356] core log_level command line argument should take log level names not int value - OpenCORD JIRA

XML

Word

Printable

Details

Type: Story
Status: Resolved (View Workflow)
Priority: Low
Resolution: Done
Affects Version/s: None
Fix Version/s: VOLTHA v2.3
Component/s: ro-core, rw-core
Labels:
None

Story Points:
1
Epic Link:
Logging Evolution

Description

Currently, the cores take an integer value to set the initial log level (i.e. 0 to 5). Instead, they should support the following values

OFF

FATAL

ERROR

WARN

INFO

DEBUG

TRACE

Attachments

Options
- Issue Only
- Show All Reviews
- Show Open Reviews
- Show All Issues
- Show Open Issues

Gerrit Reviews

No reviews matched the request. Check your Options in the drop-down menu of this sections header.

Activity

People

Assignee:: Rohan Agrawal

Reporter:: David Bainbridge

Watchers:: 3 Start watching this issue

Dates

Created:: 2019/12/12 10:24 AM

Updated:: 2020/02/24 8:56 PM

Resolved:: 2020/02/24 8:56 PM

Gerrit Reviews

There are no open Gerrit changes

Show There are 6 closed Gerrit changes

Hide There are 6 closed Gerrit changes

[VOL-2356] removed Panic loglevel and added a method to convert loglevel from string to int: Gerrit Review:

[VOL-2356]core log_level command line argument should take log level names not int value: Gerrit Review:

[VOL-2356]core log_level command line argument should take log level names not int value: Gerrit Review:

[VOL-2356]core log_level command line argument should take log level names not int value: Gerrit Review:

[VOL-2356]core log_level command line argument should take log level names not int value: Gerrit Review:

VOL-2356 Change log.V() to use a typed LogLevel: Gerrit Review: