L7|ESP Services
Every L7|ESP instance is composed of a set of services running in a container. If your container is running, but you cannot access L7|ESP in the web browser, use the l7 command-line utility to check the status of these services.
$ l7 status $ l7 stop # stop all services $ l7 start # start all services $ l7 restart # restart all services in one command $ l7 status l7-esp.broker RUNNING pid 95176, uptime 4 days, 4:44:44 l7-esp.concierge RUNNING pid 95184, uptime 4 days, 4:44:44 l7-esp.database RUNNING pid 95113, uptime 4 days, 4:44:46 l7-esp.executor RUNNING pid 95185, uptime 4 days, 4:44:44 l7-esp.haproxy RUNNING pid 95178, uptime 4 days, 4:44:44 l7-esp.http:l7-esp.http.0 RUNNING pid 95182, uptime 4 days, 4:44:44 l7-esp.http:l7-esp.http.1 RUNNING pid 95181, uptime 4 days, 4:44:44 l7-esp.http:l7-esp.http.2 RUNNING pid 95180, uptime 4 days, 4:44:44 l7-esp.logger RUNNING pid 95179, uptime 4 days, 4:44:44 l7-esp.notification RUNNING pid 95175, uptime 4 days, 4:44:44 l7-esp.pipeline RUNNING pid 95183, uptime 4 days, 4:44:44 l7-esp.scheduler RUNNING pid 95177, uptime 4 days, 4:44:44
Below is a short description of each service:
l7-esp.broker
ZeroMQ broker (backend messages for services mentioned below)
l7-esp.concierge
Serves configurations and a number of other services
Flask (synchronous) web server deployed via Gunicorn
l7-esp.database
Launches and monitors the PostgreSQL database
Creates schema (if needed)
l7-esp.executor
Runs tasks
Receives messages via ZeroMQ
l7-esp.haproxy
Launches HAProxy and monitors it
l7-esp.http
Main backend server(s)
Tornado (asynchronous) v5 web server
l7-esp.logger
Consolidates all logs into
l7-esp.logReceives messages via ZeroMQ
l7-esp.notification
Manages L7|ESP and 3rd party notifications
Flask (synchronous) web server deployed via Gunicorn
l7-esp.pipeline
Submits Pipelines to the executor
Receives messages via ZeroMQ
l7-esp.scheduler
Runs scheduled tasks (custom content)