More actions
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
::*Multitail | ::*Multitail | ||
::*...Others like Logtail require some more tweaking for proper integration. | ::*...Others like Logtail require some more tweaking for proper integration. | ||
:*These modern monitoring tools are crazy good. Easy to access and use. However... | ::*These modern monitoring tools are crazy good. Easy to access and use. However... | ||
:*Due to the way they expose sensitive server information they won't be publicly accessible. | ::*Due to the way they expose sensitive server information they won't be publicly accessible. | ||
:*These help me keep track of resource hogs, identify traffic anomalies and more effectively assess incident reports (if and when). | ::*These help me keep track of resource hogs, identify traffic anomalies and more effectively assess incident reports (if and when). | ||
; 3-22 notes | ; 3-22 notes | ||
# Pivoted away from [https://dashy.to/ Dashy] before even starting (an absurd amount of vulnerabilities wrapped in one npm install package!) | # Pivoted away from [https://dashy.to/ Dashy] before even starting (an absurd amount of vulnerabilities wrapped in one npm install package!) | ||
Revision as of 00:47, 24 March 2025
Maintenance Log
- Revised Extensions list
- Adoption of two dashboards for stronger internal monitoring:
-
- atop/htop (We love the terminal!)
- Fail2Ban
- Logwatch
- Multitail
- ...Others like Logtail require some more tweaking for proper integration.
- These modern monitoring tools are crazy good. Easy to access and use. However...
- Due to the way they expose sensitive server information they won't be publicly accessible.
- These help me keep track of resource hogs, identify traffic anomalies and more effectively assess incident reports (if and when).
- 3-22 notes
- Pivoted away from Dashy before even starting (an absurd amount of vulnerabilities wrapped in one npm install package!)
- Orienting towards a simpler, custom-fit dashboard to combine all metrics (including curated Netdata and GoAccess outputs), logs and wiki activity / recent changes.
- Automated the aforementioned to my needs. All internal services have consistent albeit basic access and archival methods in place.
- Created a collection of scripts for managing the dashboards, recording metrics & storing the logs (securely).
- Three external monitors
- DigitalOcean (Host) - Various opt-in metrics, notifications and a responsive support team.
- BetterStack More granular at free tier than UptimeRobot.
- UptimeRobot Most basic monitor for sanity checking. Minimal offerings at free tier.
- For me, this covers the level of redundancy and monitoring I'm looking for. It covers both internal and external services, allows parity checking, comparison and historic logs I can review over time.
- SEO Updates:
- Indexing! The site is now appropriately being crawled. (3-18)
- Sitemap accepted, robots happy, on-site adjustments to follow. (3-18<)
- Fixed incorrect certificate call at "www.kenshidb.wiki" which was returning 403 and a bad handshake warning. Revoked previously generated certificate for Netdata during proxy server testing, allowing for...
- Creation of redirect for "www.kenshidb.wiki" to appropriately present "https://kenshidb.wiki/w/Main_Page".
- In so doing fixed the Google listing for "www.kenshidb.wiki" which now correctly paths to the frontpage of the website and does not crawl as a 403.
- Inquiries to and conversations with...
- DigitalOcean - Particulars about metrics, extra firewall tweaks, load balancing, etc. Their docs are decent, their support actually answers.
- Talks ongoing from 3-21 to 3-23. Essentially finished.
- MediaWikifolks - MediaWiki 1.44, Parsoid status, Extension updates, Extension depreciation, ideal package & library versions, etc.
Project:Updates not to be neglected -- I'll be organizing the Gadgets, Widgets, Modules & Extensions lists for that (ideally 3-23).