pm2-telegram-notification | Send server logs to a telegram group/chat

by shubhroshekhar JavaScript Version: 0.4.0 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | pm2-telegram-notification Summary

pm2-telegram-notification is a JavaScript library typically used in Nodejs applications. pm2-telegram-notification has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can install using 'npm i pm2-telegram-notification' or download it from GitHub, npm.

Send server logs to a telegram group/chat. works with pm2 process manager.

Support

Quality

Security

License

Reuse

Support

pm2-telegram-notification has a low active ecosystem.

It has 3 star(s) with 0 fork(s). There are 1 watchers for this library.

It had no major release in the last 12 months.

pm2-telegram-notification has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of pm2-telegram-notification is 0.4.0

Quality

pm2-telegram-notification has 0 bugs and 0 code smells.

Security

pm2-telegram-notification has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

pm2-telegram-notification code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

pm2-telegram-notification is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

pm2-telegram-notification releases are not available. You will need to build from source code and install.

Deployable package is available in npm.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi has reviewed pm2-telegram-notification and discovered the below as its top functions. This is intended to give you an instant insight into pm2-telegram-notification implemented functionality, and help decide if they suit your requirements.

Creates a debounceEngine

Get all kandi verified functions for this library.

pm2-telegram-notification Key Features

No Key Features are available at this moment for pm2-telegram-notification.

pm2-telegram-notification Examples and Code Snippets

No Code Snippets are available at this moment for pm2-telegram-notification.

Community Discussions

No Community Discussions are available at this moment for pm2-telegram-notification.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install pm2-telegram-notification

create a telegram bot link
add that bot to a group if you want to send logs to a group
get chat_id to get chat_id use https://api.telegram.org/bot<BOT_TOKEN>/getUpdates api
if its a group chat id append g-. group chat CHAT_ID = 123456 -> g-123456. personal chat CHAT_ID = 123456 -> 123456.
install pm2-telegram-notification -- pm2 install pm2-telegram-notification
configure bot token -- pm2 set pm2-telegram-notification:bot_token BOT_TOKEN
configure chat id -- pm2 set pm2-telegram-notification:chat_id CHAT_ID if its a group chat id append g- eg: group chat CHAT_ID = 123456 -> g-123456 personal chat CHAT_ID = 123456 -> 123456
configure server name (optional) --pm2 set pm2-telegram-notification:server_name SERVER_NAME
configure lifecycle (optional) default: true --pm2 set pm2-telegram-notification:lifecycle (true/false)
configure error (optional) default: true --pm2 set pm2-telegram-notification:error (true/false)
configure error_log (optional) default: true --pm2 set pm2-telegram-notification:error_log (true/false)
server_name = name of the server
bot_token = token generated with telegram as suggested in 'Telegram setup section'
chat_id = identifier corresponding to particular group or personal chat on which the notifications are expected to be posted, as explained in 'Telegram setup section'
lifecycle = enabled alerts for lifecycle event handlers exposed by pm2, default is true
error = enabled alerts for error handlers exposed by pm2, default is true
error_log = flag configuration to truncate log with ref-id above 3500 characters with a trace in logs annotated with that ref-id, default is true
violation_time = time interval gap in which if another alerts occurs is said to count as violation, default is 10000
violation_count = violation count limit after which the notification is delayed with debounce time, default is 8
debounce = delay/debounce time applied in milliseconds to notification in case if violation count limit is reached, default is 30000

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: