Project:Maintenance/032325: Difference between revisions
Information about Kenshi Wiki
More actions
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
:*[https://www.netdata.cloud/ Netdata] (Works perfectly! Customizing... 3-18) | :*[https://www.netdata.cloud/ Netdata] (Works perfectly! Customizing... 3-18) | ||
:*[https://goaccess.io/ GoAccess] (Also works perfectly! Even more customizing, Netdata is huge as is... 3-18) | :*[https://goaccess.io/ GoAccess] (Also works perfectly! Even more customizing, Netdata is huge as is... 3-18) | ||
::*These modern monitoring tools are crazy good. Easy to use | ::*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). | ||
::*Synchronizing these with my BetterStack configuration (should) cover most ends in this regard. Surely there's more to be done... | ::*Synchronizing these with my BetterStack configuration (should) cover most ends in this regard. Surely there's more to be done... | ||
Revision as of 02:41, 19 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
- Furtherance of server-sided security measures (we love the modern web)
- Inquiries to and conversations with...
- DigitalOcean, some MediaWikifolks & Google
Project:Updates not to be neglected -- I'll be organizing the Gadgets, Widgets, Modules & Extensions lists for that (ideally 3-23).