Issue Manager JIRA Integration
We currently have Issue Manager integrated with JIRA but today have run into an issue where Silk Central as sent a high volume of requests to JIRA to update issue/status(s).
I am unclear on how the synchronization works between the 2 systems.
Is there a way to check what triggered this high volume sync? Or somewhere we can check the configuration of the scheduled sync?
Issue tracking integrations are updated either by schedule or manually.
1. Logs on scheduled updates can be found in the AppServer log files (accessible via Administration > Log Files > Application Server Log).
The schedule is configured in TMAppServerHomeConf.xml (e.g. C:\Program Files (x86)\Silk\Silk Central 19.5\instance_1_silk\Conf\AppServer\TMAppServerHomeConf.xml). The relevant configuration options can be found in Config > IssueStateUpdate
It is possible to configure the UpdateInterval in minutes, to turn on/off the issue statistics, to turn on/off issue statistics for baselines and to optionally schedule a timestamp when the update should start for the first time.
A description how to disable updating of external issue statistics can be found here:
2. Manual updates can be triggered In Tests > Details View > Tab: Issues
If you press the button Update Issue States then immediately the update starts. Logs on this can be found in the FrontendServer log files.
In both cases most of the data is logged in log level DETAILED or higher.
We've investigated the configuration of the scheduled Sync and have confirmed no manual syncs are being run frequently.
But we continue to see a high volume of Attempts from Silk Central authenticating to JIRA.
Any idea's on how we can narrow our search to find the root cause of this problem as it is creating performance issues with JIRA.
If you set the log level to DEBUG then more information will be visible in the logs.
Frontendserver (manual triggered updates), e.g.
C:\Program Files (x86)\Silk\Silk Central 19.0\instance_1_silk\Conf\FrontendServer\SccFrontendBootConf.xml
AppServer (scheduled updates), e.g.
C:\Program Files (x86)\Silk\Silk Central 19.0\instance_1_silk\Conf\AppServer\SccAppServerBootConf.xml
Config > Log > LogLevel
Set to 3 (= DEBUG)
It is not necessary to restart the services.
Information on the issue updates will be logged to FrontendServer.log and AppServer.log.