Architecture
Main components of a Tat Installation are:
- Tat, also called Tat Engine. Your can running as many Engine as you want.
You can imagine running many Tat-Engine instances on Mesos/Marathon, Kubernetes or Swarm, or configure yourself behind a reverse proxy. Source: http://github.com/ovh/tat
- Tatwebui: it’s a web application, an easier way to call Tat Engine than curl. This application
is component oriented, your can display messages with different Views. See next chapter about Tatwebui for
more information. Source: http://github.com/ovh/tatwebui
- Tatcli, the TAT Command Line Interface. All Tat features are available on tatcli. You can use it
for “one shot” action on Tat Engine, or for display a UI in command line with
tatcli ui
. Tatcli ui
is popular to keep an eye on alerts or monitoring events without having a browser on it. Source: http://github.com/ovh/tat/tatcli
- uServices: Tat Engine is simple to be used, it’s also easy to develop uService above tat to
make things a little more advanced, like on-call schedule & intervention, reporting, etc…
You’ll find some opensourced uService in chapter Ecosystem