I have a feature request to allow to monitor for web page changes. This can be an interesting thing to discover website defacements or
This could be implemented (relatively) easily in a multi-stepped approach and with almost no impact on database levels.
Today the web monitoring provides the following items you can create triggers on:
- Download speed for scenario
- Download speed for step of scenario
- Failed step of scenario
- Last error message of scenario
- Response code for step of scenario
- Response time for step of scenario
Step 1:
A thing that could be added is the checksum of the HTTP response body, per step.
This would allow the creation of a trigger that alerts when the page content has changed.
So you could call this "Checksum for step "XXX" of scenario "YYY".
Step 2:
Allow the user to create (multiple) regular expressions to substitute/delete data from the webpage, and then take the checksum.
This would allow the user to remove dynamic sections like dates, news blocks and such.
Step 3:
Allow the user to store the whole webpage in the database, but also allow a configurable amount of days to keep it stored. (a multiple of the check frequency for example)
Normal "items" have this configurable option (History storage period) , but not web scenarios I believe.
When a difference is found, store the difference somewhere and allow it to be included in the problem and email notification.
Thank you very much for considering this feature request.
Christophe
This could be implemented (relatively) easily in a multi-stepped approach and with almost no impact on database levels.
Today the web monitoring provides the following items you can create triggers on:
- Download speed for scenario
- Download speed for step of scenario
- Failed step of scenario
- Last error message of scenario
- Response code for step of scenario
- Response time for step of scenario
Step 1:
A thing that could be added is the checksum of the HTTP response body, per step.
This would allow the creation of a trigger that alerts when the page content has changed.
So you could call this "Checksum for step "XXX" of scenario "YYY".
Step 2:
Allow the user to create (multiple) regular expressions to substitute/delete data from the webpage, and then take the checksum.
This would allow the user to remove dynamic sections like dates, news blocks and such.
Step 3:
Allow the user to store the whole webpage in the database, but also allow a configurable amount of days to keep it stored. (a multiple of the check frequency for example)
Normal "items" have this configurable option (History storage period) , but not web scenarios I believe.
When a difference is found, store the difference somewhere and allow it to be included in the problem and email notification.
Thank you very much for considering this feature request.
Christophe
Comment