search

dlakaplan / LogParse

0 stars 0 forks source link

Implement slack webhook for astrid (GBT) logs #23

Open swiggumj opened 4 years ago

swiggumj commented 4 years ago

Slack output in markdown blocks 

For
example

would be easier to read too, I think.

dlakaplan commented 4 years ago

The hook is in the software already - all you need to do is provide the URL locally

dlakaplan commented 4 years ago

In terms of formatting, the problem is that (as currently implemented) those blocks have fixed width. so it doesn't look good. As an example:

WARNING:log_parser:Cannot identify science scan to accompany scan 0
##############################
### Report for: examples/logs/AGBT18B_226_100_log.txt starting at line 0
### NANOGrav AGBT18B_226 observation (0.2h elapsed; 0.0h observing; 0.0m
 slewing; 1 scans 1 sources)
### Backend: 'GUPPI'
### 2019-05-02 15:17:28-04:00 - 2019-05-02 15:29:24-04:00
   429 sec (     2 sec slewing) --> Execute PSR J0125-2327 (std) for   90s +  
90s cal at 820.0MHz at linenumber   427 at 2019-05-02 15:24:37-04:00 (1776 sec 
requested) 
    Writing to guppi_58605_69876_J0125-2327_0001_cal

as far as I can tell, there is not an option to change the width of the code block. I think slack markdown is slightly different from GitHub in this respect.

dlakaplan commented 4 years ago

If the overall legibility is lacking, let me know how you'd suggest changes to the formatting. code blocks would work with shorter lines: how would you break them?