Is explicitly writing to logs possible?

I have an incoming which checks multiple storages to see if the progress value in the storage is an empty array. This shows that the incoming routes which fill the storages are completed. Now one of the storages it’s progress value wasn’t empty and the check returned a negative result. How can I write info to the logs so that I can debug what storage/incoming wasn’t finished?

I’d like to second this question/feature request. It’d be great if we can force a write-to-log.

2 Likes

Hi @tommy, @floris,

Thank you for the valuable feedback.

We usually use storage to debug by writing things to the storage at the parts we want to check. However, we understand that it’s not a good way to debug, and providing a native feature would be a great addition to the integration process.

We will pass your feedback on to the team. We will let you know once we have an update.

Hi @tommy @floris

We’ve added your suggestion to our internal backlog for consideration. At this time, we don’t have an estimated timeline for when it might be implemented.

If you’d like to stay updated on new features and improvements, feel free to keep an eye on our release notes. Any updates related to this feedback will be shared there when available.

Thanks again for your input!

Ok, thanks. Now I want to write logs to a storage but in a storage, one cannot properly sort on Identifier, timestamp,.. What do you propose to log this properly?

@tommy +1. Little bit off, but sorting based on identifiers in storages would be great to have - especially when one has alot of rows…

1 Like

Hi @tommy @gerg.borsodi

Unfortunately, it’s currently not possible to sort storage entities when using Filesystem storages. However, when a new type of storage is introduced in the future, we plan to include this functionality as part of our improvements.

Alternatively, you can use storage API when storing the entities for logging purposes. The logs are always stored in the same order they are executed. Writing storage entities with the storage API allows you to view the entities as the payload in the HTTP request.

Please let us know if this workaround would work.

Hi @tommy @floris

We would like to inform you that the requested functionality will be released in version 3.97.0, which will be available for UAT environments mid-October, and for production environments late-October.

Once again, thank you for your feedback!

3 Likes