- result # Details [here](#result-tag-and-result_code-field)
### Result tag and Result_code field
Upon finishing polling the target server, the plugin registers the result of the operation in the `result` tag, and adds a numeric field called `result_code` corresponding with that tag value.
Upon finishing polling the target server, the plugin registers the result of the operation in the `result` tag, and adds a numeric field called `result_code` corresponding with that tag value.
This tag is used to expose network and plugin errors. HTTP errors are considered a sucessful connection by the plugin.
This tag is used to expose network and plugin errors. HTTP errors are considered a successful connection.
|Tag value |Corresponding field value|Description|
|Tag value |Corresponding field value|Description|
@@ -72,10 +70,9 @@ This tag is used to expose network and plugin errors. HTTP errors are considered
...
@@ -72,10 +70,9 @@ This tag is used to expose network and plugin errors. HTTP errors are considered
|timeout | 4 |The plugin timed out while awaiting the HTTP connection to complete|
|timeout | 4 |The plugin timed out while awaiting the HTTP connection to complete|
|dns_error | 5 |There was a DNS error while attempting to connect to the host|
|dns_error | 5 |There was a DNS error while attempting to connect to the host|
NOTE: The error codes are derived from the error object returned by the `net/http` Go library, so the accuracy of the errors depends on the handling of error states by the `net/http` Go library. **If a more detailed error report is required use the `log_network_errors` setting.**