Will Freitag

Is this feature still planned to be implemented? It will be very useful since it's hard to explain (to a customer), that "lastSuccessCode: 500" does not mean, that the notifier...

Maybe related: Instead of enhancing the information, a notification can give, we could think about having metrics on the notifications (and other stuff, too)? See #4212

Sorry, you got me wrong, Fermín. There is nothing to complain about the current metrics, the notifications provide (except around the subject of this issue ;-) ). Additionally to the...

Exactly this is, what we do. We send data (test-data in a high frequency) and when an 400 is encountered, we simply retry (same session, same payload) and get an...

Great! I will test (tomorrow) and give feedback! Thanks!

All the same :-( Using `telefonicaiot/fiware-orion:latest` (Orion-Version "3.7.0-next") has the same result. I had the idea, that location or doubles in general might be a problem (you know best, comparing...

For completeness, this is, what I'm currently trying: Notification: ```JSON { "description": "MG", "subject": { "entities": [ { "idPattern": ".*", "type": "Vehicle", } ] , "condition":{ "attrs":["test_attribute"] } }, "notification":...

@fgalan The output is: ```JSON { "orion" : { "version" : "3.7.0-next", "uptime" : "0 d, 2 h, 18 m, 47 s", "git_hash" : "90d592b1293645f43cb12af49fe128c3e7aedb7a", "compile_time" : "Thu Sep 1...

What I did before (I'm using a Node-RED flow), is sending the above payload to Orion Context Broker using the verb PUT (id and type in URL and not in...

Here we go: OKAY means: Subscription works as expected, only sent on changed data. FAIL means: Subscription is firing always, even on identical data. OKAY: ```Java let simple = {...