- 4 minutes to read

Add or manage Message Type

This guide shows you how to manage Nodinite Message Types.

You can add a new Message Type, edit, or Delete an existing one from the list in the overview.

A Message Type can have the following relationships:

You will see the Search Field Expressions from user-defined Search Fields in read-only mode.
Manage Message Type
This example shows how to manage the Message Type.

Basic data fields

  • You must provide a unique Name to create the Message Type.
  • Description: Optionally, add a user-friendly description.
  • Web Site: Optionally, provide a quick link for end-users, such as a WIKI or SharePoint site with additional documentation.

Remove old messages based on Message Type (Days to keep)

The Logging Service periodically removes old Events, Context, and Bodies.

  • You define the retention period per Message Type.
  • The system only removes logged events that are in the processed state.

Manage Retention
This example shows how to manage retention for Message Types.

Days to keep Events

Set the number of days to keep events for a given Message Type. If you set the value to zero (0), the system removes events on the next cleanup run.
The 'Never remove Events' option keeps data in Nodinite forever.

When the system removes Log Events, it also deletes comments.

Days to keep Context

Set the number of days to keep context data for Log Events of a given Message Type. If you set the value to zero (0), the system removes context on the next cleanup run.
The 'Never remove Context' option keeps data in Nodinite forever.

This value cannot exceed the 'Days to keep Events'.

Days to keep Bodies

Set the number of days to keep bodies for events of a given Message Type. If you set the value to zero (0), the system removes bodies on the next cleanup run.
The 'Never remove Bodies' option keeps data in Nodinite forever.

This value cannot exceed the 'Days to keep Events'.

Visualization of the days to keep for events:

graph TD subgraph "fal:fa-envelope-open-text Days to keep Events" baseInformation(Information about</br>the Event itself) searchFieldValues(Search Field Values) comments(Comments) subgraph "far:fa-key Days to keep Context" conntextValues(&nbsp &nbsp &nbsp Context &nbsp &nbsp &nbsp) end subgraph "fal:fa-file-code Days to keep Bodies" Bodies(&nbsp &nbsp &nbsp Body &nbsp &nbsp &nbsp) end end

The system bases the default values for a new Message Type on System Parameters from the configuration database:

  • DaysToKeepMessageEventsDefault: Sets the default number of days to keep events. Deleting an event also deletes its data/body message. The system assigns this value to new message types as default. You must restart the Logging Service if you change this value.
  • DaysToKeepMessageContextDefault: New 5.3 Sets the default number of days to keep context for an event. The system assigns this value to new message types as default. You must restart the Logging Service if you change this value.
  • DaysToKeepMessageDataDefault: Sets the default number of days to keep data in an event. The system assigns this value to new message types as default. You must restart the Logging Service if you change this value.

If you log too many Messages or Events, data searches may slow down.

Tip

Adjust these settings to fit your business needs. Only keep the data you need.

Custom Fields

As part of the Repository Model, you can add Custom Field values to provide additional documentation about your Message Type.
Custom Fields
This example shows an assigned value from a Custom Field.

Services

The system lists Services associated with the Message Type. Click the link to go to the associated Service.

Search Field Expressions

The system lists Search Field Expressions associated with the Message Type. You can Add or manage Search Field in Log Administration.

Search Field
This example shows Search Fields in use with the Message Type.

Click the link to go to the associated Search Fields. Learn more in the 'Manage Search Field Expression' user guide.

Custom Metadata

As part of the Repository Model, you can add Custom Metadata to provide well-structured, additional documentation about the Message Type.

Statistics

Use perpetual Statistics to analyze traffic patterns for the selected Message Type. The statistics also show a list of tracked Endpoints on the Message Type.
Message Type Statistics
This example shows the recorded traffic pattern and its known Endpoints on the selected Message Type.

Next Step

Add or manage Search Field
Add or manage Service
Add or manage System

Message Types
Repository Model
Search Fields
Services
System
Endpoints
Log Views