In your official docker images, I see that there are ways to configure volumes, license, and credentials when starting containers. But is there a way to configure the level of transparency? Something like logging levels. The only logs we see are during startup about loaded fonts, license info, environment, content root, and finally which address it’s listening on.
When exceptions are raised during runtime, we see very minimal information and overall nothing helpful.
Is it possible to set a log level that lets us see more context about the running instances? Something like info, debug, and verbose levels are often seen in our industry as a way to tweak the amount of information available to sift through. Often, the errors we see now on the client side (i.e. content of response bodies) are also not helpful and we’re left wondering what the next steps should be other than opening more support tickets or a new topic in this forum.
@james-ontra
Could you please specify which Aspose product you are using and the environment in which you are running the containers? Additionally, are you looking for a specific logging framework or method to implement this logging level configuration?
Could you please specify which Aspose product you are using and the environment in which you are running the containers?
If you click through the link in my original message, you’ll see that the Aspose product we’re using is Aspose.Words. My topic also does not pertain to a specific environment. I’m inquiring about increasing the level of transparency in any environment.
Additionally, are you looking for a specific logging framework or method to implement this logging level configuration?
This has nothing to do with integrating logging frameworks. I understand this is an automated bot asking canned questions but I’ll clarify anyway:
The question is if there are options to configure logging levels on containers based on your official Aspose.Words images. Perhaps with more environment variables, something like:
docker run -e "LogLevel=DEBUG" # and so on ...
If so, please refer me to any documentation that I may have overlooked. If not, perhaps this is something your team will consider adding in later releases.
Let me check the documentation and current implementation, and I will return with more information.