If at any point you face issues with Bloom and we suspect this is due to a defect that lies with the application, you may be asked by Neo4j technical support to gather further traces.
Steps to gather the debug traces:
- Alter the URL you use to access Bloom and append
&LOGS_LEVEL=debug
to the URL and reload the page.
Note: If you are using SSO to access Bloom, please perform this step once Bloom loads after your SSO redirect. - Trigger the issue
- Open the Web browser developer console
- If using Chrome as your web browser:
- Open the developer tools console: Click the three dots next to your profile picture
- Select "More tools"->"Developer Tools"
- Select "Console" in the bottom tier
- Open the developer tools console: Click the three dots next to your profile picture
- If you use Firefox as your web browser
- Open the developer tools console: Select the menu (the three lines icon at the top right)
- Select "More Tools"->"Browser Console"
- Select "Console" in the bottom tier.
- Open the developer tools console: Select the menu (the three lines icon at the top right)
- If using Chrome as your web browser:
- Type and execute
bloom_da()
- A zip file will be created and downloaded with the information needed. Please save it and share this in your support ticket.
For example (on Google Chrome), this is how this looks like:
Comments
0 comments
Please sign in to leave a comment.