Synthetic Monitoring using proxy servers

[shinmaeng]

Hi, elastic staffs.

I have two questions about Synthetic installed in private network.
It can not call any outbound requests to the internet unless I do any network works.

1. I read the heartbeat document below about synthetic options.
   Browser options | Heartbeat Reference [7.14] | Elastic
   But, I didn't find the proxy_url option. Other types like http, tcp have the option that calls the proxy url instead of hosts.
   Can I apply the proxy_url option when using a browser type option?

2. As I said earlier, It can't call outbound requests to the internet now.
   When the synthetic monitoring agent call the url, it gets network timeout 30s.
   But, it judges "Up" count even though the request fails because of the network block.
   I want to know that the way to judge "Down" when I get the network timeout.

Thank you in advance!!

[Andrew_Cholakian1 (Andrew Cholakian)]

Apologies for the delay here. You can use a proxy server today by modifying the synthetics.config.ts file. I've posted an example below:

// note that `env` is the `env` argument passed to the synthetics program
// the default being `development`
export default (env): SyntheticsConfig => {
  const params: {[key: string]: any} = {};
  if (env === "production") {
    params.url = "https://elastic.github.io/synthetics-demo/"
  } else {
    const port = 8080;
    params.url = `http://localhost:${8080}`;
    params.devWebserver = {port};
  }
  return {params, playwrightOptions: {proxy: {server: "http://myproxy.example.net", username: "myuser", password: "mypass"}}};
};

I've also created an issue to support this via a CLI flag and heartbeat option since that would be more convenient in many cases.