nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira reduce logging for namespace

Avinash Singh

We have recently integrated Okta and Jira, however since then we see lots of INFO messages logged to the log files.

Eg.

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.
https://jiratest.xxx.co.xx/secure/admin/ViewLogging.jspa

c.a.j.authenticator.okta.OktaJiraAuthenticator30 ERROR

How do we only log on ERROR?

Accepted answers

Rambabu Patina {Appfire}

Hi @Avinash Singh,

Did you provided the full package name in the 'Package Name' field on enabling log for ERROR event.

Like.. com.atlassian.jira.authenticator.okta.OktaJiraAuthenticator

To set the logging level permanently you can follow the below steps:

1) configuring the log4j.properties file, located in the $JIRA_INSTALL/atlassian-jira/WEB-INF/classes/ directory

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.

Thanks,
Ram.

All comments

Rambabu Patina {Appfire}

Hi @Avinash Singh,

Did you provided the full package name in the 'Package Name' field on enabling log for ERROR event.

Like.. com.atlassian.jira.authenticator.okta.OktaJiraAuthenticator

To set the logging level permanently you can follow the below steps:

1) configuring the log4j.properties file, located in the $JIRA_INSTALL/atlassian-jira/WEB-INF/classes/ directory

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.

Thanks,
Ram.

Avinash Singh

Thanks Rambabu.

Isnt c.a.j.authenticator.okta.OktaJiraAuthenticator30 the full package name from the logs?

I cant restart the server at the moment, so I would need to do it through Jira Logging and Profiling admin section.

Rambabu Patina {Appfire}

It is not a full package name. First three names shorthanded in the log file.

Can you enable ERROR log using the below package name and let us know how it goes.

com.atlassian.jira.authenticator.okta

Avinash Singh

Excellent that did the job. Is there a way to identify the full package name or did assume that from the log message ?

tony wong

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.

Alex Gay_lo39f6

somebody has an idea on the okta package name for Confluence?

Will it be that simple to replace jira with confluence?

log4j.logger.com.atlassian.jira.authenticator.okta = ERROR, console, filelog

JCFP Admin

It's work on my instance.

Thanks Tony

Alex Gay_lo39f6

To exclude the okta spam in the log files:

Stop the application

Go to: /atlassian/jira/atlassian-jira/WEB-INF/classes

edit: log4j.properties

add:

# reduce okta logs
log4j.logger.com.atlassian.jira.authenticator.okta = ERROR, console, filelog

Start the application

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server