Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Implementing logging instead of printing errors to the console #62

Closed
5 tasks done
Jordian0 opened this issue Oct 20, 2024 · 5 comments
Closed
5 tasks done

Comments

@Jordian0
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Feature Description

In the context of your Telegram bot, logging provides a way to capture important events, errors, and debugging information, helping you monitor and maintain the bot effectively

Use Case

Log when a user requests a conversion or checks a cryptocurrency price, allowing you to analyze usage patterns over time.

Benefits

When errors occur, logging allows you to capture the context in which they happened, making it easier to implement error recovery strategies.

Priority

Medium

Record

  • I agree to follow this project's Code of Conduct
  • I'm a GSSOC WOB24 contributor
  • I want to work on this issue
  • I'm willing to provide further clarification or assistance if needed.
Copy link

Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible.

@muhammedsafuvan
Copy link

can I work on this?

@Jordian0
Copy link
Author

I want to work on this task. I'm waiting for it to be assigned to me.

@Harish-2003
Copy link
Contributor

Any images?

@Jordian0
Copy link
Author

Jordian0 commented Nov 3, 2024

Not really

@Harish-2003 Harish-2003 closed this as not planned Won't fix, can't repro, duplicate, stale Nov 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants