Monitoring Splunk

Website Monitoring App - No Data After Changing URLs

swhittier
Engager

I installed the Website Monitoring App v2.7 and completed the setup. After that I changed the index to point to "website_monitors" then created my first URL input. When I created the URL I set it up as 'https://sitename.com'. I didn't realize the site doesn't work if I don't include the 'www' so I removed the input and created a new one as 'https://www.sitename.com'.

  • When I look at the dashboards all I see is failed connections for the original URL.
  • If I go to Status Overview and filter it to "Include on enabled inputs" it says "No results found".
  • If I open Search and search for those 2 URLs using index = "website_monitors" I am able to find both URLs with the original failed URL generating no data since I removed it yesterday ~5:00 PM and the new URL generating since then and running right up until now.

Any idea why the dashboards aren't populating the data?

Tags (1)

swhittier
Engager

Some additional notes about this issue.

I ran a search 'sourcetype=web_ping' and it shows no data in the last 24 hours. So I ran a search 'index="website_monitors" url=https://www.sitename.com' to see if there was anything in the index for the new URL. I see events every 5 minutes and up to date.

Oddly, I noted that below each event it shows the following extractions:

 host = SPLINDEX source = web_ping://Site sourcetype = web_ping

If 'sourcetype=web_ping' shows here how come it doesn't show if I search only on sourcetype=web_ping?

0 Karma
Get Updates on the Splunk Community!

Splunk Decoded: Service Maps vs Service Analyzer Tree View vs Flow Maps

It’s Monday morning, and your phone is buzzing with alert escalations – your customer-facing portal is running ...

What’s New in Splunk Observability – September 2025

What's NewWe are excited to announce the latest enhancements to Splunk Observability, designed to help ITOps ...

Fun with Regular Expression - multiples of nine

Fun with Regular Expression - multiples of nineThis challenge was first posted on Slack #regex channel ...