[FLAGON-289] Remove Logstash Dependency for Header Requests

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Done
• Affects Version/s: UserALE.js 2.0.0
• Fix Version/s: UserALE.js 2.0.0
• Component/s: UserALE.js
• Environment: JavaScript
• Flags: Important
• Assignee: Joshua Poore
• Reporter: Joshua Poore
• Due: 27/Apr/18
• Created: 16/Apr/18 13:59
• Updated: 30/May/19 05:15
• Resolved: 30/May/19 05:15

Description

We have previously relied on Logstash to handle requests from the page for data from headers. This is a vulnerability for two reasons: it makes certain information passed to UserALE.js via our API unobtainable and it places a strong dependency on Elastic assets and specific system configurations to get basic data.

Definition of Done: Header Requests are Made By UserALE.js not LogStash. Remove configs from existing logstash-config. Confirm that when logging, UserALE.js logs from browser tabs are correctly providing data pushed through UserALE.js API (useraleVersion, toolName, toolVersion, userId.

Issue Links

• mentioned in: Page Loading...
• mentioned in: Page Loading...

Sub-Tasks

• "userid" field seems to impact ability to correctly map 'details' field for tab meta data.: Open
• Log additional tag-specific event information: Open
• Collect Add'l "Low-Hanging Fruit" from Header Data: Open