Project

ocular

0.0
Repository is archived
No commit activity in last 3 years
No release in over 3 years
oculargaro/ocularHomepageDocumentationSource CodeBug TrackerWiki
Framework to automate responses for infrastructure events. Ocular allows to easily create small scripts which are triggered from multiple different event sources and which can then execute scripts commanding all kinds of infrastructure, do remote command execution, execute AWS API calls, modify databases and so on. The goal is that a new script could be written really quickly to automate a previously manual infrastructure maintenance job instead of doing the manual job yet another time. Scripts are written in Ruby with a simple Ocular DSL which allows the script to easily respond to multitude different events.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
70,111
Stars
1
Forks
0
Watchers
2
 Releases
Current version
0.2.9
Total releases
33
First release
2016-02-19
Latest release
2017-01-03
 Development
Primary Language
Ruby
Licenses
Apache 2.0
Average date of last 50 commits
2016-07-14
Reverse Dependencies
0

 Dependencies

Development

rspec
= 3.4.0

Runtime

bunny
= 2.3.1
etcd
= 0.3.0
faraday
= 0.9.2
fog
= 1.37.0
mongo
= 2.3.0
mysql2
= 0.4.3
pg
= 0.19.0
puma
= 2.16.0
rack
= 1.6.4
rack-protection
= 1.5.3
ruby-kafka
= 0.3.15
rufus-scheduler
= 3.2.0
rye
= 0.9.13
 Project Readme

ocular

Framework to automate responses for infrastructure events.

Ocular allows to easily create small scripts which are triggered from multiple different event sources and which can then execute scripts commanding all kinds of infrastructure, do remote command execution, execute AWS API calls, modify databases and so on.

The goal is that a new script could be written really quickly to automate a previously manual infrastructure maintenance job instead of doing the manual job yet another time. Scripts are written in Ruby with a simple Ocular DSL which allows the script to easily respond to multitude different events.

Currently implemented event sources:

  • HTTP calls
  • RabbitMQ messages
  • Timers

Planned event sources:

  • SQS/SNS messages
  • Zabbix alerts
  • NATS broadcast messages
  • salt-stack event bus

Currently implemented clients to external services (ie. what you can easily do once your event has been triggered):

  • MySQL
  • etcd
  • RabbitMQ
  • AWS/EC2
  • Kafka (for logging)
  • SSH for remote execution

Planned clients to external services:

  • Graphite
  • Zabbix configuration
  • salt-stack remote state execution