You can filter out logs from being recorded by modifying the ignore options on the dashboard.
By adding a role, user channel, etc. Quark will no longer log events including those attributes to the
logging channel. For example if user X deletes their own message or their message is deleted by
someone else and user X has been added to the ignore target users list, this event will not be logged.
A target is a user or an object in which an action is carried out on.
An executor is a user in which an action is carried out by.
To add a user to the ignore options, their user ID must be provided
Redirect logs to different channels
Logs can be setup to be sent to different channels, allowing logs to be more easily managed
and organised. They can be configured per log category by setting the channel in the dropdown
for the appropriate category on the dashboard. Alternatively, you can prevent categories of logs
entirely by disabling the switch.
You can use forum channels to keep all your logs in one place!
Bot integrations
Quark is designed to be compatible with other bots! Quark provides the option for native
PluralKit support to prevent Quark’s logs from being rendered useless.
Quark also has an API to allow further configuration to support your use case.
For serious servers, Quark Pro is essential! Quark Pro
makes sure you’ll never miss a thing that goes on in your server! Quark Pro can
be added to your server as a separate bot, alongside Quark to
provide backup logs as well as logging messages up to 8 weeks old and much more!
If the server has a Quark Pro subscription, both the normal Quark bot and Quark Pro bot will have Pro features enabled!