-
Suggestion
-
Resolution: Duplicate
-
None
-
6
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
This is a feature entry to guage the interest in Atlassian providing an enterprise level auditer.
An enterprise level auditer would be distinguishable from currently available logging services for the following reasons:
- Logging information is accessible via the Administration UI.
- Logging info. can be persisted in a database table if needed.
- Logging priorities are configurable on a component by component basis - i.e. an admin. could choose to audit security at a detailed level but only receive general notices about content creation. This configuration would occur in the Administration UI.
Another possible point to consider is logging across a cluster. If it ever appears the auditer might be leveraged to let admin.s administer federated logging.
NOTE - the clustering comment applies to current thinking for Confluence, not JIRA.
Furthermore, it would be nice if the auditer could work across both Confluence and JIRA - both product customers probably have a need for this level of logging. I'm creating this issue under Confluence for the timebeing but it is a relevant consideration for JIRA also.
- is cloned from
-
CONFSERVER-3920 Enterprise level auditing
- Closed
- is duplicated by
-
JRASERVER-3157 JIRA Administration Audit trail / notifications
- Closed
-
JRASERVER-13352 Audit log for configuration changes
- Closed
- is related to
-
JRASERVER-15109 Display standard output (application logs) into the Admin console in JIRA
- Closed
-
JRASERVER-15110 Email notification service that notifies System admins on critical events in the application.
- Closed
-
JRASERVER-20939 trace log for change management of changes to projects, not issues
- Closed
- relates to
-
JRACLOUD-7846 Enterprise level auditing
- Closed