Story #3889
Document the log aggregation component in the operations documents
100%
Description
Story #2093 provides the tickets for the d1_log_aggregation component of the CN, but doesn't provide the overview documentation of the code. Write up a section of the Operations Docs that describes the installation and overall workflow of the component, including the harvest process, the indexing process, and the access control implementation. Describe which classes provide which function, and how the log aggregation is kicked off (scheduler, etc). This will help other developers understand the code. This implementation description can be tied to the "Log Aggregation architecture design":http://mule1.dataone.org/ArchitectureDocs-current/design/LogAggregator.html description as needed.
History
#1 Updated by Robert Waltz about 11 years ago
- Target version deleted (
2013.33-Block.4.4) - Product Version set to *
#2 Updated by Robert Waltz almost 11 years ago
- Milestone changed from None to CCI-1.2
- Target version set to 2014.4-Block.1.2
#3 Updated by Robert Waltz almost 11 years ago
- translation missing: en.field_remaining_hours set to 0.0
- Milestone changed from CCI-1.2 to CCI-1.3
- Tracker changed from Task to Story
- Due date set to 2014-02-01
#4 Updated by Robert Waltz almost 11 years ago
- Due date changed from 2014-02-01 to 2014-03-29
- Target version changed from 2014.4-Block.1.2 to 2014.12-Block.2.2
#5 Updated by Peter Slaughter over 10 years ago
- Due date changed from 2014-03-29 to 2014-04-26
- Assignee changed from Robert Waltz to Peter Slaughter
- Target version changed from 2014.12-Block.2.2 to 2014.16-Block.2.4
#6 Updated by Peter Slaughter over 10 years ago
- Status changed from New to Closed
The new log aggregation document is available at https://mule1.dataone.org/ArchitectureDocs-current/design/LogAggregator.html