Agree, we can now try to extend the datastructure that logs-api returns (LogEntry), ideally we would want to support different types of logs too (build logs, system logs, etc.) so we might want to create some more generic one.

I think we might want to add some metadata + values, like:

{
    "metadata": {
        "type": "job",
        "datetime": "",
        ## We can add more as needed, like user, etc.
    }
    "data": {
        "container": ...,
        "pod": ...,
        "message": ...,
        ## this ones will depend on the type, builds don't have one single container for example
    }
}

That would allow also to have a 'type' that's something like "internal", and express there the fact that it got no logs yet.

Some notes for whomever implements this:

We probably want to make the changes in small increments on the cli (first support both formats, change the api to the new format, then remove support for the old format, for example).
Might be good also to notify users of the non-backwards compatible API changes (logs-api is quite new, so probably no need to give a lot of heads up).

Eventually having 'system logs' (build, jobs, components) with a common 'trace id', so for a deployment you can see everything that happened, would be very nice to have (probably would require some effort to make sure internal things that could have secrets don't get logged to places with tool access).

@DamianZaremba btw. I think that you are the last one using the jobs-api log endpoint, can you move your code to use the logs-api instead? (so we can remove the logs code from jobs api :) ).

In T410055#11371792, @dcaro wrote:

@DamianZaremba btw. I think that you are the last one using the jobs-api log endpoint, can you move your code to use the logs-api instead? (so we can remove the logs code from jobs api :) ).

I'm in the process of doing that at sec :) there are a couple of small behaviour changes but it should be done today

In T410055#11371808, @DamianZaremba wrote:

In T410055#11371792, @dcaro wrote:

@DamianZaremba btw. I think that you are the last one using the jobs-api log endpoint, can you move your code to use the logs-api instead? (so we can remove the logs code from jobs api :) ).

I'm in the process of doing that at sec :) there are a couple of small behaviour changes but it should be done today

Done in https://github.com/cluebotng/trainer/pull/349

https://cluebotng-trainer.toolforge.org/Report%20Interface%20Import/2025-11-13%2018:02:49/logs/bayes-train.log example of where this gets pulled in

In T410055#11371972, @DamianZaremba wrote:

https://cluebotng-trainer.toolforge.org/Report%20Interface%20Import/2025-11-13%2018:02:49/logs/bayes-train.log example of where this gets pulled in

https://github.com/cluebotng/trainer/commit/861b0f3a4943848275da0460a32d2fb3f9a5b17d for now