shakdwipeea / cxla Goto Github PK

As most the logs uploaded will be timestamped, so different time-series algo can be used to analyse the trend. For example ARIMA is one instance.

user should enter the timestamp format.This will be generic for all log files.

Search should be able to handle regex and different types of queries for example a particular value is less than some specified value.

The file preview is currently shown by loading files in browser, this may create an issue for large log files

The ui is a mess right now. Proper guidelines should be displayed in the screen.

not able to parse some log files

Command Line interface to analyze the point of interests.

Graphs should have a save for later and then can be taken in hard copy.
Add plus button for next graphs.

Template Literal is fastest, smallest and simplest template engine, because it use JS's literal template feature.

It's 55 times faster than EJS, and it also use less CPU and RAM ressources, so it may be a good idea to use it instead of EJS 😀

Timestamp preview space should be increased.

Search entity uses js search function which may not work

select files from remote login via FTP

Add apt install instructions

@shakdwipeea .Entity has different pattern values, so I think we should take the latest encountered values.

current time is Fri Mar 4 17:59:06 2016

**S(10.102.218.57:80:UP)** _Hits(5477, 124/sec_, P[0, 0/sec]) ATr(39:39) Mbps(1.00) BWlmt(0 kbits) RspTime(123.86 ms) Load(0) LConn_Idx: (C:13; V:13,I:1, B:13, X:0, SI:2) Other: Pkt(568/sec, 142 bytes) Wt(1) Wt(Reverse Polarity)(10000)

**S(10.102.218.57:80:UP)** _Hits(3653, 118/sec_, P[0, 0/sec]) ATr(39:39) Mbps(1.00) BWlmt(0 kbits) RspTime(123.86 ms) Load(0) LConn_Idx: (C:13; V:13,I:1, B:13, X:0, SI:2) Other: Pkt(568/sec, 142 bytes) Wt(1) Wt(Reverse Polarity)(10000) Conn: CSvr(59, 0/sec) MCSvr(0) OE(54) E(54) RP(15) SQ(0) slimit_maxClient: (MaxClt: 0 [Ex: 0] Consumed: [Ex: 0 Borrowed: 0 TotActiveConn: 54] Available: 0) newlyUP_mode: NO, Pending: 0, update: 0x0, incr_time: 0x0, incr_count: 0

In the above sample entity are same in same timestamp, but corresponding pattern values are different so according to our algorithm it will take the first encountered value

npm package does not work. Required folders are not present viz. data and data/ftp

Fixing of the intro.js part for select entity button

Not working if value occurs before entity

There should be a counter(search bar) for particular entities in particular timestamp.Only that timestamp should be displayed in file display area where a particular entity is present