Web App Monitoring with Splunk/Jenkins

I want to tighten the end-to-end monitoring of several Linux-based web applications that sit behind AWS load balancers and talk to SQL back-ends as well as a few Windows Server-hosted services. We already collect logs in Splunk and run our CI/CD through Jenkins; what’s missing is a coherent, well-tuned monitoring layer that feeds actionable alerts into our incident-management process and supports fast root-cause analysis.

Here’s what I need from you:

• Map the full request flow of each public-facing URL, identify the key health indicators, and translate them into Splunk searches, dashboards, and alert rules.
• Integrate critical Jenkins pipeline events (build failures, test regressions, deployment status) so they surface in the same Splunk views.
• Define alert thresholds, escalation paths, and ITIL-aligned incident workflows that keep noise low while ensuring nothing critical is missed.
• Provide a short runbook and RCA template so future incidents are handled consistently.

Acceptance criteria
• New dashboards render in under 3 seconds and cover latency, error rate, throughput, resource use, and deployment status.
• All alerts fire only on actionable conditions; target is fewer than 2 false positives per week after the first month.
• Documentation is delivered in Markdown and reviewed with the team on a live screen-share.

If you’ve previously built Splunk apps, tuned Jenkins integrations, or automated monitoring on AWS, your expertise will be put to immediate use. I can grant access to a staging environment on day one so we can iterate quickly.