Login PI 3.1.42 (January 9, 2019)
- You can now generate custom events from the scripting language, that will show in the Login PI Dashboard.
- The engine automatically creates a screenshot when an error occurs in the logging folder of the session where the Login PI Engine is running.
- File and directory operations in the engine now have a continueOnError parameter
- The engine now supports reading environment variables
Changes / improvements:
- The engine now also reports back immediately after each measurement in an application script, instead of waiting until the end of the application run. It will feel much more reactive in the Login PI dashboard.
- When an environment is deleted all measurements and data related to that environment are also removed (irreversible)
- When an application is deleted all measurements and data related to that application are also removed (irreversible)
- Accounts are now ordered alphabetically
- When the dashboard percentages are below 1% it’s shows a fractional percentage
- Added a tooltip on item in the dashboard events that were cut-off by an ellipsis (…)
- Directly browsing to a URL is now possible (previously you were always redirected to the main page)
- The engine checks if the schedule is still enabled after all applications have been executed and logs off if the schedule is disabled
- Global e-mail settings frontend didn’t report back errors if you used invalid input
- The documentation tile now points to the correct link
- The engine has a new method to track processes which improves stability in closing processes
- The environment dashboard has improved sorting. It now orders on (in this specific order) Measurements over threshold, application failures and logon failures
- Environment variables can now be used in the application executable path and working directory
- When defining accounts you can also use the FQDN instead of netbios domain name. The engine supports both. (KB article needed)
- Scheduling has received a number of stability improvements
- The VMware Horizon View connector logs more info about failed connections
- The launcher issues a warning when running on windows 7. Only the console version is supported on this OS.
- Input validation has been added to the appliance menu
- Online updating is now possible from the appliance menu
- Added support for Hyper-V and XenServer (see Requirements)
- SLA Reporting would create a report for yesterday/last month when the environment didn’t exist then
- Deleting an application with results in an environment would prevent charting from loading for that environment
- Enabling the e-mail settings would already enable the feature without clicking “Done”
- Logging off action wasn’t shown in the logging when the engine fails during initialization
- Underscores weren’t properly translated to spaces in measurement names in charting
- The custom connector incorrectly reports back session failures
Login PI 3.1.34 (November 6, 2018)
This is the first generally available release of Login PI Release 3.
What's new - There are lots of new things in Release 3... but here are some highlights.
- Installation: Login PI is now delivered as a Virtual Appliance. There is no installation necessary and it only takes minutes before you are up and running.
- Logons and Applications: Logons and application scripts are now run and timed independently. You can easily turn on logons and whichever application workflows you'd like to run.
- Application Workflows: Say goodbye to the workload script that has all of the applications rolled up into one. Now applications can be added via the Web UI. For deeper application insights each application workflow can be customized in Visual Studio using our brand-new Login VSI workflow commands. Snippets are provided to make customizing super easy. Syntax highlighting, Intellisense and Autocompletion makes it even easier. All customized scripts can be uploaded using the Web UI.
- Groups and Filtering: User Accounts and Launchers are added to a general pool, enabling a higher degree of resiliency. Accounts and Launches can also be grouped to enable more discreet segmentation per environment.
- Dashboard: Multiple Environment Dashboard and deeper drill-down application performance and availability data
- Launcher: The Launcher can be downloaded from the Web UI which comes with a simple installer. The Launcher now runs as an application on the desktop
- Charts and Events
- Hour, Day, Month, Prediction Views
- Automated daily/monthly generation of SLA Reports
Differences between Release 2 and Release 3 (version 3.1.34)
- Profiles (PI2) are now called Environments (PI3)
- Thresholds (PI2) are now called Notifications (PI3)
- Connections (PI2) are now called Connectors (PI3)
- Thresholds for Notifications are not automatically generated. We advise referencing your SLAs or letting the virtual user run for a day or two and looking at the baseline values before creating a threshold.
- Target Engine: The target engine operates very similarly to Login PI 2, however a new and less obtrusive status bar will appear. Also, new application scripts are pulled every time before they run, so if you change an application script while the virtual user is logged in you will see your changes take effect on the next application run.
- Architecture: Login PI Release 3 uses Login VSI's next generation architecture. This is a modern Docker microservices architecture running on Debian, leveraging Microsoft .NET Core. Very scalable, reliable and secure.
- Logon and Latency Metrics: Login PI Release 3, version 3.1.34 will not ship with Logon statistics or Protocol Latency metrics. They will be added in subsequent versions of Release 3 very soon.
- There is no "Daily Schedule" feature in Release 3. This was sometimes used for configuring backup windows
- Migration: Login PI 2 Data cannot be migrated to Release 3. We recommend running Login PI 2 and Login PI 3 in parallel until your data retention policy has been met with Login PI 3, after which time you can decommission or backup and archive Login PI 2.
- Database: The Login PI 3 Virtual Appliance uses an embedded database, so an external database is not required or supported. Support for external databases will be provided in subsequent versions.
- Because Login PI no longer installs as a Microsoft Windows Server, Microsoft Event Viewer will no longer carry Login PI events. All events can be discovered via the ReSTful Web API.
- Login PI 3.1.34 will ship with a locally configured single administrative user. Active Directory Administrators and Read-Only users will be provided in subsequent versions.
- Active and valid Login PI 2.x licenses may be used with Login PI Release 3