Splunk® App for Edge Hub and Augmented Reality

Splunk AR: Install and Use Splunk App for Edge Hub and Splunk AR

Acrobat logo Download manual as PDF


The Splunk App for AR is a required companion app for the Splunk AR mobile app. To learn more, see About the Splunk App for AR.
This documentation does not apply to the most recent version of Splunk® App for Edge Hub and Augmented Reality. For documentation on the most recent version, go to the latest release.
Acrobat logo Download topic as PDF

Should I use asset tags, object detection, beacons, or geofences with Splunk AR?

Before choosing to use asset tags, object detection, beacons, or geofences, consider what you want to associate data with, what data you want to associate, and how you want Splunk AR users to consume the data.

Here's a summary about each method:

Method Description
Asset tags

Asset tags are barcodes or Near Field Communication (NFC) devices that store data and wirelessly send information to devices. Asset tags allow Splunk AR to identify the data you're requesting. Splunk AR supports a variety of barcodes and NFC tags.

To learn more about asset tags, see Associate an object with a dashboard in Splunk AR with asset tags. Associate Splunk data with asset tags, and scan the tags with your mobile device to access the data.

Beacons Beacons are Bluetooth low energy (BLE) devices that broadcast their location and associated data to nearby mobile devices. Splunk AR supports the iBeacon protocol.

When you associate Splunk dashboards with beacons, Splunk AR presents the dashboards on your mobile device when you're in the beacon region. To learn more about beacons, see About beacons with Splunk AR.

Geofences Geofences are GPS-based boundaries that allow a device to trigger an action when the device enters or exits the area.

Create a virtual boundary on a GPS map, and associate dashboards with the boundary. Splunk AR then presents dashboards on your mobile device when you're located within the virtual boundary. To learn more about geofences, see About geofences with Splunk AR.

Object detection

Object detection lets you associate Splunk data with real-world objects without the need for asset tags. Splunk AR currently supports 2 kinds of object detection: text and logo.

Text detection uses optical character recognition (OCR) technology. It uses text as an asset identifier and a visual anchor for placing augmented reality visualizations.

Logo detection uses logos as an asset identifier and visual anchor for placing augmented reality visualizations. You can use one logo to distinguish multiple assets by using logo detection with beacons or geofences.

What do you want to associate data with?

When you want to associate data with a real-world object, use an asset tag or object detection. When you want to present users with data once they enter a location, use beacons or geofences. Use geofences for broader locations, and use beacons for smaller regions.

Asset tags and object detection work well with individual objects that generate or refer to data, such as equipment parts or retail products. Beacons broadcast dashboards to Splunk AR users within a proximity-based region, such as a room of equipment. Geofences give Splunk AR users access to dashboards once they enter a GPS-based location, such as a factory.

Think of these options as concentric rings for data communication. From asset tags and object detection to beacons to geofences, the locality of data communication extends from specific objects to proximity-based locations to GPS-based locations:

This is a diagram that describes asset tags and object detection, beacons, and geofences as concentric rings for data communication. The diagram provides examples for each method. Use asset tags individual objects. Use beacons with small, proximity-based locations. Use geofences with GPS-based locations. For example, use asset tags with equipment parts. Use a beacon to communicate data about the room of equipment. Use a geofence to communicate data about the entire factory where the room of equipment is located.

What data do you want to associate?

If you want to place visualizations over real-world objects, opt for AR workspaces. If you want to associate standard dashboards with objects or locations, go with non-AR dashboards.

Asset tags and object detection support both dashboards and AR workspaces, while beacons and geofences support dashboards.

After you know what data you want to associate and view with Splunk AR, choose an AR workspace or Splunk dashboard as a display option.

For more information about supported visualizations and dashboard configurations, see Visualization support for Connected Experiences apps in the Splunk Secure Gateway Release Notes manual.

Augmented reality data

If you want to investigate single data that's tied to objects in the real world, opt for an AR workspace. You can overlay these visualizations on objects using the Splunk AR camera.

For example, suppose you create an AR workspace that contains system values to communicate equipment health. You can overlay the augmented reality values on top of their respective components using the Splunk AR camera. A Splunk AR user can scan the asset tag, text, or logo that identifies that object and view the data overlaid on relevant parts of the equipment. The user gets data that updates in real time and can identify exactly which value is tied to what component.

To learn more about AR workspaces see About Splunk AR workspaces.

Non-Augmented Reality data

If you don't need to overlay data on real-world objects, go with Splunk dashboards.

For example, suppose you create a dashboard that shows sales data in a retail environment. You can create a geofence around the retailer's building to communicate high-level information, such as the number of working staff and overall sales trends. You can also place beacons in various departments to broadcast department-specific data, such as product popularity. You can associate data with asset tags, such as barcodes, to scan and get individual product sales stats and inventory count.

How do you want users to consume the data?

Users can consume data using the Splunk AR app actively or passively. Users actively consume data if they know what data they're looking for and exactly where to find it. For example, a retail worker can scan a barcode to get sales stats about a product. Users passively consume data when Splunk AR presents them with dashboards when they enter a certain location. For example, Splunk AR presents a factory worker with a dashboard that shows what equipment needs maintenance once they enter the factory location.

Implement assets for active data consumption, and set up beacons or geofences for passive data consumption.

Active data consumption

Assets tags and object detection require a user to actively retrieve the data. Splunk AR users use their mobile device to scan the asset tag, text, or logo that identifies the asset to view the AR workspace or Splunk dashboard.

Asset tags and object detection are useful for a retail employee who wants to get information about a particular product or a factory employee who wants to check the temperature of a sensor reading for a machine.

For example, suppose you create a dashboard that contains inventory count, sales data, and information about whether or not other store locations carry a product. You register the barcodes and associate data with all products in the store, so you can get real-time product information using Splunk AR. A retail customer might ask an employee if a that product is in stock. The employee scans the product's barcode, and Splunk AR returns a dashboard that provides inventory count and lets you know if the product is available at other stores. The data is updated in real time, so the employee can give the customer accurate information.

See About Splunk AR asset tags to learn more about assets.

Passive data consumption

Beacons and geofences require users to passively consume data. When Splunk AR users enter a beacon region or a geofence, Splunk AR presents them with dashboards on their mobile device. Beacons and geofences are useful for users who need to identify an issue without knowing exactly where the issue is located.

For example, suppose that a cell tower maintenance employee needs to figure out which cell tower and which part of a cell tower needs maintenance. When the employee enters the geofenced cell tower site and opens the Splunk AR app to view nearby geofences, Splunk AR presents a high-level dashboard about which cell tower is problematic. The employee can approach the problematic cell tower, where beacons embedded in equipment broadcast their own dashboards. With a geofence and beacons, the employee can figure out which cell tower and what particular equipment requires maintenance.

See About geofences with Splunk AR and About beacons with Splunk AR in the Use Splunk AR manual to learn more about beacons and geofences.

Last modified on 20 June, 2023
PREVIOUS
Get started with the Splunk App for AR
  NEXT
Get data into Splunk AR using a Raspberry Pi

This documentation applies to the following versions of Splunk® App for Edge Hub and Augmented Reality: 1.0.0, 1.10.0, 1.2.0, 1.2.1, 1.3.0, 1.4.1, 2.0.0, 2.0.2, 2.1.0, 3.0.0, 3.0.1, 4.0.0, 4.0.1, 4.1.1, 4.1.2, 4.2.1, 4.2.2, 4.3.0, 4.3.1


Was this documentation topic helpful?


You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters