The place to collect feedback for CamundaBPM.
For now, we are mainly looking to get your feedback for Camunda Cockpit – what you like, dislike, what you struggle with, etc.
We'd love to take your feedback into account when further developing our product!
seeing "null" as a value for unset elements
Most people do not use multi-tenancy and so any time a value for that appears in cockpit it's shown as "null" firstly it's too technical and secondly it takes up space in the UI that the user doesn't care about. This is the same with a bunch of other values like history time to live
Cannot see errors and exceptions in cockpit if they do not result from failed job
When executing a job (timers, async continuations, ...) fails, I can see an incident in cockpit and inspect the stacktrace. In situations where the engine gets triggered externally (initially start process instance) or completing a user task, delivering a message, I cannot see any record of the stacktrace in cockpit. In the case where the initial start of the process instance fails, the instance does not even exit at all. While this may be expected behavior for a transactional workflow engine, it is not always what the user wants. One user writes the following:
Es fliegen Incidents (sehe ich in Cockpit), aber ich weiß nicht so richtig wieso (deshalb mache ich ein tail -f catalina.out und dann einen Job Retry, dann sehe ich in der Konsole wo genau die Exception fliegt und warum, sehe ich in Cockpit derzeit nicht), dann fixe ich das in der Delegate Klasse, mache ein Redeploy und dann einen Job Retry.
Customer support service by UserEcho
