# Feature list of Node-RED version 2

**URL:** <https://discourse.nodered.org/t/feature-list-of-node-red-version-2/44510>\
**Category:** General\
**Created:** [21 April 2021 18:22 UTC](https://discourse.nodered.org/t/feature-list-of-node-red-version-2/44510 "2021-04-21T18:22:50Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![drmibell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/drmibell/32/8424_2.png) [@drmibell](https://discourse.nodered.org/u/drmibell)\
**Post date:** [23 April 2021 19:38 UTC](https://discourse.nodered.org/t/feature-list-of-node-red-version-2/44510/11 "2021-04-23T19:38:54Z")

</div>

> [@paulkeates](#):
>
> it really worked and saved me lots of aggravations

That is good to know. How much effort/overhead is involved in using logstash? Or is it really necessary?

> [@rko](#):
>
> being able to see where all the messages are and what state our context is in, would be very helpful.

I realize that ideally you want this information when the flow has been stopped at a breakpoint, but sometimes a historical trace of the messages can help. The [complete node](https://discourse.nodered.org/t/using-done-complete-for-debugging/21572) can be useful for this, especially since most of the core nodes have now implemented the `done()` function.

---

_[View the full topic](https://discourse.nodered.org/t/feature-list-of-node-red-version-2/44510)._