Skip to main content

Register an MQTT adapter

Where: sidebar → Streaming. Availability depends on your environment's MQTT infrastructure.

Before you start​

You need permission to manage workspace resources and the Tenant storage key assigned by your platform operator. This tnt_ key identifies storage placement; it is not your email address, organization slug, or permission to select another organization. Do not invent or reuse another customer's key.

Register the adapter

Enter the assigned Tenant storage key, Tenant name, and Adapter name, then select Register adapter.

Save the publishing details securely

Copy the generated broker endpoint, publish topic, username, and one-time password into your approved device configuration or secret store. Select I saved the credential only after storing them.

Configure and verify the publisher

Use the returned values exactly, including the topic and secure transport settings. Obtain the supported payload format from your operator and publish a non-sensitive test message.

Ask the operator to confirm downstream receipt and storage. Registration by itself does not prove that messages have arrived or become queryable tables.

Manage the adapter​

  • Pause / Resume: change the adapter's lifecycle state. Verify downstream effects before treating this as an emergency device-disconnection control.
  • Rotate credential: issues a new password; the confirmation warns that the previous password will stop working. Coordinate the device update first.
  • Archive: removes the adapter from the active list after confirmation. Do not assume this erases historical messages or Bronze objects.

Publishing credentials are shown once. Do not place them in documentation, screenshots, source control, or AI prompts. If exposed, coordinate credential rotation with the operator.

Streaming registration does not start a dedicated Spark application for each adapter. Ask your operator how the deployed shared ingestion path maps received data into the catalog.