This message was deleted.

Hi @Dor Alon as indicated here: https://docs.opal.ac/getting-started/running-opal/run-opal-client/opa-runner-parameters you can pass a JSON object with the

config_file

key pointing to the path you want

thanks

You’re missing the OPAL_ prefix

thanks

🙂 sure

@Or Weis how can I see OPA console output ?

It should pipe out to the same STDOUT/err as the opal-clients @Asaf Cohen - correct me if I’m wrong

I can't see it in the container console output

You might need to change the log-level, pass in the JSON something like: “log_level” : “error”

I'm assuming you mean the OPA log level, the default is info and I can see it as a command line parameter how changing it to error going to help ?

Sorry, I think the controlling parameter is this one:

OPAL_INLINE_OPA_LOG_FORMAT

Which can have the following values: • “none” # no opa logs are piped • “minimal” # only the event name is logged • “http” # tries to extract http method, path and response status code • “full” # logs the entire data dict returned

thanks