Shareables When to share Delft-FEWS release version Always Delft-FEWS configuration When a specific workflowId or gui component is causing the issue Local DataStore When required or helpful for reproducing the issue Screenshot of Admin Interface Database trends Is it a new problem? What has changed? Has there been a recent configuration change? Problem description: - detailed, step by step description to reproduce the bug (Where exactly to click, which workflow to run, what settings/system time to use, from which menu the window can be opened (if it is a less commonly used tool), where in the display tree the given location/plot can be found, etc.) - a screenshot of reproducing the problem - a description what is the expected behavior and what happens instead - a screenshot of the bug happening - the Jira issue number of the feature / development that is linked to the bug (If known) Configuration: Depending on where the bug occurs the following might be entailed in configuration: - adapters - import/export folders - modules - models - client trust store - any other folder in the same directory as config, such as Archive, WarmStates, Cashes, etc. Local DataStore: -should contain data relevant to the issue Please note, that not all of these are necessary for all bugfixes, but most of these are needed for the majority of the issues. Including more than what is needed will not hinder bug fixing, adding too little will slow down support. (Especially when you have no idea what is wrong and where to look) Providing Delft-FEWS support with relevant log files, screenshots or even a copy of a config / local datastore may help us solving the issue more efficiently. Do not assume we know every detail of your system, so please give a detailed description where you encounter a problem. Below you will find some useful tips to analyse your system and provide useful information to the fews support helpdesk. In general: If it is a connection problem (with the Master Controller): If it is a problem with (failing) workflows on the Forecasting Shells If it is a problem in your Operator Client: Note Delft-FEWS will run through a VPN or via Remote Desktop Protocol, so having those connections available to us will improve the efficiency of our support. The ability to diagnose issues will depend upon the bandwidth for the connection.What to share when reporting issues to Delft-FEWS support
Remarks Just share the full log file, and check the build number is included. Problem description Always Clear steps and enough information how to reproduce the issue Additional context Always Logging When there is a stacktrace See also Howto activate debug mode Screenshots When required or helpful for reproducing the issue ALT-PrtScr F12->export->default config as zip file Collected Log files When there is an issue in the live system See also Collect System Log Files Replica When required or helpful for reproducing the issue F12->database->replicate database Thread dump When there is a deadlock How to create a Thread dump under Windows Movie When required or helpful for reproducing the issue F12->screen recording->start/resume recording When there are database performance issues See Database trends Provide clear problem descriptions
Provide additional context
How to help us to support you