Tools Print

  • tools, import
  • 0

Medusa Panel › Tools

The Tools menu gathers the maintenance and import utilities of the panel. Each item opens its own screen. This article describes what every Tools item does and the choices it offers: Import, Mass Editor, Capacity & Reliability and API Documentation.

Import

Import creates many streams or movies at once from a playlist. It is an administrator-only screen. The form has these choices:

  • Import Type — the kind of file. M3U / M3U8 Playlist is the supported option. A second option for a codec database backup (a .gz file) is listed, but importing that backup format is not supported in this version and is reported as such.
  • Import As — whether each playlist entry becomes a Streams entry or a Movies entry. Split a mixed playlist before importing.
  • Stream Profile — shown when importing as streams. Every new stream is created with this saved profile, which also fixes the server the stream runs on. The list shows each profile as profile — server.
  • Target Server — shown when importing as movies. The server the new movies are created on.
  • Import File — the playlist, selected with the drop zone or the Browse files button. An .m3u or .m3u8 file is required, up to 8 MiB and up to 10,000 entries.

Two buttons run the job. Dry Run validates the playlist and shows what would happen without saving anything; each row is numbered with the identifier the record would receive, for example Would import as stream 36. Import actually creates the records. Imported streams are created stopped and disabled, so nothing starts delivering until you enable it. Entries whose URL already exists — earlier in the same file, or in an existing stream or movie — are skipped rather than duplicated.

Both actions open a results table with the columns Source ID / Line, Type, Item, URL, Status and Message. The status of each row is Success, Skipped or Failed, and a summary line counts each outcome, such as Import complete: 30 imported, 4 skipped, 2 failed.

#EXTM3U
#EXTINF:-1 tvg-id="one.tv" tvg-name="Channel One" group-title="Sports",Channel One
http://source.example.com/live/one.m3u8
#EXTINF:-1 group-title="News",Channel Two
http://source.example.com/live/two.m3u8
A Dry Run never changes anything. Use it to confirm the playlist parses and to see how many entries are new before you commit to the real import.

Mass Editor

Mass Editor rewrites the source values of many records in one operation using a regular expression. The form offers:

  • Media Type — All types, Streams, Movies or Episodes. Choosing one type narrows the scan; All types edits them together.
  • Regular Expression — a Go regular expression matched against each stream URL and each movie or episode source, for example ^https://old\.example/(.*)$.
  • Replacement — the text that replaces each match. Capture groups are referenced as $1 or ${name}, for example https://new.example/$1. Leaving it empty removes the matched text.
  • Category — an optional filter that limits the operation to one category. Episodes inherit the category of their parent series.

The edit is a two-step, confirmed operation. Step one is Dry Run, which lists every record that would change in a results card with the columns Type, ID, Item, Category, Source and Replacement, and issues a one-time confirmation token. Step two is Confirm and Apply, which must be used within 15 minutes; the operation is rejected if any previewed source or category membership changed in the meantime.

Confirmation changes source fields directly and cannot be undone from this page. Always review the Dry Run results before applying.

Capacity & Reliability

Capacity & Reliability runs a load test against the playback path to measure how many players a server can carry while staying under 90% CPU and memory. The configuration includes:

  • Target servers — the servers to assess (this version assesses the local server).
  • Playback user — the subscriber account whose access the simulated players use.
  • Playable resource — one or more accessible streams, movies or series to play.
  • Protocols — HLS and HTTP-TS; selected protocols run together with an equal split of players.
  • HLS variant — which rendition to request, from highest bandwidth to a target bandwidth or resolution.
  • Resource limits — fixed at CPU and memory below 90%; the test adds players automatically up to the ceiling.
  • Test duration — the run length in seconds, from 10 to 86400, including ramp-up.

Start assessment begins the run and Stop assessment ends it early. A Run status panel shows the state, a progress bar, live statistics and a per-second timeline of players, CPU and memory, with per-server and per-protocol detail. When a run finishes you can Copy Report or Export PDF.

This tool generates real media traffic and real connections against the selected servers. Run it during a maintenance window and keep the duration sensible, because the test ends only when the chosen duration elapses or you stop it.

API Documentation

API Documentation opens the interactive reference for the engine HTTP API in a new browser tab. It describes the available endpoints and their parameters so you can automate the panel from your own scripts and integrations.

Related


Was this answer helpful?

« Back