Observability Project: Difference between revisions

Jump to navigation Jump to search
m
Line 24: Line 24:
* Reverse proxy in front of my current CV Wiki and to capture the traffic.  
* Reverse proxy in front of my current CV Wiki and to capture the traffic.  
* Log aggregator & event analyser to hold the data and start analysing it
* Log aggregator & event analyser to hold the data and start analysing it
==Plan/Backlog==
# Run a basic Express.js demo in a cloudlet node with a recent Node.js image [DONE]
# Implement access to it from my new `dirks.nz` domain, using encryption (https)  [DONE]
# Run Splunk in cloudlets  [In progress]
# Implement a reverse proxy using library from npm (for traffic to/from above Express.js demo)
# Create Splunk HEC (Http Event Collector) (check if config persists through redeploys)
# If needed, investigate data persistence through use of volumes from Docker <=> Cloudlet <=> Backup/Archive
# Send traffic events to Splunk HEC from Express demo (create indexes, set data retention policies, check data persistence through redeploys)
# Investigate if reverse proxy can be used for accessing Splunk instance UI, and consider recording splunk UI access logs
# Try implement auth in reverse proxy to require login before being able to access some URL paths (eg. Splunk UI)
# Implement MediaWiki in a cloudlet, and copy content from my existing cvwiki
# Route traffic to/from new cvwiki via reverse proxy, & log the traffic
# Create an UI Automation suite to test cvwiki using Playwright
# Run the above suite in cloudlet and record results to splunk
# Schedule the above cloudlet to run daily


=Technologies=
=Technologies=

Navigation menu