36 docs tagged with "operations"

This document covers the Genesis artifact store, which is an instance of JFrog's Artifactory.

There are three easy ways of testing components in your application:

This document looks at the different metric types, and how you can use them in your application's code.

To enable metrics on your application, add the following settings to your system definition file:

This lists all the tables in your data model.

Console enables you to monitor your application with precision, enabling you to see individual processes, resources and data. You can view logs for each process, insert data, control logging levels, monitor CPU and memory usage, and examine the code of specific processes.

This page displays system messages.

This screen enables you to view all the processes (microservices) that are running. The services are listed on the left of the page.

Following a successful deployment, details of each process in the deployment are displayed here with the following details:

This page shows all the available resources that publish data to the web UI.

The Genesis low-code platform provides two different options for building a Docker image.

Configuration options

The Genesis low-code platform Docker image provides a health check endpoint, which reports the status of the container.

You can run a full Genesis application in a self-contained Docker container. There are two simple ways:

If you choose to use the Gradle plugin to build the image, the Genesis low-code platform provides a Gradle task that pushes your built image to your chosen repository.

If you haven’t already initialised the database, you can run the Docker container passing the environment variable GENESISDBINSTALL=true. This triggers a remap to create all the tables and will exit on completion.

If you want more control over the image, you can create your own Dockerfile. This gives you complete control over the base image and the versions of the underlying dependencies.

The Genesis Gradle Settings plugin provides the following benefits:

GenesisJunit is only available from version 8 of the Genesis Server Framework (GSF).

Database and service tests

The Genesis Platform provides metrics both on the framework and at the application level.

Project structures

This page relates to Server logging.

Using Genesis Data Pipelines often requires some set-up/configuration of your external database. You must ensure that databases are correctly configured for Change Data Capture (CDC). Each database technology is slightly different and will therefore require slightly different set-up instructions.

CDC capabilities are only supported by MS SQL Server 2016 and later Standard and Enterprise editions. Ensure that your MS SQL instance is the Standard or Enterprise version before continuing.

CDC capabilities are only supported by Oracle Enterprise edition. Ensure that your Oracle instance is the Enterprise version before continuing.

PostgreSQL configuration

This version of the documentation describes version 8.5 of the Genesis Platform.

Service metrics are provided for specific service types. You can use these to keep track of how a service is behaving under load.

How to create a project

Tracing is the act of following what happens when a request is made to an application. The Genesis Tracing module enables you to generate tracing data for your application through an integration with industry-standard OpenTelemetry.

Unit testing does not require a database or the running of a Genesis service. So, as you define your application, each component should be unit-tested according to standard best practice.

The Genesis platform enables you to use a Jakarta Messaging (former JMS) compliant message broker as its real-time update-queue back-end via ArtemisMQ.

The Genesis low-code platform provides the option to use an external MQTT broker such as Mosquitto or RabbitMQ as the transport mechanism for the Genesis update queue.

What is the update queue?

The Genesis low-code platform uses ZeroMQ out of the box to provide a zero-configuration decentralised peer-to-peer update queue.