HTTP Endpoints
Below is a list of HTTP endpoints available for a given Mesos process.
Depending on your configuration, some subset of these endpoints will
be available on your Mesos master or agent. Additionally, a /help
endpoint will be available that displays help similar to what you see
below.
NOTE: The documentation for these endpoints is auto-generated from strings stored in the Mesos source code. See support/generate-endpoint-help.py.
Master Endpoints
Below is a set of endpoints available on a Mesos master. These endpoints are reachable at the address http://ip:port/endpoint.
For example, http://master.com:5050/files/browse
files
- /files/browse
- /files/browse.json
- /files/debug
- /files/debug.json
- /files/download
- /files/download.json
- /files/read
- /files/read.json
logging
master
- /api/v1
- /api/v1/scheduler
- /create-volumes
- /destroy-volumes
- /flags
- /frameworks
- /health
- /machine/down
- /machine/up
- /maintenance/schedule
- /maintenance/status
- /quota
- /redirect
- /reserve
- /roles
- /roles.json
- /slaves
- /state
- /state-summary
- /state.json
- /tasks
- /tasks.json
- /teardown
- /unreserve
- /weights
metrics
profiler
registrar(id)
system
version
Agent Endpoints
Below is a set of endpoints available on a Mesos agent. These endpoints are reachable at the address http://ip:port/endpoint.
For example, http://agent.com:5051/files/browse
files
- /files/browse
- /files/browse.json
- /files/debug
- /files/debug.json
- /files/download
- /files/download.json
- /files/read
- /files/read.json
logging
metrics
profiler
slave(id)
- /api/v1
- /api/v1/executor
- /containers
- /flags
- /health
- /monitor/statistics
- /monitor/statistics.json
- /state
- /state.json