The following settings require Administrative privileges to access and modify. Click the link below for more details about that topic:
Unique accounts can be set up for each user with assigned privileges.
Click Add New User at the bottom to add users, and click on an existing user to edit. Both options access the Add/Edit User window shown below.
The User Name is the text that will appear in the software; it can contain spaces and special characters. The Log In Name is used at log in and cannot contain spaces.
The User Name is the text that will appear in the software; it can contain spaces and special characters.
Log In Name and Password
The Log In Name is used at log in and cannot contain spaces.
Store the email associated to each user account.
A user can be deactivated from the Info360 site by using this toggle switch. This will disable the user's log in while maintaining any data associated with the account.
The following table summarizes the effect that Role has on privileges in Info360:
An image file can be associated to each user. This image will appear in the upper left corner of the Info360 site.
Email Server Set Up
In order for Info360 to send automatic alert emails, it requires an Email server to be set up. Any sent alert emails will be sent from the saved email server address.
Info360 requires the email, SMTP server and port.
Common email protocol to send an email message.
Port to be used on the server.
|Anonymous||Users do not need to provide credentials for the server.|
|From Email||Emails that will be used to send out notifications information.|
|Password||Password for the email above.|
To keep transactions private and secure, we need an SSL connection.
Because Info360 is accessed and operated via a web browser, the default set up doesn't have a lot of power to handle significant data processing. A solution is to install a Info360 Agent to run as a service on a machine within the local network, which can be used to handle intensive data processing like Mass Balance Analysis. Installing Info360 Agent doesn't provide a UI on the host machine, instead it functions as a background process that is ready to handle processing for a connected Info360 site.
After installing an Agent, add the Agent URL to the Info360 site using the Add New Info360 Agent icon.
Info360 Agent URL
|URL to agent application in IIS (open IIS > Default website > right-click agent application > click Browse).|
|Description||Description of agent.|
|Max Instance||Breaking down an agent to a number of smaller processes to work in parallel (minimum: 1 and maximum: 100).|
|SSL Connection||To keep transactions private and secure, we need an SSL connection.|
|Active||An agent will only worked if this is checked and active.|
Many cell phone providers have a domain name that can be used to send an email as an SMS to a phone. Info360 can use this functionality to send alert SMS messages to a cell phone if a Track is triggered.
The format to email a cell phone as text: [10-digit phone number]@[domain]
Example for AT&T: email@example.com
The Server Logs tab offers a location to query and see what the Info360 server and agent are doing behind the interface. This tab can be very useful during site configuration and debugging.
In order to access the log information in this tab, the log will need to be stored in the Info360 database. This is controlled in the Info360.ini File Logging Section: set Storage equal to "db" or "both". The alternative is for Info360 to store the log information in text files which accumulate through the day and are stored in the Log folder where Info360 is installed.
Furthermore, the amount of data stored in the log is controlled by the ClientMode setting in the Global section of the Info360.ini File. Set the value to "Debug" to get detailed log information, or set to "Release" to get only pertinent log data.
Querying the Server Log
The Log Filter provides several options to query out specific logged events.
Toggle this check box to return log events of basic system information. This category includes the largest bulk of events recorded in the log, including records of each sampling task performed and intervals when the Scheduler is waiting to run.
Use this option with a Search text of a sensor ID to find if and when a specific sensor is being sampled.
This category includes event comments that aide in identifying and resolving issues with retrieving data. Each query sent to historian databases will be shown, as well as whenever a sampling process finishes. Note: You must set ClientMode to Debug in the Info360.ini file to receive these log events.
Returns events logged by the Info360 Agent, which is the Info360 software service used to perform tasks like sensor sampling in the background on a regular basis.
Returns events logged by the Data Collection System Module, which is an add-on software used to routinely pull data from files such as CSV, XML, and JSON.
Returns errors incurred by the system. This will identify if there are any issues with sensor configuration data.
This category records when users log in and log out.
Returns any changes made by users to the server configuration, such as modifying sensor attributes.
This category records when changes are made to Workspace or Workspace elements such as Dashlets, BizBlocks, Patterns, etc. This category can be used to track the history of changes made to the database.
Returns all alerts that were triggered by any active Scheduler.
Returns instances where data is uploaded from a file. This most often occurs when manually loading updatable sensors.
The actions of specific users can be queried out by selecting a user. Alternately, [System] is the user associated with all background processes not initiated by a specific user.
[Success] and [Failure]
Each log is recorded as either a success or a failure, which can be used here to filter out the events you're looking for.
If you're looking for a specific error, then toggle Failure and untoggle Success.
Log Date Time
Each log event has an associated date and time that can be used to query events from a certain period.
The drop-down menu is used to help populate a recent time range, but ultimately the specific from and to date time values will be used in the query. A blank date in the upper limit box means that the query will apply no upper limit; events up to the current time will be retrieved.
Enter in custom text to further refine the filter based on the Server Response field. Only log events that contain the Search text in the Server Response field will be returned.
This field is not used for searching text in the specific user name or other fields. Use the other dedicated toggle options for this.
Server Log Actions
Available actions on the Server Logs page allow administrators to export and delete searced log data.
Runs the query current set up in the Log filter. See the above expandable table for more information on querying logged events.
Downloads a CSV file of the currently displayed log events. Use Search to control what events are displayed.
Delete Searched Logs
Deletes all currently displayed log event data from the database.
Opens a popup window with further information associated with the selected log event.
Deletes the selected log event from the database.
Server Log Cleanup
Available actions on the Server Logs page allow administrators to clean up server log data on schedule.
|Enables the scheduler to run every Frequency (days) for clean up.|
|Frequency (days)||Days you want to clean up logs iteratively (for example, if value is 30 then it will run every 30th day).|
|Source||Drop-down menu to select the source you want to clean up. Logs are stored in both DB and .net file based on the .ini file.|
In the screenshot below, two errors are highlighted in red that define the specific error occurring in a BizBlock calculation. In this case, a user was trying smooth out the data using moving average on a daily interval, but kept getting "No data available" as the output from the BizBlock. The message below pinpoints that there is not enough data at that interval to calculate the moving average.
Note that you will need to set the storage setting of the Logging section to "db" or "both" in the Info360.ini File to access the log information in the software.
Allows you to upload an image file that will be used as the banner in your Workspace.
Date Time Formatter
Allows you to select the Date and Time format from the drop-down menu.
Workspace Archive Scheduler
Allows you to set a particular duration (Never, Weekly, Monthly) to auto-generate a PDF snapshot of the workspace. The scheduling workspace archive process will run at midnight of the particular day. You can then share the exported PDF using the Share Workspace button in the Workspace view.
This functionality only runs when you are using Chrome version 78, 79 and 80. If you are using a different Chrome version, Info360 will return the following error message:
"Workspace archive scheduler is being disabled due to incompatible Chrome version. Please contact Innovyze support."