Skip to content

Latest commit

 

History

History
75 lines (58 loc) · 1.94 KB

Logs.md

File metadata and controls

75 lines (58 loc) · 1.94 KB

Also see at this wiki right menu Webhooks:

  • Global Webhooks at Admin Panel, sends most board actions to webhook (chat, etc)
  • Per-board webhooks at Wekan board click hamburger menu => cog icon at right side of members => Board Settings / Webhooks, send actions of one board to some webhook

Enable more Wekan debug logs:

a) Snap: sudo snap set wekan debug='true' - but also notice that in Wekan v4.56 newer most mongo logs go to /dev/null on Snap

b) docker-compose.yml: DEBUG=true

c) start-wekan.sh: DEBUG=true

d) MongoDB logs docs

e) Logging all MongoDB queries, info from StackOverflow below:

$ mongo
MongoDB shell version: 2.4.9
connecting to: test
> use myDb
switched to db myDb
> db.getProfilingLevel()
0
> db.setProfilingLevel(2)
{ "was" : 0, "slowms" : 1, "ok" : 1 }
> db.getProfilingLevel()
2
> db.system.profile.find().pretty()

Source: http://docs.mongodb.org/manual/reference/method/db.setProfilingLevel/

db.setProfilingLevel(2) means "log all operations".

Wekan logs could be at syslog

Logs are at /var/log/syslog , like with:

sudo tail -f 1000 /var/log/syslog | less

Or:

Snap

All:

sudo snap logs wekan

Partial:

sudo snap logs wekan.wekan

sudo snap logs wekan.mongodb

sudo snap logs wekan.caddy

Docker

docker logs wekan-app

docker logs wekan-db

Sandstorm

When Wekan grain is open, click at top terminal icon, so then opens new window that shows logs

Additional logs