Killtracker

An app for running killmail trackers with Alliance Auth and Discord.

Contents

• Overview
• Key Features
• Screenshots
• Installation
• Trackers
• Settings
• Change Log

Overview

Killtracker is an app for running killmail based trackers with Alliance Auth and Discord. Trackers are small programs that automatically select killmails based on a set of pre-defined conditions and then post them to a Discord channel as soon as they appear on zKillboard.

The main advantage of the Killtracker app over similar apps is it's high customizability, which allows you to cut through the noise of many false positives and only get the results you are really interested in.

For example you may want to know when a larger group is roaming through your area? Set up a tracker that shows all kills within 10 jumps of your staging that has more than 20 attackers. It will even ping you if you want.

Or you maybe want to be informed about any capitals being active within your jump range? Just setup a tracker for capital kills within 6 LY of your staging.

Key Features

• Automatically post killmails conforming with a set of conditions to a Discord channel as soon as they arrive on zKillboard
• Use 20+ clauses to define exactly what you want to track incl. clauses for location, organization, Auth state and ship types
• Clauses for "ship types" include ships, structures, customs offices, fighters and excavator drones
• Optional channel and group pinging for matching killmails
• Designed for fast response times, high throughput and low resource requirements
• Get additional insights about killmails like distance from staging
• See which fleets / groups are active in your area of interest
• Customize killmail messages with titles and colors

Screenshots

Here is an example for settings up a new tracker:

And here is how posted killmails look on Discord:

Installation

Step 1 - Check preconditions

1. Killtracker is a plugin for Alliance Auth. If you don't have Alliance Auth running already, please install it first before proceeding. (see the official AA installation guide for details)

2. Killtracker needs the app django-eveuniverse to function. Please make sure it is installed, before continuing.

3. Killtracker will generate a lot of tasks. For optimal performance we recommend a threads-based configuration of your celery workers. Please see this guide for details.

Step 2 - Install app

Make sure you are in the virtual environment (venv) of your Alliance Auth installation. Then install the newest release from PyPI:

pip install aa-killtracker

Step 3 - Configure settings

Configure your AA settings (local.py) as follows:

Installed apps

Add 'killtracker' to INSTALLED_APPS.

Killtracker configuration

Add below lines to your settings file:

# aa-killtracker
CELERYBEAT_SCHEDULE['killtracker_run_killtracker'] = {
    'task': 'killtracker.tasks.run_killtracker',
    'schedule': crontab(minute='*/1'),
}
KILLTRACKER_QUEUE_ID = ""  # Put your unique queue ID here

Queue ID

Please note that the queue ID must be globally unique for all users of the zKillboard API, so choose carefully.

We suggest to use your alliance name or alliance tag (without any spaces and special characters) as queue ID.

We recommend using only characters (upper and lower case) and numbers, but no spaces or any special characters when choosing your ID.

Example (don't use this exact example):

KILLTRACKER_QUEUE_ID = "Voltron9000"

If you are running multiple instances of Killtracker please choose a different queue ID for each of them.

Additional settings (optional)

Add additional settings if you want to change any defaults. See Settings for the full list.

Step 4 - Finalize installation

Run migrations & copy static files

python manage.py migrate
python manage.py collectstatic

Restart your supervisor services for Auth

Step 5 - Load Eve Universe map data

In order to be able to select solar systems and types for trackers you need to load that data from ESI once.

Load Eve Online map: (If you already have run this command with another app you can skip this step)

python manage.py eveuniverse_load_data map

Load app specific types:

python manage.py killtracker_load_eve

You may want to wait until the loading is complete before starting to create new trackers.

Step 6 - Setup trackers

The setup and configuration for trackers is done on the admin page under Killtracker.

First need to add the Discord webhook that points to the channel you want your killmail to appear to Webhooks. You can use one webhook for all trackers, but it is usually better to create a new channel / webhook for each tracker.

To test that your webhook works correctly you can send a test notification.

Next you can create your trackers under Tracker. Make sure you link each tracker to the right webhook. Once you save a tracker that is enabled it will start working.

>Hint:
A common mistake is to set both attacker alliance and victim alliance to your alliance in the same tracker. This will only match awox kills though, which is usually not what you want. Instead create separate trackers to capture kills and losses for your alliance.

As final test that your setup is correct you may want to create a "Catch all" tracker. for that just create a new tracker without any conditions and it will forward all killmails to your Discord channel as they are received.

Congratulations you are now ready to use killtracker!

Trackers

All trackers are setup and configured on the admin site under Killtracker.

Each tracker has a name, is linked to a webhook and has a set of conditions that define which killmails are selected and shown in the Discord channel. Note that if you define a tracker without any conditions tan you got a "catch all" tracker, that will post any killmail on Discord.

Each of the 20+ conditions belongs to one of two categories and they are named accordingly:

• require: Require conditions must be fulfilled by a killmail. e.g. a tracker with the condition require min attackers = 10 will post only killmails on Discord that have at least 10 attackers.
• exclude: Exclude conditions are the opposite of require. Killmails that fulfil this condition will never be posted by this tracker. e.g. a tracker with exclude high sec will never show any killmails from high sec.

You can combine multiple conditions to create the tracker you want. Note that conditions are always combined together with a boolean AND. For example: if your tracker has require min attackers set to 10 and exclude high sec enabled, then you will only get killmails that both have at least 10 attackers and are not in high sec.

Here is a list of all currently supported conditions for each tracker:

Settings

Here is a list of available settings for this app. They can be configured by adding them to your AA settings file (local.py).

Note that all settings are optional and the app will use the documented default settings if they are not used.