So now let's actually go back to our configuration and let's clean all this stuff up, let's remove
the tailing of all the containers we're not interested in and maybe all the health checks so we can
see a little bit more.
So let's edit the config map in here where it says for detailed health check, which is sending that
output to standard out of the console that we saw the container console.
We're going to send it to know basically we're just going to discard those health checks so we don't
see them in the logs.
And another thing we want to do is we want to provide here a path only to Java.
And no, we don't want to process logs from other containers so we can do it using a regular expression.
So instead of start the log, we're going to write minus if this will match Java minus F node minus
EBP and then log.
So this will basically only match our two applications, which means we don't need this exclusion because
it's excluded already by the first line.
And another thing that we can do is instead of forwarding it to an aggregator, we are going to send
it to a console output so we can actually see the logs as well.
So instead of forward, we're going to do a standard out.
This comment doesn't apply anymore and we can update again.
We have to restart the demon set because we changed the configuration.
So let's check the logs again.
And here you see the logs of one of our applications, so no EP is the one that's processed by this
one pod.
And here we see the logs.
Here's the message.
Hello, elastic world.
So these are all our no thep logs.
And let's check the second one.
This is the one that logs Java Web logs.
So this is how the output looks like aggregated and processed by fluently.
So here you have the timestamp, then you have the take.
This is the take that I mentioned.
Have Khubani this dot as a prefix.
This is the one that we have added here.
And then you have instead of bar slash, log slash, blah, blah, blah, you have that path, so to
say, transform into a tag.
Then you have the application named namespace name and all this stuff, and then you have the log entry.
So we're almost ready.
We have the logs that are processed by flow.
And now instead of sending them to a standard output of fluency, we want to send them to ElasticSearch.