You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi, In scriptrunner the behaviours flod the logs and I would like to disable the logging. I tried disabling from the behaviours UI config but it just re-enables all the time.
Can I disable only the behaviour part of scriptrunner from the log4j settings? Or any other way I've might have missed?
Cheers
Amir
Hi Amir.
There's a reason why those login statements are there I would say. Are they warnings? Or simple debug statements? May I see one to have a look?
Cheers!
DY
Hi, it's a bunch of DEBUG messages like:
2018-10-16 10:27:20,349 http-nio-8080-exec-4 DEBUG xxxxx 627x24683822x1 1pzz0xe 10.135.4.44,127.0.0.1 /rest/scriptrunner/behaviours/latest/validators.json [c.o.jira.groovy.Behaviour] user xxxx(xxxx) must be in role Product Owners
2018-10-16 10:27:20,360 http-nio-8080-exec-4 DEBUG xxxxx 627x24683822x1 1pzz0xe 10.135.4.44,127.0.0.1 /rest/scriptrunner/behaviours/latest/validators.json [c.o.jira.groovy.Behaviour] must be in role: 10100
2018-10-16 10:27:20,360 http-nio-8080-exec-4 DEBUG xxxxx 627x24683822x1 1pzz0xe 10.135.4.44,127.0.0.1 /rest/scriptrunner/behaviours/latest/validators.json [c.o.jira.groovy.Behaviour] user xxxxx(xxxxx) must be in role Product Owners
2018-10-16 10:27:26,933 http-nio-8080-exec-23 DEBUG xxxxx 627x24683850x2 1pzz0xe 10.135.4.44,127.0.0.1 /rest/scriptrunner/behaviours/latest/validators.json [c.o.jira.groovy.Behaviour] must be in role: 10100
2018-10-16 10:27:26,933 http-nio-8080-exec-23 DEBUG xxxxx 627x24683850x2 1pzz0xe 10.135.4.44,127.0.0.1 /rest/scriptrunner/behaviours/latest/validators.json [c.o.jira.groovy.Behaviour] user xxxxx(xxxxx) must be in role Product Owners
2018-10-16 10:27:26,936 http-nio-8080-exec-1 DEBUG xxxxx 627x24683851x2 1pzz0xe 10.135.4.44,127.0.0.1 /rest/scriptrunner/behaviours/latest/validators.json [c.o.jira.groovy.Behaviour] must be in role: 10100
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Amir!
As far as I know, they cannot be disabled. You can, however, change the file that you can log to if you follow this documentation article.
Would logging to another file satisfy your need?
Cheers!
DY
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well through the UI you can disable the behavior logging
The problem I have is that this re-enables by itself after a while. Is that a bug or is it supposed to do that when something specific triggers?
but sure it's probably a good idea to push the SR logs to a separate file, that will clear up so the Jira log at least.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.