You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running Raster Vision pipelines the python logging is configured only for the Raster Vision module. This is particularly a problem for Raster Vision pipelines that run on AWS batch where the lack of configuration effectively suppresses all log output from pipeline stages.
Since at this point Raster Vision owns the execution of the pipeline, its both the entry point and the source of the command that is running on as AWS Batch job, it should provide a way to configure logging.
Two additional options would be helpful:
--global-log-level that invokes logging.basicConfig as part of reading RVConfig
--logging-config that reads/copies logging.conf file and invokes logging.config.fileConfig as part of reading RVConfig
The second option would be useful for debugging troublesome jobs when you'd want to turn the log chattiness deferentially for a particular module.
The text was updated successfully, but these errors were encountered:
When running Raster Vision pipelines the python logging is configured only for the Raster Vision module. This is particularly a problem for Raster Vision pipelines that run on AWS batch where the lack of configuration effectively suppresses all log output from pipeline stages.
Since at this point Raster Vision owns the execution of the pipeline, its both the entry point and the source of the command that is running on as AWS Batch job, it should provide a way to configure logging.
Two additional options would be helpful:
--global-log-level
that invokeslogging.basicConfig
as part of readingRVConfig
--logging-config
that reads/copieslogging.conf
file and invokeslogging.config.fileConfig
as part of readingRVConfig
The second option would be useful for debugging troublesome jobs when you'd want to turn the log chattiness deferentially for a particular module.
The text was updated successfully, but these errors were encountered: