Details
-
Story
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
Security Level: Default (Default Security Scheme)
-
None
-
Doc Sprint - Aug 4 - Sept 1
-
DB
-
DB
Description
Order of columns in tables is inconsistent. In addition, for better UX, we want to ensure the order of table columns is as follows:
Parameter | Description | Default | X | Y
For better maintenance, cell contents in tables should go on a separate line. This applies to all the tables in the "Operation" (Admin) documentation.
Work is chunked into smaller portions here (note that Provisioning section omitted as it is covered in a different Jira): *Make sure to update template files in each section where appropriate.
Batch 1: (Bonnie)
Users
Thresholding
Admin Web Interface
Service Assurance
Batch 2: (Bonnie)
Performance Management
Events
Alarms
Batch 3: (Bonnie)
Notifications
Business Service Monitoring
Enahnced Linkd
Batch 4: (Bonnie)
Topology Map
Database Reports
Operation
System Properties
Search
Ticketing
Batch 5: (Bonnie)
Enabling RMI
Overriding SNMP
IFTT Integration
DNS Resolver
Telemetry Daemon
NOTE: for the Queues topic in the introduction to telemetry daemon, it makes sense to leave the description as the third column, as the second column relates directly to the first.
Batch 6:
Elasticsearch integration
Flow Support
Kafka Producer
Alarm correlation
Metadata
Attachments
Issue Links
- related to
-
NMS-13516 Update "Develop Documentation" section to describe table formatting
-
- Resolved
-