Instructions, product packs, Instruction sets and permissions
Tachyon lets you investigate your network using questions and actions, which are collectively known as Instructions.
You can load Instructions into Tachyon, either individually or via a Product Pack, which is essentially a zip file containing one or more Instructions. Tachyon comes with a range of pre-framed questions and actions in the form of product packs, providing extensive out-of-the-box capabilities that can be extended as new and updated product packs are made available.
Tachyon permissions for the Instructions are handled using Instruction sets. You create Instruction sets, then define roles which specify particular permissions on those sets and then assign the roles to users. Each Instruction is only allowed to reside in one Instruction Set, which associates it with a role and thereby the users that have that role and can run the Instruction. The roles have associated Management groups that determine the devices that users with the role have access to.
When Instructions are loaded into Tachyon they are placed in the default Unassigned Instruction Set, so you must move them into previously created Instruction sets before they can be run.
Connectors are used to connect to other 1E and third party systems and populate repositories. When more than one connector to different data sources are used, the information from those different data sources is de-duplicated and normalized into a single cohesive view that is then stored in a repository. In this way you can use the data from different sources to augment each other and build a better picture of "what's out there?". For example, you can sync inventory data from Configuration Manager into an inventory repository, which will fetch information about your Windows devices. You could then augment that with inventory data synced from Tachyon which could include information about non-Windows devices where the Tachyon client has been installed.
For more information on connectors please refer to:
The following connectors are supported:
- BigFix connector — Connects to a BigFix Inventory database server.
- BigFixInv connector — Connects to a BigFix Inventory database.
- File Upload connector — Uploads inventory data from a folder containing tab (TSV) and comma (CSV) separated value file(s).
- InTune connector — Connects to an InTune application and pulls in inventory and usage data.
- Microsoft Office 365 connector — Connects to an Office 365 application in InTune and pulls in inventory and usage data.
- Oracle LMS connector — Connects to Oracle LMS and queries it for inventory information.
- ServiceNow connector — Connects to a ServiceNow instance to import basic inventory data into SLA Platform.
- System Center Configuration Manager connector — Connects to a Configuration Manager database and pulls in inventory and usage data.
- Tachyon connector — Connects the Tachyon and SLA components to support Management group and Tachyon Powered Inventory features. The Tachyon Powered Inventory feature uses instructions to fetch inventory data from Tachyon clients, and is a prerequisite for Patch Success.
- vCenter connector — Connects to a vCenter server and pulls in inventory data.
- Windows Server Update Services connector — Connects to a WSUS database and pulls in patch data.
Repositories are used by applications to process and store information. For example the Patch Success application uses both an inventory and a BI repository to process the information needed to report on how successful patching is in your enterprise. Normally a connector is used to connect a data source to an appropriate repository.
Repositories are also useful when you want to segregate different types of data. For example, you could have one inventory repository for Configuration Manager inventory data, and another one for BigFix data. Alternatively, you can have connectors to different inventory sources pushing data into one repository. Any Management Groups that you create will span all the repositories you have.
For more information on managing repositories please refer to:
Custom properties are generally associated with Explorer and can be used when setting coverage tags to target Instructions to particular devices. The custom properties must be defined by a custom properties administrator before they can be used to tag devices or used to set the coverage of Instructions.
This is done from the Settings→Configuration→Custom properties page, which can be viewed by users with any of the following roles:
- Global Administrators
- Custom Properties Administrators.
For more information on managing and using custom properties please refer to:
Schedules can be created to execute specific operations on repositories in Tachyon so that they are kept up to date with their data sources and processing. These operations include:
- Syncing data sources to repositories using connectors
- Processing the BI data cube.
Repository schedules are different to Instruction schedules that can be set in Explorer.
For more information on setting schedules please refer to:
Consumers, Applications, Components and Providers
There are pages in the Settings application for each of these. They are described in the following table:
These can access Tachyon using the Tachyon Consumer API. To enhance the security of the Tachyon system, only consumers that have been registered on the Settings→Configuration→Consumers page will be allowed to access Tachyon.
|Applications||Features of Tachyon that are hosted in the Tachyon Portal. Applications are generally Consumers as they need to interact with Tachyon using the Tachyon API. These are available on the Switch App menu.|
|Components||These form part of SLA and cannot be changed or altered by a user. These can be viewed using the Settings→Configuration→Components page.|
|Providers||These are components that can be configured to provide a particular operation in SLA. These can be viewed and configured using the Settings→Configuration→Provider configuration page.|
Information on your Tachyon license is available, as well as the ability to re-activate it following an update.
You can view information on the Tachyon system information for the Consumer, Coordinator, Background channel, Core and Switch.
Monitoring log files
The monitoring pages let you view how Tachyon is performing its tasks. Four key log pages are provided:
|Process log||Whenever you execute a sync or process a repository the steps are displayed here. This page is updated in real-time and shows the status of each step as it happens.|
|Sync log||The results of performing a sync are displayed here.|
|Infrastructure log||Information on the Tachyon infrastructure is displayed here, such as: license status and instruction workflow.|
|Audit information log||This page displays information on the Instructions that have been run in Explorer. This includes the instruction text and the user that requested it.|
Defining users and roles
Tachyon users or groups can be added from AD. They can be assigned roles that determine what aspects of Tachyon they can access. Custom roles can be created that let you associate particular permissions on particular Instruction sets for particular management groups.
Management groups use inventory-based rules to define groups of particular devices, they are implemented in SLA and then made available to Tachyon applications and other consumers. After a management group is defined, each time the inventory is updated the device membership of the groups is re-evaluated by applying the management group's rules to the new inventory.
Custom roles can be created that tie particular Instruction sets to particular management groups. This means you can not only set the permissions for users to access the Instructions in specific Instructions sets, you can also determine which devices they can target using those Instructions.
Once defined, management groups can then be used to set the coverage for Instructions in Explorer and also which devices can be targeted by particular users. Management groups are also used by the Patch success and Guaranteed state applications to determine which devices are being targeted.
Uploading Instructions into Tachyon and creating Instruction sets
You determine the capabilities of Explorer by uploading Instructions from product packs into Tachyon. Product packs are either provided with the release or downloaded from the Tachyon Exchange. Once the Instructions have been uploaded into Tachyon you then need to put them into Instruction sets. The Instruction sets can then be associated with custom roles to determine the permissions applied to the Instructions. The custom roles are then applied to users to determine which Instructions each user has access to.