Identify the records from input message for a failure output record

Hi All

I am running multiple pipelines in the 5.x instance. All the logs are getting accumulated in log file.
This is well and good.
There are scenarios where pipeline is not bringing records from input to output. The reason for this is either wrong data in csv,email server down etc.

But for each data source, i am missing some records to output.
So how should i identify from the log file for which conf file records is missing for out put

In the below example my output email is having wrong password,

1 .how can i identify that this has happened for which pipeline as everything is going to same log file

Also in some cases my output is http, in those cases either my URL is wrong or the syntax is wrong. In those cases also how to identify which pipeline has cause this issue.

2. I also want to identify which records is getting missed in output. For example the input will read the data from source but when it comes to output it logs an error in logs. But how to identify this particular log message is for which record in source?

My Example Conf file is this

	file {
	      path => ".....csv"
		  sincedb_path => ""
          start_position => "beginning"
          type => "excel"
filter {
			csv {
			columns => ["date1","value1","cumvalue"]
			separator => ","


output {
email {
  to => "abc"
  body => "Testing the Email Body"
  address => ""
  port => xxx
  username => ""
  password => "welcome123"
  use_tls => true

I have tried the following

  1. Add a new field to capture the error as mutate filter. But for output failure one this event does not create

  2. I also tried adding "tags" in input, for this also the message which is having errors does not create events in output which is correct but does not show up the reason in the log file

How should i trace the above two reason. Any suggestions?

Did anyone face this issue? I think this the common question for pipeline development team

Hi @Christian_Dahlqvist , can you please suggest or throw some light, how should i move forward on this. I think is genuine requirement in this ecosystem. This is missing in the log file.

Do we have any ways wherein we can customize the log outputs? Or we can achieve this with the out of the box configuration?

To be more specific,from the below log message, how i will come to know this message is for which pipeline/conf file and if the error would have been for missing record then what was the input message/record which we read. This message is also there in log file, but there is no relationship between input and output message in log file

	"level" : "ERROR",
	"loggerName" : "",
	"timeMillis" : 1545501968108,
	"thread" : "[main]>worker0",
	"logEvent" : {
		"message" : "Something happen while delivering an email",
		"exception" : {
			"metaClass" : {
				"metaClass" : {
					"metaClass" : {
						"exception" : "535-5.7.8 Username and Password not accepted. Learn more at\n"


Friendly bump

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.