Julian Alcala created NIFI-14315:
------------------------------------
Summary: Unable to change controller service's bulletin log level
Key: NIFI-14315
URL: https://issues.apache.org/jira/browse/NIFI-14315
Project: Apache NiFi
Issue Type: Bug
Components: Core UI
Affects Versions: 2.2.0
Reporter: Julian Alcala
I am running nifi 2.2 and am finding that I am unable to set a controller
service's bulletin log level to anything outside of the default of "WARN."
Comments from Slack
"""
Jim HalfpennyJim Halfpenny commented:
I see the same behaviour on 2.0, at least in the UI. Setting the bulletin level
else sees the value return to WARN after clicking apply.
Tested the Elastic client and CEFReader service, both show the same behaviour.
The payload from the PUT that occurs when you click apply doesn’t appear to
contain anything relating to the log level
{"revision":\{"clientId":"8d4de37c-9d74-4c54-be49-8e17989e563e","version":5},"disconnectedNodeAcknowledged":false,"component":\{"id":"60dd7d3f-0195-1000-ffff-ffffc6410adf","name":"CEFReader","comments":""}}
Jim HalfpennyJim Halfpenny [14 minutes
ago|https://apachenifi.slack.com/archives/C0L9VCD47/p1741087657697309?thread_ts=1741086676.212249&cid=C0L9VCD47]
In this example I update the comment field and the log level, I see that the
comment is being being sent. It looks like component.bulletinLevel is not being
updated.
{"revision":\{"clientId":"8d4de37c-9d74-4c54-be49-8e17989e563e","version":6},"disconnectedNodeAcknowledged":false,"component":\{"id":"60dd7d3f-0195-1000-ffff-ffffc6410adf","name":"CEFReader","comments":"Test
comments"}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
