in_http plugin & logging

[Shefal...@teamaol.com]

Hello,

We are trying out Fluentd for one of our projects. We have in_http plugin as input and out_s3 as output plugin.

So the the source system POSTS by https we have the endpoint behind AWS ELB.  

The source system is telling us that are running into HTTP 500 errors but we don;t see anything on ELB side and we have also done everything on our side

http://docs.fluentd.org/v0.12/articles/logging as per the documentation but we cannot see anything in logs.

Note : This is a very small load test we are talking about 10 message/second.

Has anyone experience a similar issue or is that better way to get more of the logging in Fluentd ?

Thank you

Regards,

Shefali.

[Mr. Fiber]

> we cannot see anything in logs.

Could you see error message from in_http?

https://github.com/fluent/fluentd/blob/423cf7f9cf27950d89e7814fb3039b027b501924/lib/fluent/plugin/in_http.rb#L198

in_http returns 500 or 400 error including error cause.

#{$!} refers the error.

Masahiro

--
You received this message because you are subscribed to the Google Groups "Fluentd Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fluentd+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Shefal...@teamaol.com]

No that is what is puzzling us. We have not seen anything in fluentd logs !!

The source system & fluentd are both in AWS us-east-1 just different vpc as they are different aws accounts within our company.

Thank you.

Regards,

Shefali.

[Shefal...@teamaol.com]

Hello,

This is what is puzzling us. We don;t see any errors with Fluentd .

Both the source system ( which is doing HTTPS post)  and fluentd are in AWS us-east-1 expect that both are on different vpc as both are different AWS accounts within our company.

Thank you.

Regards,

Shefali.

On Tuesday, April 11, 2017 at 5:03:56 PM UTC-4, shefal...@teamaol.com wrote:

[Mr. Fiber]

> No that is what is puzzling us. We have not seen anything in fluentd logs !!

I mean in_http response, not fluentd logs.

--