We have recently integrated Okta and Jira, however since then we see lots of INFO messages logged to the log files.
2018-10-17 09:36:51,114 http-nio-8080-exec-24 INFO myUserName 576x4996x1 1jgqvvw 10.1.244.10 /rest/analytics/1.0/publish/bulk [c.a.j.authenticator.okta.OktaJiraAuthenticator30] Authentication result=USER_ALREADY_LOGGED_IN
I have marked this logs namespace to only log on ERROR but this doesnt make any difference.
How do we only log on ERROR?
Hi @Avinash Singh,
Did you provided the full package name in the 'Package Name' field on enabling log for ERROR event.
To set the logging level permanently you can follow the below steps:
1) configuring the
log4j.properties file, located in the
2) Add the property: like..
log4j.logger.com.atlassian.jira.authenticator.okta.OktaJiraAuthenticator = ERROR, console, filelog
3) Restart the Jira to pick up the changes.
Another way to configure this temporarily is go to
1. Login as Administrator
2. System -> logging and profiling
3. Configure logging level for another package
-Add the following "com.atlassian.jira.authenticator.okta.OktaJiraAuthenticator30"
-Set to OFF.
As mentioned this doesnt' persist, but for temporary debugging this works.
To exclude the okta spam in the log files:
Stop the application
Go to: /atlassian/jira/atlassian-jira/WEB-INF/classes
# reduce okta logs
log4j.logger.com.atlassian.jira.authenticator.okta = ERROR, console, filelog
Start the application
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events