AndyG

I had to create a datadog pipeline to GROK for the message and then convert the mesage from ERROR to INFO

I'm not sure if you can fix it on the KEDA side. Im happy with my solution. Do the Docker logs goto STDERR or STDOUT ?

Sure, its not clean, but it works GROK rule: `rule1 %{numberExtStr:first}\t%{word:second}\t.*` Then a "status remap rule" Set status attribute(s) `second`

@cumcke any idea what the issue could be ?

It is a new cluster. I ran the script a few times. I have tried it on a new cluster as well, and still fails.

Is there any way to debug it better or get some more verbose error message ?

Thanks. I will try that. I’m not using any custom USERDIR and there should be no network restrictions.

Thnaks, it did deploy and is working, but it does still show those errors. TASK [monitoring : cluster-logging - deploy] *********************************** task path: /viya4-deployment/roles/monitoring/tasks/cluster-logging.yaml:94 fatal: [localhost]: FAILED! => changed=true cmd:...

It does seem to deploy fine, but those errors are still there.

I need the "search" that is currently in the pre-v1 version. when you click on "Tasks".