|
|
1 год назад | |
|---|---|---|
| .. | ||
| etc | 86231f795d refactor: close managment http 8081 (#5564) | 4 лет назад |
| include | cb5fdb3c79 fix: rework In-flight / Mqueue API | 1 год назад |
| src | de9e619c96 fix: use ekka when performing `emqx ctl cluster *` | 1 год назад |
| test | 4865999606 Merge remote-tracking branch 'upstream/master' into release-58 | 1 год назад |
| .gitignore | baa9fd8255 chore(emqx_management): move emqx management to apps | 5 лет назад |
| README.md | 7e31e60e90 style: fix wording | 2 лет назад |
| mix.exs | 19f3b030f9 chore: preparing to run common tests / eunit with mix | 1 год назад |
| rebar.config | f28510b3ad refactor: HTTP connector into emqx_bridge_http app | 2 лет назад |
EMQX Management offers various interfaces for administrators to interact with
the system, either by a remote console attached to a running node, a CLI (i.e.
./emqx ctl), or through its rich CRUD-style REST API (mostly used by EMQX'
dashboard). The system enables administrators to modify both cluster and
individual node configurations, and provides the ability to view and reset
different statistics and metrics.
Amongst others it allows to manage
Moreover it lets you
API endpoints are implemented using the minirest framework in combination with
HOCON schema and OpenAPI 3.0 specifications.
At its current state there are some reverse dependencies from other applications
that do calls directly into emqx_mgmt.
Also, and somewhat related, its bpapi proto modules do calls directly into other applications.