-
```
This is working fine
import java.util.concurrent.atomic.AtomicBoolean
//@Typed
class LogParser{
AtomicBoolean busy = new AtomicBoolean(false)
static main(args){
new LogParser()
…
-
Right now, the `%context%` `%extra%` are just displayed as part of the `%message%`.
It would be nice to be able to access this information in a similar way as the call stack.
-
I recently saw the following warning from ISISRunLogs.h
```
/Users/svh/Documents/MantidProject/mantid/Framework/DataHandling/inc/MantidDataHandling/ISISRunLogs.h:64:13: warning: private field 'm_numO…
-
```
It should be possible to obtain the entire log in CSV format. This can
enable the use of a number of tools for analyzing and querying the log,
such as LogParser and Microsoft Excel.
- The CSV f…
-
```
It should be possible to obtain the entire log in CSV format. This can
enable the use of a number of tools for analyzing and querying the log,
such as LogParser and Microsoft Excel.
- The CSV f…
-
```
It should be possible to obtain the entire log in CSV format. This can
enable the use of a number of tools for analyzing and querying the log,
such as LogParser and Microsoft Excel.
- The CSV f…
-
```
It should be possible to obtain the entire log in CSV format. This can
enable the use of a number of tools for analyzing and querying the log,
such as LogParser and Microsoft Excel.
- The CSV f…
-
```
It should be possible to obtain the entire log in CSV format. This can
enable the use of a number of tools for analyzing and querying the log,
such as LogParser and Microsoft Excel.
- The CSV f…
-
Reported by @rocketraman via https://groups.google.com/d/msg/sematext-docker-agent/k_CQIEqAALM/xRvcCzOdBwAJ
otisg updated
8 years ago
-
```
It should be possible to obtain the entire log in CSV format. This can
enable the use of a number of tools for analyzing and querying the log,
such as LogParser and Microsoft Excel.
- The CSV f…