Configuring Boomi Integrations Monitoring

This guide provides instructions for configuring the Nodinite Boomi Integrations Monitoring agent.

Info

Before any monitoring and remote configuration can be performed, you must first install the Nodinite Boomi Integrations Monitoring agent and create a Monitoring Agent Configuration. First-time users start here.

Remote Configuration

As a Nodinite Administrator, click on the 'Configuration' button to open a modal to configure the agent:

Example of the Configuration button location in the Monitoring Agent Configuration administration page.

Configurations on the Resource can be adjusted via the Action button if the Monitor View has the Remote Actions feature enabled.

Resources per Boomi Integration Account are grouped by Application and then by Category using the value from the Name text field. Read more about Applications here:

• Applications
  
  Example of the Application naming scheme for grouping resources.

All resources for one Integration account are pre-fixed by the user-riendly Display Name set in the next step.

Configuring the connection

• Add Account
• Remove Account
• Enable Monitoring
• Disable Monitoring
• Manage monitoring thresholds
  • Global - Use if not overridden by a specific setting
  • Specific - Overrides global configuration on named queue
• Authentication
• API Usage Limits

Remember to click on the Save button to persist changes. It may take some time (depending on the user-defined synchronization interval) for Nodinite to reflect on changes.

Example of Save and Close buttons.

Add Boomi Integration Account

From the Boomi tab, you can manage any number of Boomi Integration Accounts. Each with its own set of properties.
To monitor and control one or more Boomi Integration Accounts, you must provide some basic connection details.

Example of the Boomi tab for managing integration accounts.

Click on Add button to add a Boomi Integration Account to monitor, repeat as needed.

Example of an empty Boomi Integration Account entry.

• Click the Accordion to expand the connection configuration

From within the Basic tab, you can configure the following settings:

Example of the Basic tab configuration settings.

• Boomi - Repeat for each Account
  • Enabled - When checked, Boomi account monitoring is enabled
  • Display name - The user-friendly name for this configuration (required)
  • Account Id - The Boomi Account ID (found in your Boomi platform settings) (required)
  • Max Lookback Days - Maximum number of days to look back when fetching execution records (1-30 days, default: 7)

Remove Boomi Integration Account

Click the Remove button, to remove the configuration for monitoring the Boomi Integration Account with related services/resources.

Here's an example of the 'Remove' button. Use to remove the Boomi Integration Account configuration from monitoring

Instead of removing the Boomi Integration Account, you can simply disable Monitoring. This will keep your configuration.

Enable Monitoring

A disabled Monitoring Configuration is clearly marked with a ban sign. Only disabled configurations can be Enabled.

A disabled Boomi Integration Account configuration has a ban sign to indicate that the configuration is no longer being actively monitored.

Click the checkbox to re-enable monitoring of Boomi Integration Account related Resources.

Boomi Integration Account Monitoring is enabled when the checkbox is checked.

Disable Monitoring

You can stop monitoring all of the deployed resources for the Boomi Integration Account without removing the configuration by disabling the selected configuration. An enabled Monitoring Configuration does not have the ban sign. Enabled Boomi Integration Account configurations can be Disabled.

Monitored Boomi Integration Account configurations does not have a ban sign.

Un-check the checkbox to disable monitoring of Boomi Integration Account related Resources.

Manage monitoring thresholds

From the Thresholds Evaluation tab, you can manage both the global and specific monitoring thresholds. The global (tab-level) controls let you set default time-based evaluations, while process-specific overrides allow finer control on named processes.

Thresholds

Example of global threshold configuration settings.

• Enable Threshold Evaluation - When checked, the process execution time is monitored
• Warning Time Span - The longest allowed time span for a specific process to be In Process status before a warning arises. Format: days.hours:minutes:seconds (e.g., 0.04:00:00 for 4 hours)
• Error Time Span - The longest allowed time span for a specific process to be In Process status before an error arises. Format: days.hours:minutes:seconds (e.g., 0.01:00:00 for 1 hour)

Error-Prone

💡Global settings that apply unless overriden by specifics

You can manage the monitoring settings that classify a process as error-prone when its failure rate exceeds a configured threshold within a sliding time window.

This is an advanced evaluation and is disabled by default.

Example of Disabled error-prone evaluation configuration.

Check the checkbox to enable the error-prone evaluation for the selected scope.
Example of Enabled error-prone evaluation configuration.

• Error-prone Evaluation - When checked, error-prone processes are monitored according to the specification
• Maximum number of failed executions - Alert as error-prone if the number of failed process executions within the sliding window is above this threshold
• Sliding Window (minutes) - Determines how far back in time to perform the evaluation (the 'Window')

Certificate

^{New 7.2.0}

From the Certificate tab, you can configure thresholds for monitoring SSL/TLS certificates deployed across your Boomi environments. Certificate monitoring proactively tracks expiration dates and alerts you before certificates expire, preventing service disruptions.

See Deployed Certificate monitoring for complete details on how certificate state evaluation works.

Example of Certificate monitoring configuration.

• Warning Days - Raise a warning if a certificate expires within this many days (1-3650, default: 60)
• Error Days - Raise an error if a certificate expires within this many days (0-3650, default: 30)

Certificate-Specific Thresholds

You can override the global certificate thresholds for specific certificates. This allows different warning and error periods for critical certificates that require earlier notifications.

Click the Add button to create certificate-specific threshold overrides.

Specific Processes

You can override the global settings by applying other monitoring thresholds to specific Boomi Processes.

Tip

It is easier to manage individual Boomi Processes from within the Monitor Views and the required fields are automatically populated for you. Use this global configuration to create or modify existing specific entries.

Click the Add button to create a new entry.
Example of the Add button.

An empty record is then added to the list of specific process monitoring thresholds:

Example of an empty process monitoring threshold entry.

Click the accordion to expand the entry.

Process Details tab

You can manage the basics to identify a process from within the Process Details tab.

Example of Process Details tab.

• Name - The Process Name
• Atom Name - The Atom name in which the process resides
• Folder Full Path - The Process folder full path in which the process resides
• Ignore Failures Before Date (checkbox) - When checked, failed executions before the specified date are ignored
  • Clear Date Time - Visible and editable only when Ignore Failures Before Date is checked. Ignore failed executions before this date (format: yyyy-MM-ddTHH:mm:ssZ)

Error-Prone tab

You can manage the monitoring settings for a specific process and apply an error-prone specific evaluation. If the number of errors are higher than the specified threshold within the sliding window, the process is evaluated as being error-prone.

This is an advanced setting and is disabled by default.

Example of a process with error-prone evaluation disabled.

Check the checkbox to enable the specific error-prone threshold evaluation.

Example of a process with error-prone threshold evaluation enabled.

• Error-prone Evaluation - When checked, error-prone processes are monitored according to the specification
• Maximum number of failed executions - Alert as error-prone if the number of failed process executions within the sliding window is above this threshold
• Sliding Window (minutes) - Determines how far back in time to perform the evaluation (The 'Window')

Thresholds Evaluation tab

You can manage the monitoring settings for a specific process and apply time-related specific evaluation thresholds. If the number of errors are higher than the specified threshold within the sliding window, the process is evaluated as being error-prone.

This is an advanced setting and is disabled by default.

Example of a process with error-prone evaluation disabled.

Check the checkbox to enable the specific error-prone threshold evaluation.

Example of a process with error-prone threshold evaluation enabled.

• Enable Threshold Evaluation - When checked, the process execution time is monitored
• Warning Time Span - The longest allowed time span for a specific process to be In Process status before a warning arise. (days.hours: minutes: seconds e.g. 7.12: 30: 59)
• Error Time Span - The longest allowed time span for a specific process to be In Process status before an error arise. (days.hours: minutes: seconds e.g. 7.12: 30: 59)

Authentication tab

From the Authentication tab, you can enter the basic information to connect with the Boomi Integration platform to monitor:

• User name - The user name of the Boomi Platform
• Token Authentication - When checked, API token authentication is used (BOOMI_TOKEN format). Otherwise, password authentication is used
• Password / Token - The password or token of the Boomi Platform account
  Example of the Authentication tab.

API Usage Limits

Important

There is a limit with the Boomi APIs that you need to honour. These settings impact the time it takes for the Nodinite Boomi Integrations Monitoring agent to detect and report problems with the Boomi Integration platform.

The Nodinite Boomi Integrations Monitoring agent makes use of the Boomi AtomSphere APIs. Unfortunately, there is a limit to the usage of this API.
The usage limits are described on the Boomi Atomsphere API user guide.

• API request rate for Boomi Details - API request rate in minutes for Boomi details (e.g. Environment, Atom, Process)
• API request rate for processes execution records - API request rate in minutes for Boomi process execution records (Important for Boomi Evaluation)

Tip

We believe that you can contact the Boomi support and ask to raise the default of 1,000 times your number of licensed connectors / 24 hours. A developer account does not have the limit at all.

The numbers are in minutes.

Warning

You may need to have rather high values in a production environment! If you go too low, the monitoring will be suspended for that 24 hour period.

Settings

From within the Settings tab, you configure operational behavior, logging, and secret management for the Boomi Integrations Monitoring agent.

• Environment
• Debug
• Culture Information
• Secret Management

Environment

Part of the standard features shared with all Monitoring Agents is an option to set the name of the target environment, for example, TEST, QA, PROD.

Debug

Part of the common features shared with all Monitoring Agents, there is an option to set the Debug flag for additional file logging that can be enabled/disabled as needed. Default is unchecked.

Culture Information

The Culture Information setting determines how time-based data from this agent is presented in the Web Client/Web API.

Secret Management

^{New 7.x}

Configure certificate-based encryption settings to protect sensitive credentials like API tokens and passwords. Nodinite automatically manages certificate lifecycle, generation, and renewal.

See Secret Management for complete details on encryption algorithms, certificate stores, and automated lifecycle management.

Add Nodinite Boomi Integrations Monitoring Agent Configuration

After the successful installation of the Nodinite Boomi Integrations Monitoring agent you must provide Nodinite with connection details so the Monitoring Service knows there's a new guy in town.

No monitoring or other configuration of the Nodinite Boomi Integrations Monitoring agent can be performed before the steps outlined below has been executed.

Configuration Steps

1. Add and configure a new Monitoring Agent Configuration

   Connection information is available in the README.txt file in the installation folder

2. Use the Remote Configuration feature to configure the agent. Detailed at the beginning of this user guide.
3. Create one or more self-service enabled Monitor Views that include the selected Resources provided by the Nodinite Boomi Integrations Monitoring agent according to business needs.
   • Add or manage Monitor View
4. Fine-tune specific settings directly on Resources using Remote Actions

Frequently asked questions

Use the troubleshooting guide to find the FAQ and answers to known problems.

Note

ExecutionRecordsRateOfApiRequests depends on your Boomi subscription, developers has virtually no limit. Production environment currently has a very low limit to 1000 / day / connector (!)

Next Step

• Add or manage a Monitoring Agent Configuration
• Add or manage Monitor View
• Install Nodinite Boomi Integrations Monitoring Agent
• Update

Related Topics

• Monitoring Agents
• Applications
• Remote Configuration
• Resources
• Secret Management