- 5 minutes to read

Comments

A very handy collaboration feature in Nodinite is the ability to use comments to share insights about actions taken on Nodinite Log Events. For example: 'John Doe is working on the matter regarding order 1337.'

A User with access to Log Views can view and add comments to Log Events.

Adding Comments

The Comments tab provides a simple interface to add and view comments:

  • Comment input field - Type your comment in the text area at the top of the tab
  • Save button - Click the Save button to add your comment to the Log Event
  • Comment history - View all comments in chronological order with timestamp and author information

Add and View Comments for Log Event
The Comments tab showing the comment input field, existing comments with timestamps, and the user who added each comment.

Comments appear immediately after saving and include:

  • Time - When the comment was added, displayed in your local datetime (YYYY-MM-DD HH:MM:SS format). Hover over the timestamp to see the UTC time in a tooltip
  • Text - The comment content
  • By - The username of the person or system that created the comment

Tip

The Comments tab badge shows the number of comments (e.g., "Comments (2)") so you can quickly see if there's team activity on a Log Event before opening the tab.

Collaboration Examples

Real-world examples from the screenshot demonstrate effective comment usage:

  • "AI AI ??" - Quick question to get clarification from team members
  • "AI Promised to fix this" - Documenting ownership and commitment to resolve an issue

Comments create a conversation thread directly on the Log Event, eliminating the need for separate communication channels and ensuring context is never lost.

Comment Sources

Comments may originate from:

Comment
Example of a comment created by the Logging Service due to the MessageProcessingMaxBodySize - System Parameter.

Important

Individual comments cannot be deleted by Users.
This behavior is by design, intended to share (and protect) the fact that potentially sensitive information has been managed or tampered with.

Using Comments with Non-Events

Comments are particularly powerful when working with the Non-Events Agent, which monitors for missing or delayed messages. Once you investigate and resolve an issue, you can use comments combined with Log View filters to remove resolved alerts from view while preserving the audit trail.

Clearing Resolved Non-Event Alerts

Comments alone do not remove Log Events from Log Views. The Log View must be configured with a filter to exclude events based on comment content. For example, configure a filter like Any Comment != "Resolved" or Any Comment != "Fixed" to hide events once you've added a resolution comment.

You can also use operators like "Does not contain" to filter more flexibly. For example, setting Text Does not contain "fix" will hide any Log Event that has a comment containing the word "fix" (case-insensitive).

Log View Search Criteria Filter
Example filter: Text Does not contain "fix" - excludes any Log Event with a comment containing "fix".

This powerful combination allows you to:

  • Acknowledge investigation - Add a comment like "Resolved - scheduled maintenance caused delay" to dismiss the alert from filtered views
  • Document root cause - Explain what happened: "Fixed - Customer batch delayed due to upstream system outage"
  • Track resolution - Note actions taken: "Resolved - Contact established with supplier, delivery rescheduled"
  • Maintain audit trail - The Log Event and comment remain searchable in other Log Views (without the filter) for compliance and analysis

Comment on Non-Event
Add a comment to a Non-Event Log Event and use Log View filters to hide resolved alerts while preserving the record.

Tip

Configure your non-event Log Views with a filter like Any Comment != "Resolved" to automatically hide events once you add a resolution comment. This keeps your active alert view focused on unresolved issues.

Filter Configuration Examples

Common filter patterns for comment-based Log Event management:

  • Exact match exclusion: Field = "Text", Operator = "!=", Value = "Fixed"
  • Partial match exclusion: Field = "Text", Operator = "Does not contain", Value = "fix"
  • Status tracking: Field = "Text", Operator = "Does not contain", Value = "resolved"
  • Work in progress: Field = "Text", Operator = "Contains", Value = "WIP" (to show only active work)

The "Does not contain" operator is particularly useful as it works regardless of case and matches partial words, making your filters more flexible and user-friendly.

Additional Non-Event Comment Use Cases

Comments enhance non-event monitoring workflows when combined with Log View filters:

  • Business exceptions - "Resolved - Holiday schedule, expected zero orders this weekend"
  • Planned downtime - "Fixed - Maintenance window 2AM-4AM completed, system restored"
  • Pattern changes - "Acknowledged - New customer onboarding, lower transaction volume expected this week"
  • False positives - "Resolved - Threshold adjusted after observing pattern"
  • Escalation notes - "In Progress - Issue escalated to vendor, ticket #12345" (filter to show only unresolved)
  • SLA tracking - "Resolved - Response time exceeded due to network issues, customer notified"

By combining comments with Log View filters, you create a comprehensive record of integration health, anomalies, and team responses—all while keeping your active alert views focused on unresolved issues.

Next Step