Search docs.molo17.com

    How to create a support ticket

    You open a support request at support.molo17.com. The portal has a new design, with Spark triage, a log upload voucher on every request and notification settings. The full walkthrough is in Use the MOLO17 support portal. This page keeps the short answer and the list of logs to attach.

    Open a request

    1. Sign in at support.molo17.com, or create an account with your work email;

    2. Describe the problem in the box on the Home page and select Triage with Spark, or select New request and choose Bug, Help, Change or Incident;

    3. Enter a summary and a description, choose the priority and submit the request;

    4. Send the logs with the voucher on the request page.

    Every step, with screenshots, is in Use the MOLO17 support portal. For the incident commitments of your plan, read Enterprise support.

    Which logs to attach

    Logs let us start on your problem without asking you for them first. Send a compressed archive made by Gluesync, never single .log files or screenshots of a log.

    Kind of problem What to attach How to collect it

    A pipeline, an entity or an agent fails, stalls, or loses data

    The Core Hub log. The agents run inside Core Hub, so their lines are in the same file: there is no separate log for each agent. Add the error text of the entity (Copy error) and the name of the pipeline and of the entity

    Settings → Support in the Control Plane, see Collect and send logs to MOLO17 support

    A schedule or a maintenance window did not run (the Schedules & events area)

    The Chronos log as well as the Core Hub log

    Select Collect full environment logs, statistics and metrics in the Control Plane. An archive without this option holds the Core Hub log only. Or use the bundle of Gluesync Control, which holds the log of every container

    An installation or an update fails, a container does not start, or the host or Docker misbehaves

    The support bundle of Gluesync Control: the installer logs, the configuration with the secrets removed, a snapshot of the system and the log of every container

    gluesync collect-logs on Linux and on Windows Server, see Gluesync Control and Gluesync Control for Linux

    The Control Plane does not open

    The support bundle of Gluesync Control

    gluesync collect-logs, which does not need the Control Plane

    A problem that you can reproduce

    The logs of the time of the problem, written at the level DEBUG

    Set the level in Settings → Support → Log level settings before you reproduce the problem, reproduce it, and collect the logs at once. Set the level back afterwards. Do not leave it at ERROR, which hides the progress messages that we need

    A problem that happened days ago

    All the rolled log files that cover the time of the problem, and the date, the time and the time zone at which it started

    Check Log retention settings on the same page first. Core Hub deletes the files that are older than Max history (Days) or beyond Total size cap (GB)

    Add Include database, which puts a snapshot of the Core Hub database in the archive, only when we ask for it.

    The voucher of your request sends a bundle straight into the request. Where the voucher is and how to use it is in step 8 of Use the MOLO17 support portal. Read Read Gluesync logs and diagnose errors for where each component writes its log.

    Tell us what the logs cannot

    Add this to your request:

    • The Gluesync version that you run;

    • When the problem started: date, time and time zone;

    • The impact: which pipelines or entities are affected, and whether data is stopped or only late;

    • For a slow start, how many entities the pipeline has;

    • For a bug: the steps to reproduce it, what you expected and what you saw, and the versions of the source and the target database.