Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Completely disable logging outputs on screen #8

Open
dirk-thomas opened this issue May 21, 2018 · 2 comments
Open

Completely disable logging outputs on screen #8

dirk-thomas opened this issue May 21, 2018 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@dirk-thomas
Copy link
Member

From @inspire1989 on April 27, 2017 16:50

Hi,
I want to disable the ROS logging in the console completely, but still have the logging to the /rosout topic. I tried these two options:

  1. Set output="log" in the launch file. This disables the output of Debug, Info and Warning messages but still, Error and Fatal messages are shown.
  2. Set the logger level to Fatal but this completely disables the /rosout topic.

Are there any other possibilities I could try out? For me, it sounds like a design-issue, because, if I explicitly specify the "log" output, I do not want to have outputs in the console...

Otherwise, I would be grateful to see this fixed in the next ROS version! :)

Thanks!

Copied from original issue: ros/ros_comm#1039

@dirk-thomas dirk-thomas added the enhancement New feature or request label May 21, 2018
@dirk-thomas
Copy link
Member Author

From @inspire1989 on April 27, 2017 20:9

By the way, I have another logging framework running that should still be able to log everything to the console.

@dirk-thomas
Copy link
Member Author

In ROS the log threshold determines that all log messages with a lower level are being ignored. The backend actually performing the logging can be swapped (see existing implementations: https://github.com/ros/ros_comm/tree/lunar-devel/tools/rosconsole/src/rosconsole/impl).

You use case of assigning separate thresholds for different sinks isn't supported. You might be able to configure / extend the log4cxx backend to match your needs.

But this is likely not a feature the maintainers will work on in the future. Please consider to contribute a pull request if this functionality is useful for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant