ngx-top

KO | EN

gitlite — search

#javascript #ai #llm #go #golang #android #rust #deep-learning #nodejs #windows #awesome #awesome-list #pytorch #openai

(★ 25)

Monitor nginx access logs in real time.

ngx-top Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# ngx-top

Monitor nginx access logs in real time.

![screenshot](https://cloud.githubusercontent.com/assets/157610/22991025/eda61298-f3b2-11e6-8a17-b03d87dbb056.gif)

![Build status](https://travis-ci.org/pbogdan/ngx-top.svg?branch=master)

## Installation

ngx-top binary can be built in two ways, either using [haskell stack tool](https://www.haskellstack.org):

```
stack build
```

The location of the produced binary can be found with `stack exec -- which ngx-top`.

Another option is to produce a fully statically linked binary using [docker-compose](https://docs.docker.com/compose/):

```
docker-compose up
```

and the binary will be placed in the `build` folder.

Statically and dynamically linked binaries are now available via Releases section.

## Usage

```
$ ngx-top logfile [logfile...]
```

Currently ngx-top supports log files in the default combined format and a custom gateway format. At this time only the custom format contains all the required information to enable full current feature set.  
ngx-top will attempt to automatically detect correct log file format, defaulting to gateway format if auto-detection fails for any reason.

### Running a demo

ngx-top-gen binary is included to generate random log lines for testing / demo purposes:

```
stack exec -- ngx-top-gen > logfile
```

This will generate approximately 100 lines per second and write them to `logfile`.

And in another terminal window:

```
stack exec -- ngx-top logfile
```

`stack exec` invocations above can be replaced with usage of binaries in the build folder if docker-compose build method was used.

### Usage as haskell library

`ngx-top` can also be used as a Haskell library which allows supplying custom parsers without the need to making changes to `ngx-top` itself. The simplest example which replicates the default behaviour would look as follows:

```haskell
import NgxTop

main = defaultMain defaultSettings
```

If you wish to inject custom parsers you would also need to depend on the [log-parser](https://github.com/pbogdan/log-parsessr) package. The first step is to write a parser function of the following type:

```haskell
import Log.Nginx.Types

myParser :: ByteString -> Either Text AccessLogEntry
```

which is expected to process a single line of input and return either an error or `AccessLogEntry` record. The next and final step is to supply it to `defaultMain` function:

```haskell

import qualified Data.List.NonEmpty as NE

main = defaultMain Settings { parsers = NE.fromList [myParser] }
```

## Performance

Using Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz ngx-top can currently process approximately 17000 log lines per second. Memory usage will vary depending on the log file, no extensive testing has been performed yet to determine accurate figures.
It's important to note that due to continuous processing memory usage will constantly grow overtime, to prevent an unintentional memory exhaustion ngx-top will exit when total memory usage reaches 256 MB.

---

This project includes GeoLite2 data created by MaxMind, available from [www.maxmind.com](http://www.maxmind.com).

ngx-top

ngx-top Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

ngx-top

ngx-top Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README