Great! Thanks Andy

On Tue, May 2, 2017 at 11:49 AM, Andy LoPresto <[email protected]> wrote:

> Sorry, I replied before fixing my copy/paste. You want this line:
>
> <logger name="org.apache.nifi.processors.standard.InvokeHTTP"
> level="DEBUG"/>
>
> Andy LoPresto
> [email protected]
> *[email protected] <[email protected]>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On May 2, 2017, at 2:48 PM, Andy LoPresto <[email protected]> wrote:
>
> The request won’t be in the provenance data, but it is logged in DEBUG
> mode. You can enable this by adding the following line to your
> $NIFI_HOME/conf/logback.xml file:
>
> <logger name="org.apache.nifi.processors.standard.LogAttribute"
> level=“DEBUG"/>
>
> Then tail $NIFI_HOME/logs/nifi-app.log when you run the processor.
>
> Andy LoPresto
> [email protected]
> *[email protected] <[email protected]>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On May 2, 2017, at 2:19 PM, Frank Maritato <[email protected]>
> wrote:
>
> Is there any way, either through logs or through the provenance data,
> where I can see the entire HTTP request (including headers) that was sent
> by InvokeHTTP?
>
> I'm seeing a weird problem where the external API I'm calling gives me a
> slightly different result when I call it via curl vs when it's called
> through nifi's InvokeHttp processor.
>
> Thanks!
> --
> Frank Maritato
> Data Architect
>
>
>
>


-- 
Frank Maritato
Data Architect

Reply via email to