More actions
No edit summary |
No edit summary |
||
| Line 30: | Line 30: | ||
# Created a collection of scripts for managing the dashboards, recording metrics & storing the logs (securely). | # Created a collection of scripts for managing the dashboards, recording metrics & storing the logs (securely). | ||
# Submitted a support ticket to DigitalOcean to inquire about a correct firewall configuration tunneling and cached-based connections will work along with regular traffic to the site. | # Submitted a support ticket to DigitalOcean to inquire about a correct firewall configuration tunneling and cached-based connections will work along with regular traffic to the site. | ||
;3-22 notes | |||
# Added Fail2Ban, Logwatch & Multitail for increased logging activity. | |||
# Pivoted away from Dashy before even starting (and absurd amount of vulnerabilities wrapped in one npm install package!) | |||
# Orienting towards a simpler, custom-fit dashboard to combine all metrics, 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. | |||
# External services are next on the list. I'll be retaining BetterStack, expanding DigitalOcean's role (somewhat) and looking into UptimeRobot. | |||
# 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. | |||
# In talks with DigitalOcean to align all aspects of the firewall such that it doesn't affect any services now or planned. Being diligent about this one. | |||
---- | ---- | ||
[[Project:Updates]] not to be neglected -- I'll be organizing the Gadgets, Widgets, Modules & Extensions lists for that (ideally 3-23). | [[Project:Updates]] not to be neglected -- I'll be organizing the Gadgets, Widgets, Modules & Extensions lists for that (ideally 3-23). | ||
---- | ---- | ||
Revision as of 04:59, 23 March 2025
Maintenance Log
- Return to the main page or
- Return to the Maintenance Index
- As of 3-18-25
- Plans
- Revised extensions list
- Documentation (with pictures and examples) imported
- Numerous server-side automations
- Adoption of two dashboards for stronger internal monitoring:
- Netdata (Works perfectly! Customizing... 3-18)
- GoAccess (Also works perfectly! Even more customizing, Netdata is huge as is... 3-18)
- 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).
- Synchronizing these with my BetterStack configuration (should) cover most ends in this regard. Surely there's more to be done...
- Fiddling with various SEO-oriented aspects -> GoogleSearchConsole
- Indexing! The site is now appropriately being crawled. (3-18)
- Sitemap accepted, robots happy, on-site adjustments to follow. (3-18<)
- Furtherance of server-sided security measures (we love the modern web)
- Inquiries to and conversations with...
- DigitalOcean - Particulars about metrics, extra firewall tweaks, load balancing, etc. Their docs are decent, their support actually answers.
- MediaWikifolks - MediaWiki 1.44, Parsoid status, Extension updates, Extension depreciation, ideal package & library versions, etc.
- Google - Rather, all site crawlers, the site's meta description, headers, so on and so forth. The Page Speeds tool is awesome!
- 3-21 notes
- 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.
- Created a collection of scripts for managing the dashboards, recording metrics & storing the logs (securely).
- Submitted a support ticket to DigitalOcean to inquire about a correct firewall configuration tunneling and cached-based connections will work along with regular traffic to the site.
- 3-22 notes
- Added Fail2Ban, Logwatch & Multitail for increased logging activity.
- Pivoted away from Dashy before even starting (and absurd amount of vulnerabilities wrapped in one npm install package!)
- Orienting towards a simpler, custom-fit dashboard to combine all metrics, 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.
- External services are next on the list. I'll be retaining BetterStack, expanding DigitalOcean's role (somewhat) and looking into UptimeRobot.
- 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.
- In talks with DigitalOcean to align all aspects of the firewall such that it doesn't affect any services now or planned. Being diligent about this one.
Project:Updates not to be neglected -- I'll be organizing the Gadgets, Widgets, Modules & Extensions lists for that (ideally 3-23).