Overview documentation for what is domain/instance is monitored.

[ddebrunner]

For JobSource and MetricsSource there needs to be overview documentation as to how the JMX connection is setup using the operator parameters. At the moment each parameter is described individually and it's hard to figure out what needs to be setup to monitor something that is not the current instance.

• If domainId is not the domain of the instance running the operators:
  • thenconnectionUrl must be set, don't think this is clearly documented.
  • this mode may only be supported if running standalone which is a big limitation, not sure that's documented.
  • Not providing a filter document is broken (at least not useful with no warning) (see #123 ) if
  • domainId is not the domain of the instance running the JMX source operators
  • intended instance is not the instance running the JMX source

[ddebrunner]

Maybe sslOption is another parameter that is impacted by this, since the default is only set if the domainId is matching the current domain.

[ddebrunner]

At least having these common patterns documented with examples would be helpful.

1. Monitoring the same domain and instance as where the monitoring code is running.
2. Monitoring the same domain but different instance from the monitoring code is running.
3. Monitoring the a different domain and different instance from where the monitoring code is running.

Especially for Streaming Analytics, how do i get connectionURL, sslOption, domainid etc. in case 3.

[markheger]

• [ ] update iopages