Notification Feed
PROLive log stream from /rosout with severity filtering
When to reach for it
Notification Feed is the live log viewer: severity-filtered messages from /rosout, with optional timestamps and node names. Use it during long autonomous runs, anytime you want the robot's own log voice visible alongside the dashboard. For raw topic data including non-log messages, Topic Log (Pro) is the broader inspector. For your own publish events, Publish Log.
Worked example: Nav2 navigation run
Point Log Topic at /rosout, which auto-fills Message Type to rcl_interfaces/msg/Log. Set Min Severity to Warning so the feed only surfaces what needs attention during a long Nav2 run, then drop it to Info while debugging a specific failure. Leave Auto-scroll on for hands-off monitoring, off when you want to scroll back through what just happened without the view jumping.
Watch out for
- Min Severityfilters messages after they've already reached
/rosout; it doesn't touch the node's own logger level. If you set it to Debug and still see nothing, raise the verbosity on the robot, not in Tinca. - The subscription is capped at 20 Hz regardless of Max Entries; a node logging faster than that has entries dropped before severity filtering ever sees them.
- Switching Log Topicwipes the buffer immediately, so swap topics only when you're done reading, not mid-incident.
Configuration fields
The log topic (rcl_interfaces/msg/Log), usually /rosout.
The ROS message type for this topic, e.g. sensor_msgs/msg/Image. Usually auto-filled when you choose a topic.
Hide messages below this level. Info shows Info and above; Error shows only errors and fatals.
How many recent log lines to keep before old ones drop off.
20 to 500, step 10Keep the newest message in view as logs arrive.
Show the time each message arrived.
Show which node logged each message.