adriankumpf / logger-telegram-backend

A logger backend for Telegram

LoggerTelegramBackend

A logger backend for Telegram.

Installation

Add :logger_telegram_backend and :finch to your list of dependencies in mix.exs:

def deps do
  [
    {:logger_telegram_backend, "~> 3.0"},
    {:finch, "~> 0.16"},
  ]
end

Add the backend

In your Application.start/2 callback, add the LoggerTelegramBackend:

@impl true
def start(_type, _args) do
  LoggerTelegramBackend.attach()

  # ...
end

Add the following to your configuration:

config :logger, LoggerTelegramBackend,
  chat_id: "your_chat_id",
  token: "yout_bot_token"

To create a Telegram bot, see the next section.

Configure the Telegram bot

To create a Telegram bot, follow the instructions here and get the token for the bot.

Then send a message to the bot and get your chat_id:

TOKEN="your_bot_token"
curl https://api.telegram.org/bot$TOKEN/getUpdates

License

This project is Licensed under the MIT License.

logger-telegram-backend's Issues

Logging not working when using a remote console

I'm a bit puzzled about this: if I release an app with mix distillery.release and start it with _build/dev/rel/testapp/bin/testapp console, Logger.error("test") will correctly result in the bot sending a message. If I connect to the very same app by _build/dev/rel/testapp/bin/testapp remote_console, Logger.error("test") will result in an error:

[error] GenServer #PID<0.107.0> terminating
** (stop) {:EXIT, {{:badmatch, {:error, %Mint.TransportError{reason: :ssl_not_started}}}, [{LoggerTelegramBackend, :handle_event, 2, [file: 'lib/telegram_logger_backend.ex', line: 47]}, {:gen_event, :server_update, 4, [file: 'gen_event.erl', line: 577]}, {:gen_event, :server_notify, 4, [file: 'gen_event.erl', line: 559]}, {:gen_event, :handle_msg, 6, [file: 'gen_event.erl', line: 300]}, {:proc_lib, :init_p_do_apply, 3, [file: 'proc_lib.erl', line: 249]}]}}
Last message: {:gen_event_EXIT, LoggerTelegramBackend, {:EXIT, {{:badmatch, {:error, %Mint.TransportError{reason: :ssl_not_started}}}, [{LoggerTelegramBackend, :handle_event, 2, [file: 'lib/telegram_logger_backend.ex', line: 47]}, {:gen_event, :server_update, 4, [file: 'gen_event.erl', line: 577]}, {:gen_event, :server_notify, 4, [file: 'gen_event.erl', line: 559]}, {:gen_event, :handle_msg, 6, [file: 'gen_event.erl', line: 300]}, {:proc_lib, :init_p_do_apply, 3, [file: 'proc_lib.erl', line: 249]}]}}}

I tried to add :ssl to the extra_applications, to no avail. What could be the cause of such a behavior?

I attached a minimal app to test, just mix distillery.release and run it as I explained above

testapp 2.zip

Thanks!

unknown registry?

I think I need a little help with the configuration:

In config.ex, I have:

adapter: {Tesla.Adapter.Finch, name: LoggerTelegramBackend.Finch}

in application.ex:

{Finch, name: LoggerTelegramBackend.Finch} is one of the children

but when I start the app, I get:

[error] :gen_event handler LoggerTelegramBackend installed in Logger terminating
** (ArgumentError) unknown registry: LoggerTelegramBackend.Finch

what am I missing?

Thanks!

Avoid [error] GenServer terminating

In lib/telegram_logger_backend.ex:47 the match :ok = log_event(level, message, timestamp, metadata, state) can end up in the GenServer terminating in case the returned value is, for example, {:error, reason} instead of :ok, which is not necessarily bad, if I understand well how Mint works (also see elixir-mint/mint#211). Would it make sense to ignore the returned value?

Thanks