Sponsored Content
Top Forums Web Development Notes with Ravinder on Badging System Development Part II Post 303028304 by Neo on Friday 4th of January 2019 01:48:23 AM
Old 01-04-2019
Alerts:

OK I have come up with an easy way to implement alerts when the badge beta is done.

Will take the array of badge colors and convert that array to a JSON string and then take the cryptographic hash of that string and store that string in the user table.

Then it is easy to check when a new threshold badge has been reached without tracking values that change often.

Then when the state changes .. will issue a simple dismissable Bootstrap alert which states the user has a new badge but not the actual badge (in first beta) and will have a link to the badge page.

Later will add the actual details of the status changes to the alert message.
 

3 More Discussions You Might Find Interesting

1. What is on Your Mind?

New Badging System - Badges Prototype Beta 1 (Badges Only)

Today I mapped out the new badging system using FA icons, Beta 1 in no particular order except a 6 x 8 grid: https://www.unix.com/members/1-albums215-picture991.png The prototype HTML code for this layout: <style> .fa-badge-grid { font-size: 1.5em; } .row { ... (38 Replies)
Discussion started by: Neo
38 Replies

2. What is on Your Mind?

Status of Badging System - Beta 1

Dear All, Here is the current status of the badging system: The Beta 1 phase of the new badging system is close to completion. 42 prototype badges have been "allocated" 6 prototype badge slots are held in reserve The "alert you have new badges" prototype is running and is currently... (4 Replies)
Discussion started by: Neo
4 Replies

3. What is on Your Mind?

Badging System: UNIX.COM Bug Hunter Badge (New)

I have moved the bug badge out of reserve and into the main stream. Basically, I will assign a color level like the others, based on who has made a good actionable bug report for UNIX.COM. "Good" means screenshots, links, and even details from web dev tools our the HTML source code. So far,... (0 Replies)
Discussion started by: Neo
0 Replies
NAGIRCBOT(1)						      General Commands Manual						      NAGIRCBOT(1)

NAME
nagircbot - announce Nagios status to an IRC channel SYNOPSIS
nagircbot [-CdeHmRStxX] [-A REGEX] [-c CHANNEL] [-f FILE] [-F HOST[:PORT]] [-i INTERVAL] [-I INTERVAL] [-k KEYWORD] [-n NICK] [-N PREFIX] [-p PASSWORD] [-P FILE] [-s HOST[:PORT]] [-T LIST] [-u USERNAME] [-U NAME] [-z USER] DESCRIPTION
nagircbot is an IRC bot that reads Nagios' status information and emits alerts to an IRC channel. It can filter alerts based on severity (CRITICAL, HARD, SOFT, and/or UNKNOWN) or by regular expression. It can connect to IRC servers protected by password or SSL, and can optionally set the topic to the current Nagios status. OPTIONS
-A REGEX Filter (omit) lines that match a basic regular expression. -c CHANNEL Channel to connect to, including the leading "#" (default: "#nagircbot"). -C Use colors in IRC messages. -d Do not fork into the background. -e Use encryption (SSL) when connecting to the IRC server. -f FILE Path to Nagios' status.log, indicated by the 'status_file' parameter in nagios.cfg (default: "/usr/local/nagios/var/status.log"). -F HOST[:PORT] Retrieve status.log over the network. If no port is specified, the default is 33333. -H Only announce alerts in 'HARD' state. This is the default. -i INTERVAL Nagios alert check interval, in seconds (default: 60). -I INTERVAL How often to announce Nagios global status in the channel, in seconds. Specify an interval of 0 (the default) to disable. Do not specify an interval smaller than the alert check (-i) interval. -k KEYWORD Keyword for the channel (default: no keyword). -m Display status information for an alert in separate IRC messages instead of combining on a single message. -n NICK IRC nick to use (default: "nagircbot"). -N PREFIX Prefix for all in-channel IRC messages. -p PASSWORD IRC server password. -P FILE Write PID file. -R Only announce CRITICAL/UNKNOWN alerts. -s HOST[:PORT] IRC server to connect to. If not specified, the default is "localhost:6667". If no port is specified, the default is 33333. -S Also announce alerts in 'SOFT' state. -t Set the channel topic to an alert summary. -T LIST Enable checks to see if Nagios is still running. Send 'check' in a private message to invoke the check. Accepts a comma-seperated list (without spaces) with the following elements: max_time_last_host_update, max_time_oldest_host_update, max_time_last_host_check, max_time_oldest_host_check, max_time_last_service_check, max_time_oldest_service_check, and max_time_oldest_next_service_check. -u USERNAME Username to log into the IRC server as. -U NAME IRC "real" or full name (default: "nagircbot"). -x status.log is in Nagios 1.0 format. -X status.log is in Nagios 2.0/3.0 format. This is the default. -z USER User to run as. AUTHOR
nagircbot was written by Folkert van Heusden <folkert@vanheusden.com>. This manual page was written by John Morrissey <jwm@horde.net>, for the Debian project (and may be used by others). December 13, 2010 NAGIRCBOT(1)
All times are GMT -4. The time now is 06:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy