[sysctl]
key=?value

Is probably not a great idea.  We already have

[sysctl]
key=>value
key=<value

Let's do a per-instance warking/error disablement, something along the lines of
[sysctl_no_errors]
errors=off # or 0 or [Ff]alse, ...
key1=value1
key2=value2

Open to discussion on the exact syntax.

After spending some time to write a PoC of this, I believe I have come up with a more flexible syntax.

TuneD uses the following log levels:

Level                   Numeric value
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
LOG_LEVEL_CONSOLE       60      # defined by TuneD
CRITICAL                50      # unused
ERROR                   40
WARNING                 30
INFO                    20
DEBUG                   10
NOTSET                  0

Also see:

CAPTURE_LOG_LEVELS = {
                "debug": logging.DEBUG,
                "info": logging.INFO,
                "warn": logging.WARN,
                "error": logging.ERROR,
                "console": LOG_LEVEL_CONSOLE,
                "none": None,
                }

I believe that better than using "errors=on/off" would actually be to set the logging level for a plug-in instance.

For example:

[sysctl_show_no_errors]
type=sysctl
log_level=console    # show only messages with CONSOLE (and higher) priority
sysctl_does_not_exist=1
kernel.pty.max=8192

[sysctl_show_no_warnings]
type=sysctl
log_level=error      # show only messages with ERROR (and higher) priority
sysctl_does_not_exist=1
kernel.nmi_watchdog=0

At the moment, setting a log level for a plug-in sets a logging level for all instances of the same type and we do not want that.
Changes to logs.py will likely be necessary.

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.