GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: Muhammad Rizki <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Muhammad Rizki <[email protected]>,
	Alviro Iskandar Setiawan <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>
Subject: [PATCH v1 05/15] telegram: logger: Initialize the configuration for the Telegram logger.
Date: Wed, 18 Jan 2023 05:12:06 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

This commit adds the configuration for the logger and sets the logger
level of other loggers, such as pyrogram, to the WARNING level. Changing
the level is to disable some of their log messages, so that only our bot
logs to the console.

Signed-off-by: Muhammad Rizki <[email protected]>
---
 daemon/tg.py | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/daemon/tg.py b/daemon/tg.py
index 6b2ec20..26f8374 100644
--- a/daemon/tg.py
+++ b/daemon/tg.py
@@ -14,6 +14,8 @@ from telegram.mailer import BotMutexes
 from telegram.mailer import Bot
 from logger import BotLogger
 import os
+import logging
+import logging.config
 
 
 def main():
@@ -22,6 +24,10 @@ def main():
 	logger = BotLogger()
 	logger.init()
 
+	logging.config.fileConfig("telegram/telegram.logger.conf")
+	logging.getLogger("apscheduler").setLevel(logging.WARNING)
+	logging.getLogger("pyrogram").setLevel(logging.WARNING)
+
 	client = DaemonTelegram(
 		"telegram/storage/EmailScraper",
 		api_id=int(os.getenv("API_ID")),
-- 
Muhammad Rizki


  parent reply	other threads:[~2023-01-17 22:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 22:12 [PATCH v1 00/15] Everything about logger changes and some fixes Muhammad Rizki
2023-01-17 22:12 ` [PATCH v1 01/15] telegram: Simplify code to get DB_PORT from env Muhammad Rizki
2023-01-17 22:12 ` [PATCH v1 02/15] discord: " Muhammad Rizki
2023-01-17 22:12 ` [PATCH v1 03/15] telegram: logger: Add a telegram.logger.conf Muhammad Rizki
2023-01-17 22:12 ` [PATCH v1 04/15] discord: logger: Add a discord.logger.conf Muhammad Rizki
2023-01-17 22:12 ` Muhammad Rizki [this message]
2023-01-17 22:12 ` [PATCH v1 06/15] discord: logger: Initialize the configuration for the Discord logger Muhammad Rizki
2023-01-17 22:12 ` [PATCH v1 07/15] telegram: fix: Fix the type annoations for the decorator Muhammad Rizki
2023-01-17 22:12 ` [PATCH v1 08/15] discord: cleanup: Remove some unnecessary comments Muhammad Rizki
2023-01-17 22:12 ` [PATCH v1 09/15] discord: fix: Fix the type annotations for the decorator Muhammad Rizki
2023-01-17 22:12 ` [PATCH v1 10/15] discord: typing: Add return type annotations Muhammad Rizki
2023-01-17 22:12 ` [PATCH v1 11/15] telegram: Implement DaemonException() and report_err() in scrape.py Muhammad Rizki
2023-01-17 22:12 ` [PATCH v1 12/15] utils: fix: Fix charset issue for get_decoded_payload() Muhammad Rizki
2023-01-17 22:12 ` [PATCH v1 13/15] telegram: logger: Refactor all logging method Muhammad Rizki
2023-01-17 22:12 ` [PATCH v1 14/15] discord: Implement DaemonException and report_err in get_lore_mail.py Muhammad Rizki
2023-01-17 22:12 ` [PATCH v1 15/15] discord: logger: Refactor all logging method Muhammad Rizki
2023-01-17 23:10 ` [PATCH v1 00/15] Everything about logger changes and some fixes Ammar Faizi
2023-01-17 23:29   ` Muhammad Rizki
2023-01-17 23:31     ` Ammar Faizi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox