https://github.com/karadalex/roslogs-elk-docker

ROS Logs & ELK Stack
https://github.com/karadalex/roslogs-elk-docker

docker docker-compose elasticsearch filebeat kibana logging logs logstash ros

Last synced: about 22 hours ago
JSON representation

ROS Logs & ELK Stack

• Host: GitHub
• URL: https://github.com/karadalex/roslogs-elk-docker
• Owner: karadalex
• Created: 2019-03-08T18:50:08.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2019-03-08T18:50:33.000Z (over 5 years ago)
• Last Synced: 2024-02-29T05:38:11.027Z (4 months ago)
• Topics: docker, docker-compose, elasticsearch, filebeat, kibana, logging, logs, logstash, ros
• Language: CMake
• Size: 6.84 KB
• Stars: 9
• Watchers: 4
• Forks: 1
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Lists

• awesome-ros-tools - ROS Logs & ELK Stack - demo of collecting ROS Logs (from ROS Containers) with Filebeat which are then sent to Logstash indexed by Elasticsearch and can then be viewed and visualized at Kibana. All logs are stored in the roslogs volume.  (Development Tools / Logging)

README

        
ROS Logs & ELK Stack

============================

## How it works

Collect ROS Logs (from ROS Containers) with Filebeat which are then sent to Logstash indexed 

by Elasticsearch and can then be viewed and visualized at Kibana.

All logs are stored in the **roslogs** volume.

## Instructions

```

docker-compose up

```

To run other tools like **rqt_graph** for visualizing the topics you must first set

the ROS_MASTER_URI environment variable. The ros master posrt must match the host port in the

docker-compose file, in this project both host and container ports are 11311. 

If the ros master listens on 11311 then you can skip this step

```

export ROS_MASTER_URI=http://localhost:11311

```

and then run on your **host** machine

```

rosrun rqt_graph rqt_graph

```

## TODO

1. Filter messages in Logstash pipelines