Thought it would be easy. Gave the monitor team the f=convert URL for
e3demo.xml to html. Modified the XML to say, "Tell mother I feel fine" (ok,
not really, but something like that in business speak) but for some reason
the monitor, which is allegedly watching for text on the results page,
false positives at least a couple of times a day. (It's on a 15 minute
cycle with a 5 minute allowed response time ... typically the page will
display in under a minute ... if we consume our processing threads, though,
it could conceivable take more.)
The monitor team is saying it is the fact that the page is generated, not
"plain html" that is likely the cause. This makes no sense to me if it's
just watching the resulting loaded page. But maybe my knowledge of the
subtleties of HTTP is lacking. So we're telling the monitor to watch for
the HTTP 200 Response code for now. They have suggested I modify the script
to do the conversion and report OK or FAIL depending on the outcome. Which
yeah uh huh like maybe I'll find time to look into.
Anyhow, was just wondering if anyone else has been down this path and can
share any experiences they might have had.
Publishing Engine 6.0 m010.
--
Paul Nagai
