You are here

Home » API reference » Spam 6

DEVELOPER.txt in Spam 6 

This document will currently serve as a catch-all for developer best practices, for both Spam core and API usage.
----

Spam logging guidelines
-----------------------

Per issue #532158.

A starting recommendation of items that should be logged, and at what level:

SPAM_LOG
* content marked as spam by spam.module, with final score
* content marked as spam or not-spam by user
* any "this is never supposed to happen" errors (as they're probably indicative of a bug)

SPAM_VERBOSE
* content marked as not-spam by spam module, with final score
* individual filters indicating spam, with scores

SPAM_DEBUG
* individual filters calculating all content score
* any internal processes that would be handy to expose for debugging

File

DEVELOPER.txt
View source 
  1. This document will currently serve as a catch-all for developer best practices, for both Spam core and API usage.

  2. ----

  3. 

  4. Spam logging guidelines

  5. -----------------------

  6. 

  7. Per issue #532158.

  8. 

  9. A starting recommendation of items that should be logged, and at what level:

  10. 

  11. SPAM_LOG

  12. * content marked as spam by spam.module, with final score

  13. * content marked as spam or not-spam by user

  14. * any "this is never supposed to happen" errors (as they're probably indicative of a bug)

  15. 

  16. SPAM_VERBOSE

  17. * content marked as not-spam by spam module, with final score

  18. * individual filters indicating spam, with scores

  19. 

  20. SPAM_DEBUG

  21. * individual filters calculating all content score

  22. * any internal processes that would be handy to expose for debugging