Skip to main content

Dynamics AX CMA

The connector allows you to monitor:

  • Windows Server OS from 2003 SP2 version
  • Windows workstations from the XP version

Pack assets​

Templates​

The Monitoring Connector Dynamics AX CMA brings a host template:

  • App-Dynamics-AX-CMA-custom

The connector brings the following service templates (sorted by the host template they are attached to):

Service AliasService TemplateService Description
RIS-Import-InputApp-Dynamics-AX-RIS-Import-Input-CMA-customCheck import files presence
RIS-Import-ProcessingErrorsApp-Dynamics-AX-RIS-Import-ProcessingErrors-CMA-customCheck files importation failure
Service-RISApp-Dynamics-AX-Service-RIS-CMA-customCheck state of the RecurringIntegrationsScheduler service

The services listed above are created automatically when the App-Dynamics-AX-CMA-custom host template is used.

Collected metrics & status​

Here is the list of services for this connector, detailing all metrics linked to each service.

NameUnit
countcount

Prerequisites​

Network flow​

Only one TCP flow must be open from the host to the poller.

SourceDestinationProtocolPortPurpose
Monitored hostCollecteurTCP4317Configuration retrieval, and OpenTelemetry data flow

System prerequisites on the poller​

To be able to use the Centreon Monitoring agent, you must use a poller with at least version 24.10 for On Prem users of centreon-engine. The Centreon Monitoring agent will configure itself by connecting to Centreon Engine.

Configure Engine​

Configure how the poller and the agent will communicate. (This link directs you to the latest version of the OnPrem documentation. Use the version selector in the top right corner to switch to another version if you need to.)

System prerequisites on the monitored host​

The installer can be downloaded from the centreon-collect's releases page.

Installing the Centreon Monitoring Agent​

The installation and configuration procedure of the Centreon Monitoring Agent is detailed in this dedicated page. This includes installing the agent, and installing the plugins that will execute the non-native checks. (This link directs you to the latest version of the OnPrem documentation. Use the version selector in the top right corner to switch to another version if you need to.)

Installing the monitoring connector​

Pack​

The installation procedures for monitoring connectors are slightly different depending on whether your license is offline or online.

  1. If the platform uses an online license, you can skip the package installation instruction below as it is not required to have the connector displayed within the Configuration > Monitoring Connectors Manager menu. If the platform uses an offline license, install the package on the central server with the command corresponding to the operating system's package manager:
dnf install centreon-pack-applications-dynamics-ax-cma
  1. Whatever the license type (online or offline), install the Windows NSClient API connector through the Configuration > Monitoring Connectors Manager menu.

Plugin​

This connector relies on an integration supported by Centreon Engine and does not need a plugin.

Using the monitoring connector​

Using a host template provided by the connector​

  1. Log into Centreon and add a new host through Configuration > Hosts.
  2. Fill the Name, Alias & IP Address/DNS fields according to your ressource settings.
  3. Apply the App-Dynamics-AX-CMA-custom template to the host. A list of macros appears. Macros allow you to define how the connector will connect to the resource, and to customize the connector's behavior.
  4. Fill in the macros you want. Some macros are mandatory.
MacroDescriptionDefault valueMandatory
SYSTEMLANGUAGELanguage installed on the Dynamics365 system.en
CENTREONAGENTPLUGINSPath where the centreon_plugins.exe plugin can be found.C:/Program Files/Centreon/PluginsX
  1. Deploy the configuration. The host appears in the list of hosts, and on the Resources Status page. The command that is sent by the connector is displayed in the details panel of the host: it shows the values of the macros.

Using a service template provided by the connector​

  1. If you have used a host template and checked Create Services linked to the Template too, the services linked to the template have been created automatically, using the corresponding service templates. Otherwise, create manually the services you want and apply a service template to them.
  2. Fill in the macros you want (e.g. to change the thresholds for the alerts). Some macros are mandatory (see the table below).

Checks files in a directory tree, applies filters, and evaluates file metadata (size, timestamps, version, line count, etc.) for monitoring and alerting.

MacroDescriptionMandatoryAllowed valuesDefault valueExamples
PATHSRoot directory to search files in.XC:/RIS/Import/RIS General Ledger/Inputpath/to/file
PATTERNShell-style wildcards pattern to match filenames.
* can be used as a wildcard		*.xlsx
MAXDEPTHMax recursion depth.- 0: top only
- 1: include subdirs
- -1: recursively include all subdirs		0
OUTPUTSYNTAXOutput format string for the overall check result.Placeholders: {status}, {count}, {total}, {list}, {warn_count}, {warn_list}, {crit_count}, {crit_list}, {problem_count}, {problem_list}, {ok_count}, {ok_list}${status}: ${problem_count}/${count} files (${problem_list})
DETAILSYNTAXFormat for each file detail inside {list}.{path}, {filename}, {size}, {creation}, {access}, {written}, {version}, {line_count}, {extension}.${name}
OKSYNTAXOutput if all files are OK.{status}: {ok_count} files found - {ok_list}
FILTERFilter expression to select files for the check.nonesize > 1M && extension == '.dll'
WARNINGSTATUSFilter expression: files matching are considered WARNING.
CRITICALSTATUSFilter expression: files matching are considered CRITICAL.
WARNINGWARNING status items count must be strictly higher than this value to trigger WARNING.count > 50 = at least 1 file to trigger alert
CRITICALCRITICAL status items count must be strictly higher than this value to trigger CRITICAL.age > -1d or count > 200 = at least 1 file to trigger alert
VERBOSEDisplay detailed file info.false
TIMEOUTSet timeout for command execution120

Filter expressions​

Applies for FILTER, WARNINGSTATUS, CRITICALSTATUS.

Filter syntax is similar to C/SQL:

  • Numeric operators: ==, !=, >, <, >=, <=
  • Logical: && (AND), || (OR)
  • String equality: ==, != (note: single = is not valid)
  • IN/NOT IN: filename in ('myfile.txt'), version in ('1.0', '1.1')

Supported file metadata labels:

  • size (in bytes, supports units: K, Ko, M, Mo, G, Go)
  • line_count (line counting in txt file)
  • creation (file age in seconds since creation, supports units : w, d, h, m, s) no unit = s. Unit can’t be composed (ie : 1d3h)
  • access (file age in seconds since last access, supports units : w, d, h, m, s) no unit = s. Unit can’t be composed (ie : 1d3h)
  • written (file age in seconds since last modification, supports units : w, d, h, m, s) no unit = s. Unit can’t be composed (ie : 1d3h)
  • filename (name of the file, string comparison)
  • path (full file path, string comparison)
  • extension (file extension, e.g. '.dll')
  • version (for .exe/.dll files, string comparison)

You can also add this result list filter in WARNINGSTATUS and CRITICALSTATUS:

  • count number of items

Warning and Critical Status​

Files matching the WARNINGSTATUS/CRITICALSTATUS filters are considered WARNING/CRITICAL. You can combine with WARNING/CRITICAL to require multiple matches before changing the global state.

Examples​

Filters​

Applies for FILTER, WARNINGSTATUS, CRITICALSTATUS.

  • "size > 50M" # File larger than 50 MB
  • "extension == '.bak'" # Backup files
  • "size > 200m && extension == '.dll'" # Large DLLs
  • "count <= 0" # No file found
  • "filename in ('myfile.txt')" # Specific file by name
  • "filename == 'myfile.txt'" # Specific file by name (alternative)

File age check​

File age can be checked using 3 metadata labels, which can be mixed using logical operators :

  • creation (file age in seconds since creation, supports units : w, d, h, m, s) no unit = s. Unit can’t be composed (ie : 1d3h)
  • access (file age in seconds since last access, supports units : w, d, h, m, s) no unit = s. Unit can’t be composed (ie : 1d3h)
  • written (file age in seconds since last modification, supports units : w, d, h, m, s) no unit = s. Unit can’t be composed (ie : 1d3h)

“I want to trigger a CRITICAL alert if at least one file of my test directory has not be updated since 1 day or more, and WARNING alert if more than 12 hours and less than 1 day”

PATH= C:/Users/User/Documents/test
PATTERN= *.*
MAXDEPTH= -1,
DETAILSYNTAX= {filename}: {size}
WARNINGSTATUS= written > 12h
CRITICALSTATUS= written > 1d
WARNING= 0
CRITICAL= 0

File size check​

“I want to trigger CRITICAL alert if at least 1 DLLs in System32 (including subdirs without recursivity) size is >100M, and trigger WARNING alert if at least 2 DLLs size is >10M”

The extension filter can be done using PATTERN or FILTER.

PATH= C:/Windows/System32
PATTERN= *.dll
MAXDEPTH= 1,
OUTPUTSYNTAX= {status}: {problem_count}/{count} DLLs have issues: {problem_list}
DETAILSYNTAX= {filename}: {size} {version}
FILTER= extension == '.dll'
WARNINGSTATUS= size > 10m
CRITICALSTATUS= size > 100m
WARNING= 1
CRITICAL= 0

Note:

  • If "line_count" is used in any filter or output, line count calculation will be enabled (may impact performance).
  • Paths, patterns, and filters are case-insensitive on Windows.
  • Use / as the path separator instead of \ (e.g., C:/Users/...). Backslashes require extra escaping and may cause errors.

File presence check​

“I want to trigger a CRITICAL alert if file is not present“

PATH= C:/Users/User/Documents/test
PATTERN= myfile.txt
MAXDEPTH= -1,
DETAILSYNTAX= {filename}: {size}
WARNINGSTATUS=
CRITICALSTATUS= count < 0
WARNING=
CRITICAL= 0

“I want to trigger a CRITICAL alert if at least one file is present“

PATH= C:/Users/User/Documents/test
PATTERN= myfile.txt
MAXDEPTH= -1,
DETAILSYNTAX= {filename}: {size}
WARNINGSTATUS=
CRITICALSTATUS= count > 0
WARNING=
CRITICAL= 0
  1. Deploy the configuration. The service appears in the list of services, and on the Resources Status page. The command that is sent by the connector is displayed in the details panel of the service: it shows the values of the macros.

Troubleshooting​

Please find the troubleshooting documentation for the API-based plugins in this chapter if you cannot find the solution to your issue below.