orpiske commented on issue #1783:
URL: https://github.com/apache/camel-k/issues/1783#issuecomment-831743886
Thanks!
> Great! I think these are acceptable, compared to having the operator log
fully JSONified.
>
> Just to be sure, what do you mean exactly by 4?
Basically, what I meant is that the JSON for the build log and the JSON for
the operator logs are different.
```
{"level":"info","ts":1620106986.5145833,"logger":"camel-k.controller.kamelet","msg":"Invoking
action
monitor","request-namespace":"camel-colorization","request-name":"cassandra-sink","api-version":"camel.apache.
org/v1alpha1","kind":"Kamelet","ns":"camel-colorization","name":"cassandra-sink"}
```
The maven logs are slightly different and we'll have to adjust that to make
them look the same (either by modifying the logback configuration or consuming
them).
>
> The first value is to have full JSON for the operator log. Then, the
second requirement would be to enable correlation for the Build logs, that are
interleaved into the operator reconcile loop. To meed that requirement, it'd be
useful to add a build correlation key. Or to find another mechanism, so that
SOPs or users can quickly pick into the build and reconciliation for a
particular resource.
I see. It makes sense. If I understand it correctly, this is just the first
part: just printing the maven logs in JSON format.
To make it truly useful, we'll have to consume and process that maven JSON
format so we can normalize it and correlate it. So, IMHO, the next step would
be to work on that.
Do you think it makes sense to split that into 2 tasks (and, consequently,
in 2 contributions)?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
