Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The HTTP Client function enables communication with a third-party HTTP server. Using the functions, stream editors can control outgoing requests handling. This function supports REST API and also supports authentication via the OAuth 2.0 framework. The following HTTP Client functions are available in Usage Engine:

  • Collector

  • Processor

  • Forwarder

You can set the values for how the HTTP Client function would behave when communication with the third-party HTTP server, and specify the method of communication.

HTTP Client Forwarder

Select this Function to send data to the third-party HTTP server.

In addition to the steps mentioned in the Connection and Operational Settings, you can take the following optional steps to configure HTTP Client forwarder:

  • In Maximum number of parallel requests, specify the maximum number of parallel requests that can be handled simultaneously.  

  • You can toggle on the Retry on fail functionality, allowing the service to retry the operation when an error has occurred. You can specify the number of retries in the Number of retries box, where the retries will be attempted inside the dynamically adjusted period of retry time.

    Note!

    The maximum number of allowed retries is 12 and all retries will be attempted in a total span of approximately 68 minutes.


    Use Case Scenario

    The Retry on fail functionality can be used when servers respond with error codes such as 500 or 503 due to intermittent server issues. The retry on fail option allows users to retry sending the requests a set number of times. This is only useful for 5xx error codes.


  • You can choose to either Ignore or Stop the stream when an error is detected.  


  • No labels