Zaiming (Stone) Shi e7f0c83406 Merge pull request #12970 from zmstone/0503-refactor-dashboard-listener 1 anno fa
..
etc 86231f795d refactor: close managment http 8081 (#5564) 4 anni fa
include cb5fdb3c79 fix: rework In-flight / Mqueue API 1 anno fa
src 07cbdc6e90 feat(mgmt): add ignore_readonly qeury-string to PUT /configs API 1 anno fa
test e7f0c83406 Merge pull request #12970 from zmstone/0503-refactor-dashboard-listener 1 anno fa
.gitignore baa9fd8255 chore(emqx_management): move emqx management to apps 5 anni fa
README.md 7e31e60e90 style: fix wording 2 anni fa
rebar.config f28510b3ad refactor: HTTP connector into emqx_bridge_http app 2 anni fa

README.md

EMQX Management

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.

Functionality

Amongst others it allows to manage

  • Alarms
  • API Keys
  • Banned clients, users or hosts
  • Clients (and sessions) including their topic subscriptions
  • Configurations
  • Manage plugins
  • Fixed subscriptions
  • Topics

Moreover it lets you

  • modify hot and non-hot updatable configuration values,
  • publish messages, as well as bulk messages,
  • create trace files,
  • and last but not least monitor system status.

Implementation Notes

API endpoints are implemented using the minirest framework in combination with HOCON schema and OpenAPI 3.0 specifications.

TODO/FIXME

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.