fork of featuring better prometheus metric query links on alerts
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

12 KiB

Forest's Go-NEB fork which attempts to re-write alerts' promql alert conditions into actual graphs

run it with ./

Testing process:



echo "firing up alert $name" 

# change url o
curl -XPOST $url -d "[{ 
	\"status\": \"firing\",
	\"labels\": {
		\"alertname\": \"$name\",
		\"instance\": \"\"
	\"annotations\": {
		\"description\": \"the hamburger is upside down!!\"
	\"generatorURL\": \" - (avg by(instance) (irate(node_cpu_seconds_total{mode%3D\\\"idle\\\"}[10m])) * 100) > 15&\"

echo ""

echo "press enter to resolve alert"

echo "sending resolve"
curl -XPOST $url -d "[{ 
	\"status\": \"resolved\",
	\"labels\": {
		\"alertname\": \"$name\",
		\"instance\": \"\"
	\"annotations\": {
		\"description\": \"the hamburger is upside down!!\"
	\"generatorURL\": \" - (avg by(instance) (irate(node_cpu_seconds_total{mode%3D\\\"idle\\\"}[10m])) * 100) > 15&\"

echo ""

you might want port-forward the alertmanager (http on port 9093 ) to your localhost so you can see what its doing in its web gui.


Build Status

Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, the original Matrix bot written in Python.

Table of Contents

Quick Start

Clone and run (Requires Go 1.14+):

go build
BIND_ADDRESS=:4050 DATABASE_TYPE=sqlite3 DATABASE_URL=go-neb.db?_busy_timeout=5000 BASE_URL=http://localhost:4050 ./go-neb

Get a Matrix user ID and access token and give it to Go-NEB:

curl -X POST localhost:4050/admin/configureClient --data-binary '{
    "UserID": "@goneb:localhost",
    "HomeserverURL": "http://localhost:8008",
    "AccessToken": "<access_token>",
    "Sync": true,
    "AutoJoinRooms": true,
    "DisplayName": "My Bot"

Tell it what service to run:

curl -X POST localhost:4050/admin/configureService --data-binary '{
    "Type": "echo",
    "Id": "myserviceid",
    "UserID": "@goneb:localhost",
    "Config": {}

Invite the bot user into a Matrix room and type !echo hello world. It will reply with hello world.



  • Login with OAuth2.
  • Ability to create Github issues on any project.
  • Ability to track updates (add webhooks) to projects. This includes new issues, pull requests as well as commits.
  • Ability to expand issues when mentioned as foo/bar#1234.
  • Ability to assign a "default repository" for a Matrix room to allow #1234 to automatically expand, as well as shorter issue creation command syntax.


  • Login with OAuth1.
  • Ability to create JIRA issues on a project.
  • Ability to expand JIRA issues when mentioned as FOO-1234.


  • Ability to query Giphy's "text-to-gif" engine.


  • Ability to query Guggy's gif engine.


  • Ability to read Atom/RSS feeds.

Travis CI

  • Ability to receive incoming build notifications.
  • Ability to adjust the message which is sent into the room.


  • Ability to receive alerts and render them with go templates


Go-NEB is built using Go 1.14+. Once you have installed Go, run the following commands:

# Clone the go-neb repository
git clone
cd go-neb

# Build go-neb
go build


Go-NEB uses environment variables to configure its SQLite database and bind address. To run Go-NEB, run the following command:

BIND_ADDRESS=:4050 DATABASE_TYPE=sqlite3 DATABASE_URL=go-neb.db?_busy_timeout=5000 BASE_URL=https://public.facing.endpoint ./go-neb
  • BIND_ADDRESS is the port to listen on.
  • DATABASE_TYPE MUST be "sqlite3". No other type is supported.
  • DATABASE_URL is where to find the database file. One will be created if it does not exist. It is a URL so parameters can be passed to it. We recommend setting _busy_timeout=5000 to prevent sqlite3 "database is locked" errors.
  • BASE_URL should be the public-facing endpoint that sites like Github can send webhooks to.
  • CONFIG_FILE is the path to the configuration file to read from. This isn't included in the example above, so Go-NEB will operate in HTTP mode.
  • LOG_DIR is a directory that log files will be written to, with log rotation enabled. If set, logging to stderr will be disabled. Go-NEB needs to be "configured" with clients and services before it will do anything useful. It can be configured via a configuration file OR by an HTTP API.

Configuration file

If you run Go-NEB with a CONFIG_FILE environment variable, it will load that file and use it for services, clients, etc. There is a sample configuration file which explains all the options. In most cases, these are direct mappings to the corresponding HTTP API.


The API is documented in sections using godoc. The sections consists of:

  • An HTTP API (the path and method to use)
  • A "JSON request body" (the JSON that is inside the HTTP request body)
  • "Configuration" information (any additional information that is specific to what you're creating)

To form the complete API, you need to combine the HTTP API with the JSON request body, and the "Configuration" information (which is always under a JSON key called Config). In addition, most APIs have a Type which determines which piece of code to load. To find out what the right type is for the thing you're creating, check the constants defined in godoc.

Configuring Clients

Go-NEB needs to connect as a matrix user to receive messages. Go-NEB can listen for messages as multiple matrix users. The users are configured using an HTTP API and the config is stored in the database.

Configuring Services

Services contain all the useful functionality in Go-NEB. They require a client to operate. Services are configured using an HTTP API and the config is stored in the database. Services use one of the matrix users configured on Go-NEB to send/receive matrix messages.

Every service has an "ID", "type" and "user ID". Services may specify additional "config" keys: see the specific service you're interested in for the additional keys, if any.

List of Services:

Configuring Realms

Realms are how Go-NEB authenticates users on third-party websites.

List of Realms:

Authentication via HTTP:

Authentication via the config file:


There's a bunch more tools this project uses when developing in order to do things like linting. Some of them are bundled with go (fmt and vet) but some are not. You should install the ones which are not:

go get
go get

You can then install the pre-commit hook:



|      |                 Go-NEB                               |
| +---------+                                                 |
| | Clients |                                                 |
| +---------+                                                 |
|      |                                                      |
| +---------+       +------------+      +--------------+      |
| | Service |-------| Auth Realm |------| Auth Session |-+    |
| +---------+       +------------+      +--------------+ |    |
|     ^                   ^              +---------------+    |
|     |                   |                                   |
      |                   |                   
    WEBHOOK            REDIRECT
    REQUEST            REQUEST
Clients      = A thing which can talk to homeservers and listen for events. /configureClient makes these.
Service      = An individual bot, configured by a user. /configureService makes these.
Auth Realm   = A place where a user can authenticate with. /configureAuthRealm makes these.
Auth Session = An individual authentication session /requestAuthSession makes these.

Viewing the API docs

The full docs can be found on Github Pages. Alternatively, you can locally host the API docs:

# Start a documentation server listening on :6060
GOPATH=$GOPATH:$(pwd) godoc -v -http=localhost:6060 &

# Open up the documentation for go-neb in a browser.
sensible-browser http://localhost:6060/pkg/

Docker image

To get started quickly, use the image from

docker run -v /path/to/data:/data -e "BASE_URL=http://your.public.url:4050" matrixdotorg/go-neb

If you'd prefer to build the file yourself, clone this repository and build the Dockerfile.

The image sets the following environment variables:


The image exposes port 4050 and a volume at /data. The BASE_URL environment variable needs to be set, a volume should be mounted at /data and port 4050 should be appropriately mapped as desired.