- 0 minutes to read
</i> Configure Nodinite Pickup Service Logging Agent for Mulesoft AnypointMQ Integration">

Release Notes

Mulesoft AnypointMQ Configuration Example

Effortlessly integrate your enterprise systems by configuring the Nodinite Pickup Logging Service to fetch JSON Log Events directly from your Mulesoft AnypointMQ queues. This guide walks you through secure, scalable, and reliable log event collection, ensuring your business-critical data is always available for analysis and compliance.

-* ✅ Seamless integration with Mulesoft AnypointMQ
-* ✅ Secure and reliable log event collection
-* ✅ Scalable setup for enterprise environments
-* ✅ Long-term storage and compliance-ready

graph TD subgraph "Mulesoft AnypointMQ" roS(fal:fa-list Queue) roBO(fal:fa-trash-can Dead letter queue) end subgraph "Nodinite instance" roPS(fal:fa-truck-pickup Pickup Service) roPS -.->|Bad/invalid messages| roBO roS --> roPS roPS --> |Long term storage|roDB(fal:fa-database Log Database) end

The diagram above illustrates how the Pickup Service interacts with AnypointMQ queues, processes messages, and stores them in the Nodinite Log Database. Invalid messages are routed to the Dead Letter Queue for further review.

AnypointMQs

The AnypointMQs section lets you manage all Mulesoft AnypointMQ sources for your log events.

You configure these sources in the Settings.json file, which uses JSON format. The default path is:

C:\Program Files\Nodinite\Logging Agent - Pickup Service\Settings.json

{
  ...
  "AnypointMQs": [
                      {
      "Enabled": true,
      "LogAPI": "http://localhost/Nodinite/Dev/LogAPI/",
      "UseConfigurationDatabase": false,
      "ConfigurationDatabaseConnectionString": null,
      "ActiveConsumers": 1,
      "Username": "nodinite-reader",
      "Password":"1337",
      "Environment": "prod",
      "EnvironmentId" : "f7a16b7b-1337-4cb5-93ba-1e5289f707ec",
      "OrganizationId": "75ec82b6-f930-4ea2-1337-7c56ee24c9d3",
      "UseConnectedApp": true,
      "IsEuPanel": false,
      "ClientId": "9186414a9dc4dfc94c4ccf670d25e4e",
      "ClientSecret": "replaceme",
      "RegionId": "eu-west-1",
      "Queue": "LogEvents",
      "DeadLetterQueue": "LogEvents.dlq",
       "ReplaceRules": [
        {
          "Name": "Fix Endpoint real customer id to {customerId}",
          "ReplaceName": false,
          "ReplaceUri": true,
          "Pattern": "/([0-9]{4,})$",
          "Group1Value": "{customerId}"
        }]
    }]
  ...                      
}

AnypointMQs is an array of AnypointMQ queue configurations. Each entry defines how the Log Agent connects to and processes messages from a specific AnypointMQ queue. This setup ensures your Nodinite JSON Log Events are reliably collected and managed.

Property Description Value Example Comment
ActiveConsumers Number of threads to run 1 Currently limited to 1 thread
Username The name of the user to log on with nodinite-reader
Password Password for user 1337
Environment The name of the environment Test
EnvironmentId Identifier for environment f7a16b7b-1337-4cb5-93ba-1e5289f707ec Guid
OrganizationId Identifier for organization 65ec82b6-f930-4ea2-1337-7c56ee24c9d3 Guid
RegionId Name of region eu-west-1 According to your run-time
UseConnectedApp Flag to use Connected App true or false True when ClientId and ClientSecret is set
IsEuPanel True when using EU control plane true or false
ClientId ClientId when using Connected App option 9186414a9dc4dfc94c4ccf670d25e4e
ClientSecret ClientSecret when using Connected App option replaceme
Queue Name of the queue with JSON Log Events Nodinite-LogEvents
DeadLetterQueue Name of queue for invalid Log Events Nodinite-LogEvents.DLQ
Enabled See the Shared Configuration section for more info
LogAPI See the Shared Configuration section for more info
UseConfigurationDatabase See the Shared Configuration section for more info
ConfigurationDatabaseConnectionString See the Shared Configuration section for more info
ReplaceRules See the shared Replace Rules section for more info

Important

You must restart the Nodinite Pickup Logging Service for configuration changes to take effect.

Next Step

Configure