Loading...
 
Skip to main content

Monitoring pre-dogfood servers

  • Tracker item actions
Trackers Items
Status
Open
Subject
Monitoring pre-dogfood servers
Version
12.x
Category
  • Community projects
  • Feature request
  • Indexing
Feature
Administration
Monitoring
Resolution status
New
Submitted by
Marc Laporte
Volunteered to solve
Marc Laporte
Lastmod by
Marc Laporte
Rating
(1)
Related-to
Description

Set-up monitoring for all our pre-dogfood servers for all the checks we have, but especially last successful re-index. If last successful re-index is more than x (ex.:3) days old, an email alert should be sent out.

Here is a real-world example of why having checks on all pre-dogfood servers would have made everything smoother. An unidentified commit in trunk is causing indexing to crash:
https://dev.tiki.org/item4609

If we had been warned by a pre-dogfood sever, we could have found the commit and fixed the problem a few days after it appearing.

Note that this type of crash can also happen with some data not yet supported by the indexer, and thus, it can happen at any time, not just on code changes. And with a broken index, a Tiki site can be in big trouble because it doesn't just skip over the problem, it just dies. We are fortunate to have tons of data on all the pre-dogfood servers.

Because of issue 4609, we are stuck with respect to testing Unified Search with MySQL in trunk. Once this is solved, maybe something else will be discovered, so we to know ASAP so it's stable enough for Tiki12. This is crucial as per Search Dilemma

Importance
10 high
Easy to solve?
9
Priority
90
Demonstrate Bug on Tiki 19+
Please demonstrate your bug on show2.tiki.org
Demonstrate Bug (older Tiki versions)
 Show.tiki.org is currently unavailable

Unable to connect to show.tikiwiki.org. Please let us know of the problem so that we can do something about it. Thanks.

Ticket ID
4678
Created
Wednesday 21 August, 2013 06:35:50 GMT-0000
by Marc Laporte
LastModif
Tuesday 20 July, 2021 01:30:42 GMT-0000