Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

HTTP Access Log Feature for Fisheye/Crucible (ver: 2.3.6)

nagarjun k April 25, 2013

Hello Team,

When we scan in the JIRA administration screen, and search & enter the "Logging & Profiling" menu, there is an option to enable" HTTP Access Logging".

Its a great utility to have, as it can help track the account(s) using the JIRA instance. we can deduce quite a few metrics out of this useful utility.

My questions are:

1. Now does anyone know if we have such setup in Fisheye/Crucible(F/C) setup?

2. If it does exist, then how does one enable HTTP Access logging for this tool?

3. If it doesnt exist, then is there a possibility to create such utility (new patch/change configuration)?

4. And more importantly, was F/C designed to have such a feature in place?

F/C version (the one we have): 2.3.6

Thank you folks.

regards

nk

3 answers

1 accepted

0 votes
Answer accepted
nagarjun k May 10, 2013

Thank you very much Atlassian team for your reply. We are now making a conscious effort to move to latest F/C environment in our organisation (ver: 2.10).

Your recommendations have been very fruitful. Thank you for the assistance.

This query is now closed & complete.

regards

nk

0 votes
Sergey Svishchev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 25, 2013

Your questions are answered by this KB article (note that in later versions the class name has changed):
https://confluence.atlassian.com/display/FISHEYE023/Enabling+Access+Logging+in+FishEye

0 votes
lpater
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 25, 2013

You can enable access logging in FishEye, as described here: https://confluence.atlassian.com/display/FISHEYE/Enabling+Access+Logging+in+FishEye

Note that in versions earlier than 2.7.8 the generated logs won't have the logged in user names because of a bug (https://jira.atlassian.com/browse/FE-3040). This is fixed in 2.7.8 and later releases.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events