Serilog.Sinks.Telegram
0.1.2
See the version list below for details.
dotnet add package Serilog.Sinks.Telegram --version 0.1.2
NuGet\Install-Package Serilog.Sinks.Telegram -Version 0.1.2
<PackageReference Include="Serilog.Sinks.Telegram" Version="0.1.2" />
paket add Serilog.Sinks.Telegram --version 0.1.2
#r "nuget: Serilog.Sinks.Telegram, 0.1.2"
// Install Serilog.Sinks.Telegram as a Cake Addin #addin nuget:?package=Serilog.Sinks.Telegram&version=0.1.2 // Install Serilog.Sinks.Telegram as a Cake Tool #tool nuget:?package=Serilog.Sinks.Telegram&version=0.1.2
Serilog.Sinks.Telegram
Writes Serilog events to a given Telegram chat being it a private chat or a group.
Install
Install-Package Serilog.Sinks.Telegram
Note that a Telegram bot api key is required in order to configure the sink, if you don't know how the bot creation process works please refer to the official documentation.
Configuration
To configure the sink simply add "TeleSink" using the "WriteTo" method on the Serilog logger configuration.
new LoggerConfiguration()
.MinimumLevel.Information()
.WriteTo.TeleSink(
telegramApiKey:"my-bot-api-key",
telegramChatId:"the target chat id")
.CreateLogger();
Optionally a minimum log level can be specified:
new LoggerConfiguration()
.MinimumLevel.Information()
.WriteTo.TeleSink(
telegramApiKey:"my-bot-api-key",
telegramChatId:"the target chat id",
minimumLevel:LogEventLevel.Warning)
.CreateLogger();
Q.A.
How do i discover the chat id parameter?
Once your bot is created simply open a chat towards it (or include it into a group), then you can use the Telegram API to get the last updates for your bot:
curl -X GET \
https://api.telegram.org/bot<my-bot-api-key>/getUpdates \
-H 'Cache-Control: no-cache'
The response should report the last conversations your bot had along with their chat ids:
{
"ok": true,
"result": [
{
"update_id": 123456789,
"message": {
"message_id": 2,
"from": {
"id": 000000,
"is_bot": false,
"first_name": "XXX",
"last_name": "XXX",
"username": "XXX",
"language_code": "XX"
},
"chat": {
"id": 0000000,
"first_name": "XXX",
"last_name": "XXX",
"username": "XXX",
"type": "private"
},
"date": 1531306919,
"text": "hello dear bot!"
}
}
]
}
How can i run unit tests?
You need an api key and a chat id in order to run the unit tests. You can add them to the Configuration/TestConfig.json config file or (better solution) you can add another config file named /Configuration/TestConfig_private.json and use it to store you secrets. This is the preferred solution if you want to make a pull request or fork & push the code to another repo since that path is already ignored.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. |
.NET Core | netcoreapp1.0 was computed. netcoreapp1.1 was computed. netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard1.3 is compatible. netstandard1.4 was computed. netstandard1.5 was computed. netstandard1.6 was computed. netstandard2.0 was computed. netstandard2.1 was computed. |
.NET Framework | net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen30 was computed. tizen40 was computed. tizen60 was computed. |
Universal Windows Platform | uap was computed. uap10.0 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 1.3
- Flurl (>= 2.7.1)
- Flurl.Http (>= 2.3.2)
- NETStandard.Library (>= 1.6.1)
- Serilog (>= 2.7.1)
NuGet packages (7)
Showing the top 5 NuGet packages that depend on Serilog.Sinks.Telegram:
Package | Downloads |
---|---|
OKEService.EndPoints.Web
OK Micro Service EndPoints.Web Package |
|
Saapp.Framework.EndPoints.Web
Package Description |
|
BEFactoryBusinessLayer
After several years of developing Back End applications I decided to collect all the various scenarios in easily using all the famous libraries used for those who develop applications with Dependency Injection |
|
M.YZ.Basement.EndPoints.Web
Package Description |
|
ITomoLog
Package Description |
GitHub repositories
This package is not used by any popular GitHub repositories.