Automating the filling and output of files from routine documents templates is one of those areas in the construction industry where traditionally soft, except for accounting, is at the level of licked handicrafts, in my humble opinion. Therefore, developing the theme , I invite you to discuss those problems and opportunities that were encountered in the implementation process on the basis of MS Excel.
 
of the previous article it's been half a year already. During this time, with the help of this preparation, the text part of the Executive Documentation was developed and handed over ...

Typical yuzkeys for Kibana - look at the logs, see the errors, create tickets for them. We have quite a lot of logs, there is not enough storage space for them. Therefore, simply inserting a link to a document from Elasticsearch /Kibana is not enough, especially for low-priority tasks: while we get to it, the index with the log can be already deleted. Accordingly, you have to save the document to a file and attach it to the ticket.
 
 
If you do this once, it does not go anywhere, but to create ten tickets in a row will be stupidly lazy, so I decided to automate this "quick" (ha-ha).
 
 

For the first time about TECO, I read in the parody article Real Programmers Do not Use Pascal , written not long before my birth. It was written that real programmers do not use the new-fashioned editors of EMACS and VI:
 
No, this Programmer wants an editor of the form "Asked? So get it! "- complex, mysterious, powerful, not forgiving mistakes, dangerous. TECO, to be precise.
 
The original [/b]
No, the Real Programmer wants a 'you asked for it, you got it' text editor - complicated, cryptic, powerful, unforgiving, dangerous. TECO, to be precise.
 
 
This intrigued me. What kind of animal ...