Viewing Environmental Controls

To view and change application and engine variables, perform the following steps:

    Procedure
  1. In TIBCO Control Plane, click Data Planes from the left navigation.

  2. On the Data Plane card of your choice, click Go to Data Plane.

  3. In the Applications section, click a running Flogo app from the listed apps.

  4. Click the Environmental Controls tab.

Application Variables

This section lists the application variables that are user-defined. You need to click Push Updates after modifying the values.

Engine Variables

This section lists the engine variables that are associated with the Flogo runtime environment. You can add, modify, or delete. You need to click Push Updates after modifying the values. The variables on the Engine Variables tab are FLOGO_LOG_LEVEL and FLOGO_OTEL_TRACE, you can add the rest of the variables as per your requirement.

Name Type Description
FLOGO_LOG_LEVEL String

Used to set a log level for the Flogo app. Supported values are INFO, DEBUG, WARN, and ERROR.

Default value: ERROR

FLOGO_LOG_CONSOLE_STREAM

String

Used to specify the logging output stream for Flogo engine and app logs. Supported values are stdout and stderr.

Default value: stderr

FLOGO_OTEL_TRACE Boolean

When FLOGO_OTEL_TRACE is set to true, OpenTelemetry tracing is enabled for the flogo app.

When FLOGO_OTEL_TRACE is set to false, OpenTelemetry tracing is not enabled for the flogo app.

Default: false

FLOGO_OTEL_SPAN_KIND

String

Used to specify the type of span to be used in OpenTelemetry. The supported values are INTERNAL, SERVER, CLIENT, PRODUCER, and CONSUMER.

Note: If no value or an invalid value is provided, the default value is set to INTERNAL.
FLOGO_RUNNER_QUEUE_SIZE Integer

The maximum number of events from all triggers that can be queued by the app engine.

The default value is 50.

FLOGO_RUNNER_WORKERS Integer

The maximum number of concurrent events that can be run by the app engine from the queue.

The default value is 5.

FLOGO_FLOW_CONTROL_EVENTS Boolean

If you set FLOGO_FLOW_CONTROL_EVENTS as true, the Flow limit functionality is enabled, whenever the incoming requests to trigger reach FLOGO_ RUNNER_QUEUE_SIZE limit the trigger is paused. When all the requests currently under processing are finished, the trigger is resumed again. All the connectors supporting the Flow limit functionality are mentioned in their respective user guides.

FLOGO_MAX_STEP_COUNT Integer

The application stops processing requests once the FLOGO_MAX_STEP_COUNT limit is reached. The maximum limit is 10 Million.

FLOGO_APP_PROP_RECONFIGURE Boolean The engine variable FLOGO_APP_PROP_RECONFIGURE should be set to true for updating an app configuration on runtime without restarting the app instance.
FLOGO_APP_PROPS_AWS String

You can override application properties of an application in the AWS Parameter Store on runtime using a JSON string in the FLOGO_APP_PROPS_AWS engine variable.

FLOGO_APP_PROPS_CONSUL String

You can override application properties of an application in the CONSUL on runtime using a JSON string in the FLOGO_APP_PROPS_CONSUL engine variable.

FLOGO_APP_PROP_SNAPSHOTS Boolean

When you dynamically override the app properties while the flow is running, it takes the values from the snapshot if this variable FLOGO_APP_PROP_SNAPSHOTS is set to true.

HTTP_PROXY

String

If your data plane has restricted external connectivity through a proxy server, set the HTTP_PROXY and HTTPS_PROXY system variables in your app and explicitly add the proxy service URL to enable the activities to reach external APIs.

Example:

HTTP_PROXY=http://squid-service.default.svc.cluster.local:1234

HTTPS_PROXY=http://squid-service.default.svc.cluster.local:1234

After setting these variables in the Flogo app, the apps will be able to connect to the internet.

HTTPS_PROXY

Resource Configuration

Resource Allocation for Deployed Applications:

  • Previously Deployed Apps: If you have already deployed an application using an older version, you can now reconfigure its resource allocation to optimize performance. These applications would have had a default resource allocation set at the time of deployment.

  • Flexibility for All Deployed Apps: Users can modify the resource allocation for any deployed application, regardless of whether it is newly created or an older version. This allows you to fine-tune resource usage and ensure that your applications have the resources they need to run smoothly.