If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to REGISTER before you can post. To start viewing messages, select the forum that you want to visit from the selection below.
Scenarios create checks that are commonly needed for web pages.
For example: Download speed, Failed connection, and response code.
To see the data a scenario is pulling in go to:
Monitoring >> Latest Data
Set the Group and/or Host to filter out every thing except that host.
You should see the Name of the scenario on the left with a plus sign. Click on that to expand it. There you can see the download speed, connection success or failure, and response code.
All you need are triggers to check the values of those items (No they don't show up under configuration...). Say for example your scenario is called Web (I know a bit generic). Combine the expression for the trigger like so:
Item key: Host:web.test.in[Web,,bps]
--> for the download speed
Now when you create a scenario put in the actual URL in the Steps. At least at first. When you start getting data then you can try the Macros instead. Especially, when you try to make this into a template.
You should try the example on this page at least once:
The items automatically created by web scenarios don't return strings.
The response data for Host:web.test.error[Web] would be just the numerical codes. 200, 300, 404, 504, etc.
Why is the string function available in the web scenario and you can't key off of it? That makes no sense. I was able to do this manually in 2.0.6 and now that feature is gone? That seems highly unlikely to me...
Before 2.2 was out, I was able to manually create a web scenario for each host, and create the items and triggers.... but now that functionality has been removed when one of the major feature enhancements of 2.2 is the so called "improved" web scenario method...
Can anyone tell me why in 2.2, I am unable to trigger off of a string? Was this feature removed? This is why I was waiting to upgrade to 2.2... This is very frustrating.
Comment