Managing Data Sources

Review, test, and manage the data connections that supply data to Reporter.

Data Sources are connections that Reporter uses to fetch the data needed for report generation. Some Data Sources can already be configured for internal Lerian products, such as Midaz or CRM. Use this page to review those connections, test them, or manage external database connections through the Lerian Console.

What is a Data Source?

---

A Data Source represents a configured connection between Reporter and a data store. To generate reports, Reporter needs access to source data. For internal product data, the connection may already exist. For external databases, operators can add and manage the connection from this page.

Each Data Source includes:

• Connection name — a human-readable identifier for easy management.
• Database type — the database engine being used (PostgreSQL, MySQL, MongoDB, Oracle, or SQL Server).
• Access configuration — host, port, database name, credentials, and optionally SSL configuration, when the Data Source is an external database connection.
• Schemas — for databases that support schemas (PostgreSQL, Oracle, SQL Server), you can specify which schemas to access.
• Metadata — additional key-value fields for organization.

Operators usually use this page to answer three questions:

• Is the connection available?
• Which schemas, tables, and fields can Reporter read?
• Is this the right Data Source for the Template or Report being prepared?

Supported databases

---

Database	Default port	Schema support
PostgreSQL	5432	✅
MySQL	3306	❌
MongoDB	27017	❌
Oracle	1521	✅
SQL Server	1433	✅

Accessing the Data Sources page

---

To open the Data Sources page, click Data Sources from the left-side menu on the Reporter page.

You do not need to start here in every Reporter journey. Start here when the needed Data Source is missing, when an external database must be added, or when a report fails because data is unreachable.

The page displays all configured connections, each in a card showing:

• Connection name and database type.
• Connection status (Connected, Disconnected, or Connecting).
• Configured schemas (if any).
• Latency from the last check.
• Host, database, and user details.

You can expand each card to view the database schema, including available tables and columns.

Available actions

From the Data Sources page, you can:

Add a Data Source

Create a reusable external database connection for Reporter.

Edit a Data Source

Update credentials, host, schemas, SSL, or metadata.

Test connection

Confirm Reporter can reach the database and load schema information.

Delete a Data Source

Remove retired connections that are no longer used.

If a Report fails because data is missing or unreachable, start by testing the Data Source and checking whether the expected schema and table appear in the expanded card.