Heartbeat: HTTP check with dynamic url prameter

Elastic Stack Beats
1

Hi,

we´re trying to have some kind of dynamic parameter in the monitored URL in order to prevent the existing cache infrastructure deliver the response. We need to check the underlying infrastructure and not the cache.

I've tried to export an OS environment variable (which is kept updated by cron) in the URL like
http://www.example.com/foo/bar?ts=${NOW}

But the heartbeat log shows the following error:
ERROR [reload] cfgfile/list.go:69 Unable to hash given config: error_text accessing '0.hosts' (source:'/etc/heartbeat/monitors.d/....

Any idea how to fix the error or implement such kind of functionality in a different manner?

Thanks in advance!

2

That is not something we currently support, but may come in the future in the form of scriptable API checks with our synthetics product. That's not something we are actively working on at the moment, but is something we would like to do in the medium to long-term.

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.