Hello,
Just want to ask, if we already setup synthetic monitoring browser journey, do we still need HTTP type to monitor?
Does the browser monitoring sufficient enough as I believe it able to capture http error also.
Thanks
Hello,
Just want to ask, if we already setup synthetic monitoring browser journey, do we still need HTTP type to monitor?
Does the browser monitoring sufficient enough as I believe it able to capture http error also.
Thanks
Hello Siti,
You don't need to, but they make sens together:
Normally, a browser journey contains multiple steps in the application, so it can take a longer time to execute them and they produce more load on the server. Therefore, you may want to run the journey only every X minutes or so.
The HTTP monitor on the other hand only does one call to the application, which means it is fast and only produces minimal load. Therefore, you can run this monitor every minute to detect any availability issues faster.
Best regards
Wolfram
Hello @Wolfram_Haussig ,
Thank you for your reply.
I see then, because we have a lot of synthetic monitor and for one application it seems like we create both browser journey and http.
I try to manage on the consumption perspective and to see if by creating browser only is sufficient enough and we don't really need on the http area.
Need your advise on this, thank you!
I am sorry, this is something you need to decide on yourself - I can only provide the guidelines above.
If you are happy with the interval and the performance impact of the browser monitors you do not need the HTTP monitors.
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.