How to enable Logging from Ghost Nodes flows to Nodinite
What is Ghost Nodes? Read more about this innovative new system integrations platform at the Ghost Nodes web site
Follow the steps outlined below in order to enable logging from Ghost Nodes to Nodinite.
In this step, you will open a modal in order to manage some logging options.
- From within the Ghost Studio, first create, or open an existing graph that you want to enable logging for.
- Then, click on link properties at the top menu.
In this step, you will set some basic settings to enable logging.
- Check Enable logging
- Uncheck Enable summary logs
In this step, you will add a Log pre-processor to the graph canvas.
In this step, you will link the NodiniteLogEventConverter with the adapter to receive events to be logged from and set some log-related properties.
In this step, you will manage the destination for the Nodinite JSON Log Events.
It is possible to use other log destinations. This example uses the file destination node. Review the Nodinite Pickup Service to select the best option for your business case.
Make sure the target folder is a highly available file share, otherwise you should log to a share that is local to the node where this graph runs. You do not want to get any problems due to problems with logging.
Before deploying, check the mandatory properties of the NodiniteLogEventConverter and change the properties according to your preferences.
The properties to be specified match 1:1 with the properties of a Nodinite JSON Log Event.
||Log Agent Value Id||6||Log Agent source, who sent the data? This value should rarely change between different graphs|
||Original Message TypeName||"https://nodinite.com/Customers/1.0#Batch"||Message Type Name|
||LogEvent Endpoint Type||Ghost Nodes||Select the type of Endpoint transport|
||Use UTC timestamps||Checked/Unchecked||Use datetime in ISO8601 format or use the local time|
||LogEvent Event Direction||0||Select the type of Direction for the Endpoint transport|
||ApplicationInterchangeId||""||Id for Application scope, use to keep related events together|
If you need logging from other adapters, repeat the steps as necessary by your requirements and specifications.
The output log files must now be consumed by the Nodinite Pickup Service.
- You should monitor the shares/folders with output files from Ghost Nodes. Use the Nodinite File Monitoring Agent.
- You can create monitoring to give you alerts for missing log events or when content does not conform to your standards. Use the Nodinite Non Events Monitoring Agent.
- You can probably use many other Nodinite Monitoring Agents to make sure every node and dependent resources in a Ghost Nodes installation, is healthy.