Crosser Node 3.1.0

Crosser Node 3.1.0

Release Note

Release date: 2023-12-20

Changes

Sending metrics for Host and Runtimes

Now that Crosser Control Center can handle metrics both for the Node and the deployed flows (runtimes), the Node will report metrics for the host as well as all flows.

The metrics reported for the host is

  • Uptime (in seconds)

  • CPU (in %)

  • Bytes Received (excluded data received from Crosser Control Center)

  • Bytes Sent (excluded data sent to Crosser Control Center)

  • HTTP requests (sent to the Node HTTP server)

  • MQTT messages in

  • MQTT messages out

  • Memory usage (in MB)

  • Warnings

  • Errors

The metrics reported for each runtime (flow) is

  • Uptime (in seconds)

  • CPU (in %)

  • Bytes Received (excluded data received from Crosser Control Center)

  • Bytes Sent (excluded data sent to Crosser Control Center)

  • Messages received

  • Message sent

  • Memory usage (in MB)

  • Warnings

  • Errors

Log Level for Status messages

When reporting Node status to the Crosser Control Center the log level was previously Information. It has now been changed to Debug to avoid filling the log with information about Node status being sent.

Update to SSL Protocol TLS13

In previous versions of the Node TLS12 was used, as of 3.1.0 the SSL Protocol used will be TLS13.

Bug Fixes

Undeploy Flow fails if already manually deleted

If a flow was deployed and then manually removed from disk it could not be undeployed from the Crosser Control Center. The job to un-deploy would always fail with a message that the file was not found.

This bug was introduced in 3.0.0 and fixed in 3.1.0.

Modules could receive data over MQTT before the Flow was started

When using the MQTT Sub Broker module, modules could receive data before settings were loaded.

This could cause various issues depending on the type of module being connected to the MQTT Sub Broker module.

This could only happen when using the MQTT Sub Broker module and a quick fix for older nodes would be to use the MQTT Sub Client modules instead of the MQTT Sub Broker module.

This bug was introduced in 2.6.0 and fixed in 3.1.0.



    • Related Articles

    • Crosser Security Overview

      Crosser Security Overview November 2023 About this document This document describes security aspects related to the Crosser Streaming Analytics solution. The Crosser Streaming Analytics solution The Crosser Streaming Analytics solution has two main ...

    • Crosser Node 2.5.3

      Crosser Node 2.5.3 May 2022 Bugfix - Prevent Crash When Getting ChannelClosedExceptions When running remote sessions with unstable network connections the node host process could crash due to not handling a ChannelClosed exception in a proper way.

    • Monitoring the Crosser Node

      Introduction Once you have your first flows deployed, you might think about how to integrate the Crosser Node and Flows into your existing monitoring solution. In this article we describe what options you have and how to utilize provided interfaces ...

    • Crosser Node 2.5.4

      Crosser Node 2.5.4 Note: Version 2.5.4 of the node has been pulled back due to critical issues that were identified after the release. Please upgrade to a later version. September 2022 Bugfix - Prevent Invalid Http Requests To Cause 100% CPU This bug ...

    • Crosser Node 2.5.6

      Crosser Node 2.5.6 - Performance improvements November 2022 FlowMessage Improvements In complex flows where the flow splits into several paths the FlowMessage needs to be cloned. When having large and complex structures in the FlowMessage this was a ...