knightchaser / aesir Goto Github PK

When the user adds some rules(Rule name to filter) while searching like below;

It gets an error like the one below.

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'split')
    at selectize.js:318:65
    at Array.forEach (<anonymous>)
    at selectize.js:301:22

let eventCallTrace = item.event.eventdata.CallTrace.split("|").map(trace => `<code>${trace}</code>`).join("<br>");

Some events may not have item.event.eventdata.CallTrace property. Use ternary methods or do something.

After accomplishing many goals(If necessary implementations are finished), let's apply GitHub Action for CI/CD. Because this project aims for a fast dockerized Go application, such strategies will accelerate and simplify the deployment procedure.

Currently, the search tab doesn't provide any kind of pagination. If users search for some conditions in a large-size EVTX dataset collection, the current code will just return lots of rows at once like the picture below. Also, the current status performs sorting via _id property after receiving all data from MongoDB, so it might be bad practice in case of large data handling

Improvement suggestions

• Pagination (e.g. Showing 30 results at once. Use MongoDB's aggregation to limit the number of results) ▶ Using infinite scroll? ▶ abolished
• Showing pagination bar (use Bootstrap components) both on and below the table.
• Sorting the result on the MongoDB side, not the client side may reduce the speed
• Printing how many rows are searched (e.g. 1,920 results) on the table
• Forcibly fix the table width (design)
• Possible improvements in Go backend related to search features /webRequestHandler/api.go

Adopting pagination may require additional calculations for querying a specific range of data from MongoDB.