Jump to: navigation, search

GVP MCP:vxmli:detailed fetch error-enable

(Created page with "{{OptionCreate |component=GVP_MCP |compshort=GVP_MCP |prodshort=GVP |section=vxmli |parameter=detailed_fetch_error.enable |configobject=Application }} {{PubOption |hidden=No }...")
 
Line 1: Line 1:
 +
{{PubOption}}
 +
{{DraftOption
 +
|hidden=false
 +
|default=false
 +
|valid=Choose between: true or false
 +
|takeseffect=At start/restart
 +
|shortdesc=Specifies whether a more detailed fetch error should be generated. If enabled, a different error id and trap is generated for fetching errors of type 4xx, all other fetching errors will be handled as usual. In addition, the CallId is included to all fetching error log message.
 +
}}
 +
{{PubExtended}}
 +
{{DraftExtended}}
 
{{OptionCreate
 
{{OptionCreate
 
|component=GVP_MCP
 
|component=GVP_MCP
Line 6: Line 16:
 
|parameter=detailed_fetch_error.enable
 
|parameter=detailed_fetch_error.enable
 
|configobject=Application
 
|configobject=Application
−
}}
 
−
{{PubOption
 
−
|hidden=No
 
−
}}
 
−
{{DraftOption
 
−
|hidden=false
 
 
}}
 
}}

Revision as of 13:32, January 17, 2018


View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

detailed_fetch_error.enable

Default Value: false
Valid Values: Choose between: true or false
Changes Take Effect: At start/restart


Specifies whether a more detailed fetch error should be generated. If enabled, a different error id and trap is generated for fetching errors of type 4xx, all other fetching errors will be handled as usual. In addition, the CallId is included to all fetching error log message.

Draft Option

No draft option


Comments or questions about this documentation? Contact us for support!