Loading...
 

tiki-check.php: make all these 50+ values available to Nagios/Icinga/Shinken

Status
Open
Subject
tiki-check.php: make all these 50+ values available to Nagios/Icinga/Shinken
Version
12.x
Category
  • Feature request
  • Dogfood on a *.tiki.org site
Feature
Monitoring
Resolution status
New
Submitted by
Marc Laporte
Volunteered to solve
Marc Laporte
Lastmod by
Nelson Ko
Rating
(0)
Related-to
Description

Use case 1:

  • Customer has his own hosting (ex: dedicated or shared hosting)
  • There is not just Tiki on that hosting
  • Tiki consultant doesn't really control the hosting. They may change config to suit another app or in an upgrade.
  • Tiki consultant sets up everything just nice thanks to Tiki Check
  • Several months go by, all is well. Tiki Consultant is a hero.
  • Hosting company (or someone else working on another app on the same server) proceeds to an upgrade/change without telling anyone
  • Several months go by, problems appear, there is dissatisfaction
  • Customer considers this as within the warranty and expects the Consultant to fix without extra charge
  • Tiki consultant feels: "hey, it worked when I left it"
  • Tiki consultant doesn't remember / have data on the previous config so can't explain the cause of the issues.
  • Customer thinks Tiki was perhaps not such a good idea, as it's not supporting data load and there are all kinds of quirks
  • Customer gets told, "why didn't you use system XYZ instead?"


In an alternate reality, Tiki Consultant sets up a Nagios/Icinga/Shinken instance to track all Tiki sites he has been associated with. Data is logged quietly in the background.

When an issue is reported, he can look at historical data and see what changed and have a clue. As a bonus, he can indicate to the customer that hosting company made changes to the server without advising anyone. Tiki Consultant is a hero (and can bill that time), and hosting company is not. If Nagios/Icinga/Shinken could alert the Tiki Consultant of changes, it would permit Tiki Consultant to review changes and to evaluate if there are any risks of issues.

Use case 2: run on all *.tiki.org sites to help reliability.

Use case 3: run on pre-dogfood servers and if we notice something went awry (ex: requires more RAM), we have a clear indication of which day the commit came in.
We have 50+ beautiful checks in tiki-check.php Surely it can't be hard to make them accessible to an outside monitoring system?

Solution

OK this task is kind of broad and unactionable, so I have broken it down into actionable sub-tasks. It is more of an ongoing thing anyway.

1) Document the state of testing going on tiki.org sites, collect historical information, and produce monthly report on pass/fail on various checks. (some of these checks might fail a lot of the time with no problem, but collecting the historical info is useful to tune the tests for future, notification can be disabled for most of these checks).

2) If possible, provide easy access to the monitoring dashboard for tiki.org sites.

3) Increase the number of checks on the Tiki.org sites. There is a scalability issue here - it might require more machines and changi's shinken setup might scale better than amette's icinga setup. Anyway, the more checks the better, even if it is to understand better how Tiki sites behave under various situations, in various measured parameters.

4) Organize TMIT webinar on "how did we setup a Tiki monitoring infra". Will invite all sysadmins to describe/present their setup. The idea is not to do an academic study on the umpteen ways to do such a thing but just to present what has been done.

I will create separate tasks for each of these

Importance
9
Easy to solve?
7
Priority
63
Demonstrate Bug (Tiki 19+)
Please demonstrate your bug on show2.tiki.org
 About show2.tiki.org

To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.

Version: Create show2.tiki.org instance
Demonstrate Bug (older Tiki versions)
Please demonstrate your bug on show.tikiwiki.org
 About show.tikiwiki.org

To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.

Version: Create show.tikiwiki.org instance
Ticket ID
4680
Created
Wednesday 21 August, 2013 07:21:13 GMT-0000
by Marc Laporte
LastModif
Tuesday 20 July, 2021 02:15:31 GMT-0000

Attachments

 filenamecreatedhitscommentversionfiletype 
2021-07-19_220647.png 20 Jul 21 02:15 GMT-00000


Keywords

The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.

Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.

Accessibility (WAI & 508)
Accounting
Administration
Ajax
Articles & Submissions
Backlinks
Banner
Batch
BigBlueButton audio/video/chat/screensharing
Blog
Bookmark
Browser Compatibility
Calendar
Category
Chat
Comment
Communication Center
Consistency
Contacts Address book
Contact us
Content template
Contribution
Cookie
Copyright
Credits
Custom Home (and Group Home Page)
Database MySQL - MyISAM
Database MySQL - InnoDB
Date and Time
Debugger Console
Diagram
Directory (of hyperlinks)
Documentation link from Tiki to doc.tiki.org (Help System)
Docs
DogFood
Draw -superseded by Diagram
Dynamic Content
Preferences
Dynamic Variable
External Authentication
FAQ
Featured links
Feeds (RSS)
File Gallery
Forum
Friendship Network (Community)
Gantt
Group
Groupmail
Help
History
Hotword
HTML Page
i18n (Multilingual, l10n, Babelfish)
Image Gallery
Import-Export
Install
Integrator
Interoperability
Inter-User Messages
InterTiki
jQuery
Kaltura video management
Kanban
Karma
Live Support
Logs (system & action)
Lost edit protection
Mail-in
Map
Menu
Meta Tag
Missing features
Visual Mapping
Mobile
Mods
Modules
MultiTiki
MyTiki
Newsletter
Notepad
OS independence (Non-Linux, Windows/IIS, Mac, BSD)
Organic Groups (Self-managed Teams)
Packages
Payment
PDF
Performance Speed / Load / Compression / Cache
Permission
Poll
Profiles
Quiz
Rating
Realname
Report
Revision Approval
Scheduler
Score
Search engine optimization (SEO)
Search
Security
Semantic links
Share
Shopping Cart
Shoutbox
Site Identity
Slideshow
Smarty Template
Social Networking
Spam protection (Anti-bot CATPCHA)
Spellcheck
Spreadsheet
Staging and Approval
Stats
Survey
Syntax Highlighter (Codemirror)
Tablesorter
Tags
Task
Tell a Friend
Terms and Conditions
Theme
TikiTests
Federated Timesheets
Token Access
Toolbar (Quicktags)
Tours
Trackers
TRIM
User Administration
User Files
User Menu
Watch
Webmail and Groupmail
WebServices
Wiki History, page rename, etc
Wiki plugins extends basic syntax
Wiki syntax text area, parser, etc
Wiki structure (book and table of content)
Workspace and perspectives
WYSIWTSN
WYSIWYCA
WYSIWYG
XMLRPC
XMPP




Useful Tools