Troubleshoot Splunk AR
Make sure you have a good scanning environment and check for unsupported visualizations if you're running into issues with Splunk AR.
Unable to scan barcode
If you're having trouble scanning a barcode, make sure you have sufficient lighting and that the barcode is on a non-reflective surface. If you're still having trouble, try slowly moving the camera over a surface near the barcode. Pan the camera across the surface and over the barcode again.
You can also restart the scan if the AR workspaces seem out of place.
Here's how to restart a scan if you've already scanned an asset:
- Deselect the workspace.
- Tap the refresh button.
- Tap Discard.
This clears all AR workspaces on your screen and refreshes the AR scanning function.
Here's how to restart a scan if you haven't scanned an asset:
- Tap the three dots icon.
- Tap Start New Scan.
This refreshes the AR scanning function.
Unable to see a dashboard or panel
If the dashboard you're looking for isn't on the dashboard list, or a panel isn't loading, the dashboard may contain an unsupported visualization or configuration. See Visualization support in the Splunk Secure Gateway Release Notes manual for supported and unsupported visualizations.
An admin must choose which dashboards to make visible in the Connected Experiences apps. See Select which Splunk apps to show dashboards from in the mobile apps in Use Splunk Secure Gateway.
Unable to see a dashboard list
If you can't see your list of dashboards, you might be receiving a Spacebridge connection error. See Troubleshoot Splunk Secure Gateway connection issues and Troubleshoot Splunk Secure Gateway performance issues.
Dashboards or AR workspaces aren't loading when I scan an asset tag
Check your internet connection. You also might be running into a service connection error. See Troubleshoot Splunk Secure Gateway connection issues and Troubleshoot Splunk Secure Gateway performance issues.
AR workspace oriented incorrectly
Augmented reality visualizations rely on a visual reference to render in a specific position and size. You can optimize scanning AR workspaces by using QR codes created in the Splunk App for AR.
If you're using NFC tags, attach a detection image to the NFC tags. You can adjust and save visualizations for subsequent scans because the detection image provides Splunk AR a visual reference to anchor the AR workspace. See Save Splunk AR workspace orientation with NFC tags to learn how to use a detection image.
If you're using QR codes from the Splunk App for AR, use 4-by-4 centimeter QR codes. Splunk AR accepts 4-by-4 centimeters as a standard baseline size for a visual reference. If a QR code is larger, Splunk AR perceives the QR code as closer to the camera than it actually is and renders a relatively larger workspace. If a QR code is smaller than 4-by-4 centimeters, Splunk AR perceives the QR code as further from the camera and renders a relatively smaller workspace. A 4-by-4 centimeter QR code ensures that AR workspaces render in proper position and scale.
Device was unregistered after changing user credentials
If you or a Splunk admin changes your Splunk user credentials, then your device will be logged out.
To log in again, an admin must enable token authentication and you must log in again. See Enable token authentication to learn how to enable token authentication. and see Log in to a Splunk platform instance in a Connected Experiences app for how to log in.
You can view or share logs from the Splunk AR app with the Splunk Support team to further troubleshoot any issues you might be running into.
- Navigate to Settings.
- Long press the Settings header. This takes you to the Diagnostics screen.
- Select Logs.
- Select the ellipsis.
- To share the logs with the Splunk Support team, select Share.
Run Splunk SOAR Playbooks in Splunk AR |
This documentation applies to the following versions of Splunk® AR for iOS: 1.5.0, 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.1, 2.5.0, 3.0.0, 3.0.1, 3.0.2, 3.1.0, 3.1.1, 3.2.0, 3.2.1, 3.3.0, 3.4.1, 3.4.2, 3.4.3, 3.5.0, 3.5.1, 4.0.0, 5.0.1, 5.0.2, 5.0.3
Feedback submitted, thanks!