Hello HN, this a pet project I've been working on:
It allows to visualize logs from raw files in a faceted manner in a sql database.
It creates templates of recurring logs, extracting the 'moving' parts into columns values it stores in a column oriented DB
For now it is possible to:
- load a raw log file
- provide a dissect pattern to extract meta fields such as the timestamp ('ts') and message ('msg')
- Conduct analysis on the extracted data in grafana:
- Aggregate (sum, avg, percentile) on metrics, group by facets (extracted strings)
- Compute elapsed times between any given pair of events with sql (example to come)
I would like to meet someone who writes code without any bugs. Now if you're not putting bugs on purpose in your program, you probably don't know what they may arise from. So why use a tool (prints) which is deeply influenced by your assumptions on the program and which probably where wrong in the first place?
Some more arguments for the debugger:
-No need to recompile for each print
-Available for multi-threaded progs
-possibility to see the state in libs you're dependent on, in which you can't put logs nor asserts.
Hello guys, we are working on TradeSketch, a tool to build highly customizable trading indicators without coding, and use it to scan the stock market. We have just started to work on the concept, and even if it's not yet functionnal (it is not plugged to a backend), we would like to have your feedback already. What we showcase here is an example of how to create a custom indicator with our interface, and use it to screen stocks daily.
What we would like to know is:
Would you use this tool to implement your strategies?
How can we make this tool more useful/easy to use?
What kind of products (Stocks, FX, Crypto) are you interested in?
What do you use currently to scan automatically the products to find opportunities?
Thanks a lot
It allows to visualize logs from raw files in a faceted manner in a sql database. It creates templates of recurring logs, extracting the 'moving' parts into columns values it stores in a column oriented DB For now it is possible to:
- load a raw log file
- provide a dissect pattern to extract meta fields such as the timestamp ('ts') and message ('msg')
- Conduct analysis on the extracted data in grafana:
I came to work on this mostly after taking interest in templating algorithms and particularly drain: http://jiemingzhu.github.io/pub/pjhe_icws2017.pdf
Let me know if you have remarks or if you think something like this would be useful to you!