Where are the Insight logs for Data Center installations

Still need help?

The Atlassian Community is here for you.

Ask the community


Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

When we install Insight app on a Data center installation of Jira, the Insight logs are not stored with the other Jira logs and they are also not part of Support zip by default. This page explains where these logs are stored.

Solution

The below mentioned solution works for the insight versions prior to Jira 4.20.4 and Insight 9.1.4:

  • On Data Center - Insight will keep all its log files in /jira-shared-home/log/
  • These logs are not part of the Support zip by default.
  • When Jira is restarted, it adds the Insight logs directory location to the atlassian-jira.log file

  • So, if you need to know the location for the Insight logs on your instance, try to do a grep for : 

    grep 'Insight log directory' atlassian-jira.log*

     You should get results like this :

    atlassian-jira.log.1:2020-12-14 10:41:54,971+0100 ThreadPoolAsyncTaskExecutor::Thread 4 WARN      [c.r.j.p.i.s.i.schema.log.ImportObjectSchemaLogger] Insight log directory: /Users/aaa/deployments/jira8110/jira-home/log
    atlassian-jira.log.1:2020-12-14 10:41:54,975+0100 ThreadPoolAsyncTaskExecutor::Thread 4 WARN      [c.r.j.p.i.s.i.schema.log.ExportObjectSchemaLogger] Insight log directory: /Users/aaa/deployments/jira8110/jira-home/log
    atlassian-jira.log.1:2020-12-14 10:41:54,977+0100 ThreadPoolAsyncTaskExecutor::Thread 4 WARN      [c.r.j.p.i.s.automation.log.AutomationLogger] Insight log directory: /Users/aaa/deployments/jira8110/jira-home/log
    atlassian-jira.log.1:2020-12-14 10:41:54,979+0100 ThreadPoolAsyncTaskExecutor::Thread 4 WARN      [c.r.j.p.i.s.i.schema.log.ImportLogger] Insight log directory: /Users/aaa/deployments/jira8110/jira-home/log
    atlassian-jira.log.1:2020-12-14 10:41:54,981+0100 ThreadPoolAsyncTaskExecutor::Thread 4 WARN      [c.r.j.p.i.s.core.audit.InsightAuditLogger] Insight log directory: /Users/aaa/deployments/jira8110/jira-home/log
    atlassian-jira.log.1:2020-12-14 10:41:54,983+0100 ThreadPoolAsyncTaskExecutor::Thread 4 WARN      [c.r.j.p.i.s.i.schema.log.InsightWorkflowLogger] Insight log directory: /Users/aaa/deployments/jira8110/jira-home/log
    atlassian-jira.log.1:2020-12-28 12:02:13,359+0100 ThreadPoolAsyncTaskExecutor::Thread 13 WARN      [c.r.j.p.i.s.i.schema.log.ImportObjectSchemaLogger] Insight log directory: /Users/aaa/deployments/jira8110/jira-home/log

    This is how we can confirm the location for the logs.


  • This is an LS from a Shared Home/log folder:
log % ls
insight_audit.log			
insight_import.log
insight_automation.log			
insight_objectschema_export.log
insight_automation.log.2022-01-20	
insight_objectschema_import.log
insight_automation.log.2022-01-21	
insight_workflow.log
insight_automation.log.2022-01-24


  • For the insight version later than Jira 4.20.4 and Insight 9.1.4, changes were implemented. So the log location will be present under JIRA_HOME\log folder in each node and included in the support.zip. 

Insight Import Logs

There are two types of imports in Insight:

  • Scheduled import
    • Occurs in the node defined in the "Dedicated Scheduling Node" setting in "Administration > Manages apps > Insight Configuration > Dedicated Scheduling Node". 
  • Manual imports
    • These are triggered manually by a Jira administrator. 
    • The import logs will be present on whichever node the import is executed from. 

As a result, in a multi-node Data Center configuration, the insight import logs are not kept in one central location but rather on the node executing the import in the <Jira_Home>/log directory.


Last modified on Mar 28, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.