MEIER-320: Filter health check logs/traces and add Cloudflare WAF scanner block#81
Merged
andymeierdev merged 3 commits intomainfrom Mar 24, 2026
Conversation
🍹
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two changes to reduce log noise and block vulnerability scanners at the edge.
1. Filter health check logs and traces (app)
In
Program.fs:UseSerilogRequestLoggingwith a customGetLevelthat drops/healthrequests toVerboselevel — below the configured minimum (Information), so they no longer appear in Seq or console output.FilteronAddAspNetCoreInstrumentationthat excludes/healthfrom generating OpenTelemetry trace spans sent to Seq.2. Cloudflare WAF custom rule for scanner blocking (Pulumi)
New
pulumi/src/cloudflare/waf.tscreates a WAF custom ruleset on theandymeier.devzone usingphase: "http_request_firewall_custom". A single rule blocks requests matching common vulnerability scanner paths and file extensions at the Cloudflare edge before they reach the origin:/.env,/.git/wp-*,/wordpress,/xmlrpc/phpMyAdmin,/phpmyadmin,/pma/cgi-bin,/actuator,/solr,/telescope,/vendor.php,.asp,.jsp,.cgiAction is
block(403 at edge, zero origin load).Validation
dotnet buildpasses with zero warnings/errors./fake.sh Test)pulumi previewshows only the newcloudflare:Rulesetresource to create