curtisf / logger

Loggerbot version 3, the Discord bot serving nearly 24 million users.

Logger is a powerful Discord bot meant to give staff members oversight over the various actions taking place in their server. Come talk about me with my creator at Logger's Lounge.

Installation

You are mostly on your own selfhosting this version. Required applications:

• PostgreSQL 11
• Redis
• NodeJS 14+ (14.5.0)

1. Setup Postgres and add a superuser (default user works)
2. Clone bot repo and enter the created folder
3. Copy .env.example into .env
4. Fill out all fields in it (even Sentry unless you hotpatch it out)
5. npm install
6. node src/miscellaneous/generateDB.js
7. Set ENABLE_TEXT_COMMANDS="true" in .env
8. node index.js
9. Use your prefix to set the bot's commands. If yours is %, then you'd do %setcmd global to globally set commands, and %setcmd guild to quickly set server-specific slash commands

Usage

node index.js

Contributing

Pull requests are welcome as long as it follows the following guidelines:

1. Is your idea really one that a large group of moderators would like?
2. Is your idea scalable?
3. Will your idea cause the bot to hit it's global ratelimit?
4. Have you proposed it to piero#5432 in my support server?

If you have done all of the above steps, then open a pull request and I will review it. Style guide and testing will be implemented in a later update.

logger's Issues

Recurring duplicate text channel update messages

Repro Steps (Inconsistent):

• Admin modifies a channel permission
• Logger emits a message to the specified channels saying "Texture channel was updated (ChanName)\n Creation...etc...role RoleName"
• Logger re-emits a message every 10 minutes indefinitely. Sometimes it will eventually stop it self, sometimes I have to spend a couple hours trying various things on the server until Logger stops. I have been unable to narrow down the actual cause/fix for this yet.

add multi db

quick.db

feature request: log the originator of message delete events

while it's very helpful to have a history of removed messages, their author, and their contents, it'd be convenient if that log also included who initiated the removal.

this would greatly reduce the amount of time squinting at audit logs to check whether a moderator was the one who removed the message, or if the user removed it themselves.

AES_Key and Paste_CREATE_ENDPOINT

Hi,
Im not sure if this repo is still active but i was wondering where should i generate the AES_KEY and which haste-server to host? I was looking around github but it seems like there are multiple.

.env Question

What do you mean by SENTRY_URI key. I didnt get that thing at all. I was digging into the code.

Feature Request - Log the following events

• Emojis If I may ask, what exactly is broken about the emojis module?
• Log Profile Picture Changes - Opt in for administrators and members so it doesn't clog big servers and user's consent is respected
• Monitor stream start/stop, possibly with duration and quality/framerate
• Discord Audit Log seems to show who moved a user to a voice channel. Is this in the audit log API which the bot uses? if so, please add "who move who to what voice channel" feature
  

Message delete log is not working

Bug fix and feature request: Fix the guildUpdate event

Bug: When I change the server icon of a server, the bot does not specify what exactly changed, it only says "unknown". this is detrimental as, in my server the icon changes frequently and I need to keep track of it.

Feature request: while the aforementioned behavior is obviously unintended, I think a good feature would be to show a larger embed with the newly changed server icon.

[Tutorial] Running on Docker with Docker-Compose

Hey everyone,

Here is a docker compose file.

The bot works perfectly with it. If you want to set it up quickly.

Please create the following folders
logger
bezerk

Clone logger to /logger/
Clone bezerk to /bezerz/.

After that you can run docker-compose up -d without any problems.
Run node src/miscellaneous/generateDB.js before the first start & adjust the .env.

version: "2"
services:
  cache:
    image: redis:6.2-alpine
    restart: always
    command: redis-server --save 20 1 --loglevel warning
    volumes: 
      - ./cache:/data
  node:
    image: "node:18"
    user: "node"
    working_dir: /home/node/app
    environment:
      - NODE_ENV=production
    volumes:
      - ./logger:/home/node/app
    command: "node index.js"
    depends_on:
      - cache
      - node2
      - db
  node2:
    image: "node:18"
    user: "node"
    working_dir: /home/node/app
    environment:
      - NODE_ENV=production
    volumes:
      - ./bezerk:/home/node/app
    command: "node index.js"
  db:
    image: postgres
    restart: always
    shm_size: 128mb
    volumes:
      - ./postgresql:/var/lib/postgresql/data
    environment:
      POSTGRES_PASSWORD: "YOurPassWoRd"

Wrong "Invite Used" - Logger Takes Most Recent Invite and Applies it as the Invite Used

Logger uses the most recent invite created as the "Invite Used" when creating the info card for a new member. Oftentimes, this is not correct.