Testing and Vetting Web Data Connectors
This topic includes some suggestions for testing and vetting web data connectors.
Examine the source
https://) to reference external libraries (if the source site supports HTTPS) to help verify the site's authenticity.
To the extent possible, make sure you understand what the code is doing. In particular, try to understand how the code is constructing requests to external sites, and what information is being sent in the request.
Test the web data connector in an isolated environment
If possible, test the web data connector in an environment that is isolated from your production environment and from user computers. For example, add a web data connector to a safe list on a test computer or virtual machine that's running a version of Tableau Server that is not used for production.
Monitor the traffic created by the web data connector
When you test a web data connector, use a tool like Fiddler(Link opens in a new window), Charles HTTP proxy(Link opens in a new window) or Wireshark(Link opens in a new window) to examine the requests and responses that the connector makes. Make sure that you understand what sites the connector makes requests to and what content the connector is requesting. Similarly, examine the responses and their content to be sure that the connector is not reading data or code that is not directly related to the connector's purpose.
Test the performance and resource usage of the web data connector
When you test a web data connector, use tools to monitor its CPU and memory usage. Remember that the web data connector will run on Tableau Server, which is an environment in which many processes are already running. You want to make sure that when the connector fetches data, the connector does not have an undue impact on server performance.
Check whether the connector writes to disk. If it does, check how much disk space it occupies, and examine the output to make sure you understand what it's writing and why.