Datasources | Germain Documentation

In GermainUX, a Data Source is a concrete software or hardware resource that the platform can access to collect data or execute an automated transaction.

A Data Source represents a specific infrastructure instance, endpoint, file location, or service—not a general application category.

💡 Examples include:

Example
A physical or virtual server
A database
A log directory
A REST endpoint
A Docker container
An SMTP service

⚙️ Common Data Source Types

Resource	GermainUX Data Source type	Details
Physical host	Host	Represents a physical server.
Virtual machine	Host	Uses a descriptive type such as `VM`.
Docker container	Host	Uses a descriptive type such as `Docker Container`.
Mobile device	Host	Uses a descriptive type such as `Android` or `iPhone`.
Directory	FilePath	Represents a directory that GermainUX can monitor or access.
File	FilePath	Represents a specific file or file-location pattern.
REST endpoint	URI	Represents an HTTP or HTTPS endpoint.
SMTP service	URI	Represents an SMTP service endpoint.
Database	Database	Contains the information required to connect to a database.
Remote Java service	URI	Represents a Java service exposing management or monitoring capabilities through JMX.

🔌 Preconfigured Data Sources and Integrations

GermainUX provides preconfigured integrations for many supported technologies.

See GermainUX Integrations for the available options.

❌ What Is Not a Data Source?

📦 Applications

An Application entry is not a Data Source.

Applications are logical groupings that represent the programs, services, servers, and other components that collectively deliver an application or business service.

Individual Data Sources can be associated with an Application. For example:

Example
A log directory can belong to a Salesforce application.
A web-service endpoint can belong to an Oracle Siebel CRM application.
A database can support an eCommerce application.

GermainUX monitors the associated services, hosts, files, databases, and endpoints—not the logical Application entry itself.

🔑 Credentials

Credentials are not Data Sources.

They provide the authentication information required to connect to a Data Source. GermainUX does not collect monitoring data from the credential configuration itself.

🔨 Executables

Executables are not Data Sources.

An executable is a program or command used by a monitoring or automation component to interact with a Data Source.

🔧 Configure a Data Source

A Data Source configuration contains the information GermainUX requires to connect to, monitor, or execute actions against the resource.

Data Sources can be configured through:

The Data Sources configuration screen
The Data Source Wizard

Depending on the Data Source type, configuration may include:

Configuration Item
Hostname or URI
Port
File or directory path
Parent host
Associated application
Credentials
Tags
Enabled status

🏷️ Tag a Data Source

Tags help organize and filter Data Sources.

Common tags include:

Tag
`production`
`staging`
`development`
`critical`
`customer-facing`

Tags can be created as needed and used to locate related Data Sources across environments. The behavior is similar to labels in GitHub.

🏛️ Data Source Classes

💻 Host

Host {
    existing properties from MonitoredServer
    app: string
    tags: string[]
    enabled: boolean
}

🗄️ Database

Database {
    existing properties from MonitoredDatabase
    host: reference to parent Host
    app: string
    tags: string[]
    enabled: boolean
}

📃 FilePath

FilePath {
    path: string
    host: reference to parent Host
    app: string
    tags: string[]
    enabled: boolean
}

🔗 URI

URI {
    URI-specific properties
    host: reference to parent Host
    app: string
    tags: string[]
    enabled: boolean
}

These relationships allow GermainUX to associate each concrete Data Source with its host, application, environment, and operational context.

Component: Engine

Feature Availability: 8.6.0 or later