Advanced Monitoring Solutions is dedicated to the development, installation and maintenance of various types of metering, monitoring and data acquisition systems. These systems includes AMR (automated meter reading) systems for large buildings and shopping malls, electrical load profile recording and electrical energy verifying.
A BAP System Log ABAP Update Errors ABAP Application Log Log File Monitoring (non-ABAP) Please note that minimum of SAP Solution manager 7.1 SP12 is required. Your starting point is transaction GPAADMIN (except for Exception Monitoring),Type:Guided Procedure,Application area: Advanced Monitoring Application. See above SCN page. Wireless Temperature Monitoring Solutions for Hospitals, Healthcare, Medical and Research Facilities. Is a wireless temperature monitoring company with real time remote temp monitor solutions designed specifically for hospitals, pharmacies, laboratories, blood banks, tissue banks, dietary food services and more. Learn how to navigate the advanced settings of xFi. Learn how to navigate the advanced settings of xFi. Xfinity xFi Network Settings and Advanced Settings. . Open Advanced System Care 4. In the right pane: Right click on the PMonitor icon. Hover the cursor over Send to. Click on Desktop (create shortcut) Edit: By the way, it doesn't disappear off my desktop either. All the best, woz of oz.
« Machine learning settings in ElasticsearchNode »
By default, Elasticsearch monitoring features are enabled but data collection is disabled.To enable data collection, use the
xpack.monitoring.collection.enabled
setting.Except where noted otherwise, these settings can be dynamically updated on alive cluster with the cluster-update-settings API.
To adjust how monitoring data is displayed in the monitoring UI, configure
xpack.monitoring
settings inkibana.yml
. To control how monitoring data is collected from Logstash,configure monitoring settings in logstash.yml
.For more information, see Monitor a cluster.
General monitoring settingsedit
xpack.monitoring.enabled
- [7.8.0]Deprecated in 7.8.0. Basic License features should always be enabled(Static) This deprecated setting has no effect.
Monitoring collection settingsedit
The
xpack.monitoring.collection
settings control how data is collected fromyour Elasticsearch nodes.xpack.monitoring.collection.enabled
- (Dynamic) Set to
true
to enable the collection ofmonitoring data. When this setting isfalse
(default), Elasticsearch monitoring data isnot collected and all monitoring data from other sources such as Kibana, Beats,and Logstash is ignored.
xpack.monitoring.collection.interval
[6.3.0]Deprecated in 6.3.0. Use
xpack.monitoring.collection.enabled
set to false
instead.(Dynamic) Setting to -1
to disable data collectionis no longer supported beginning with 7.0.0.Controls how often data samples are collected. Defaults to
10s
. If youmodify the collection interval, set the xpack.monitoring.min_interval_seconds
option in kibana.yml
to the same value.xpack.monitoring.elasticsearch.collection.enabled
true
. This is different fromxpack.monitoring.collection.enabled
, which allows you to enable or disable allmonitoring collection. However, this setting simply disables the collection ofElasticsearch data while still allowing other data (e.g., Kibana, Logstash, Beats, or APMServer monitoring data) to pass through this cluster.xpack.monitoring.collection.cluster.stats.timeout
10s
.xpack.monitoring.collection.node.stats.timeout
10s
.xpack.monitoring.collection.indices
test1,test2,test3
. Names caninclude wildcards, for example test*
. You can explicitly exclude indices byprepending -
. For example test*,-test3
will monitor all indexes that startwith test
except for test3
. System indices like .security* or .kibana*always start with a .
and generally should be monitored. Consider adding .*
to the list of indices ensure monitoring of system indices. For example:.*,test*,-test3
xpack.monitoring.collection.index.stats.timeout
10s
.xpack.monitoring.collection.index.recovery.active_only
true
to collect only active recoveries. Defaults to false
.xpack.monitoring.collection.index.recovery.timeout
10s
.xpack.monitoring.history.duration
(Dynamic) Retention duration beyond which theindices created by a monitoring exporter are automatically deleted, intime units. Defaults to
7d
(7 days).This setting has a minimum value of
1d
(1 day) to ensure that something isbeing monitored and it cannot be disabled.This setting currently impacts only
local
-type exporters. Indicescreated using the http
exporter are not deleted automatically.xpack.monitoring.exporters
- (Static) Configures where the agent stores monitoringdata. By default, the agent uses a local exporter that indexes monitoring dataon the cluster where it is installed. Use an HTTP exporter to send data to aseparate monitoring cluster. For more information, seeLocal exporter settings,HTTP exporter settings, and How it works.
Local exporter settingsedit
The
local
exporter is the default exporter used by monitoring features. As thename is meant to imply, it exports data to the local cluster, which means thatthere is not much needed to be configured.If you do not supply any exporters, then the monitoring features automaticallycreate one for you. If any exporter is provided, then no default is added.
type
- The value for a Local exporter must always be
local
and it is required. use_ingest
- Whether to supply a placeholder pipeline to the cluster and a pipeline processorwith every bulk request. The default value is
true
. If disabled, then it meansthat it will not use pipelines, which means that a future release cannotautomatically upgrade bulk requests to future-proof them. cluster_alerts.management.enabled
- Whether to create cluster alerts for this cluster. The default value is
true
.To use this feature, Watcher must be enabled. If you have a basic license,cluster alerts are not displayed. wait_master.timeout
- Time to wait for the master node to setup
local
exporter for monitoring, intime units. After that wait period, the non-master nodes warn theuser for possible missing configuration. Defaults to30s
.
HTTP exporter settingsedit
The following lists settings that can be supplied with the
http
exporter.All settings are shown as what follows the name you select for your exporter:type
http
and it is required.host
Host supports multiple formats, both as an array or as a single value. Supportedformats include
hostname
, hostname:port
,http://hostname
http://hostname:port
, https://hostname
, andhttps://hostname:port
. Hosts cannot be assumed. The default scheme is alwayshttp
and the default port is always 9200
if not supplied as part of thehost
string.auth.username
auth.secure_password
or auth.password
issupplied.auth.secure_password
auth.username
. Takes precedence over auth.password
if it isalso specified.auth.password
auth.secure_password
instead. The password for theauth.username
. If auth.secure_password
is also specified, this setting isignored.connection.timeout
6s
.connection.read_timeout
10 * connection.timeout
(60s
if neither are set).ssl
proxy.base_path
/base/path
(e.g., bulkrequests would then be sent as /base/path/_bulk
). There is no default value.headers
Optional headers that are added to every request, which can assist with routingrequests through proxies.
Array-based headers are sent
n
times where n
is the size of the array.Content-Type
and Content-Length
cannot be set. Any headers created by themonitoring agent will override anything defined here.index.name.time_format
yyyy.MM.dd
, which is why the indicesare created daily.use_ingest
true
. Ifdisabled, then it means that it will not use pipelines, which means that afuture release cannot automatically upgrade bulk requests to future-proof them.cluster_alerts.management.enabled
true
.To use this feature, Watcher must be enabled. If you have a basic license,cluster alerts are not displayed.cluster_alerts.management.blacklist
Prevents the creation of specific cluster alerts. It also removes any applicablewatches that already exist in the current cluster.
You can add any of the following watch identifiers to the list of blocked alerts:
![Estatistica 4 2 1 – advanced system monitoring systems Estatistica 4 2 1 – advanced system monitoring systems](https://is4-ssl.mzstatic.com/image/thumb/Purple118/v4/1d/af/ad/1dafadaf-bcc2-0ea5-c05d-aa6ce11f21be/pr_source.png/942x0w.png)
elasticsearch_cluster_status
elasticsearch_version_mismatch
elasticsearch_nodes
kibana_version_mismatch
logstash_version_mismatch
xpack_license_expiration
For example:
['elasticsearch_version_mismatch','xpack_license_expiration']
.You can configure the following TLS/SSL settings.
xpack.monitoring.exporters.$NAME.ssl.supported_protocols
(Static)Supported protocols with versions. Valid protocols:
SSLv2Hello
,SSLv3
, TLSv1
, TLSv1.1
, TLSv1.2
, TLSv1.3
. If the JVM’s SSL provider supports TLSv1.3,the default is TLSv1.3,TLSv1.2,TLSv1.1
. Otherwise, the default isTLSv1.2,TLSv1.1
.If
xpack.security.fips_mode.enabled
is true
, you cannot use SSLv2Hello
or SSLv3
. See FIPS 140-2.xpack.monitoring.exporters.$NAME.ssl.verification_mode
(Static)Controls the verification of certificates.Controls the verification of certificates.
Valid values are:
full
, which verifies that the provided certificate is signed by a trustedauthority (CA) and also verifies that the server’s hostname (or IP address)matches the names identified within the certificate.certificate
, which verifies that the provided certificate is signed by atrusted authority (CA), but does not perform any hostname verification.none
, which performs no verification of the server’s certificate. Thismode disables many of the security benefits of SSL/TLS and should only be usedafter very careful consideration. It is primarily intended as a temporarydiagnostic mechanism when attempting to resolve TLS errors; its use onproduction clusters is strongly discouraged.The default value isfull
.
xpack.monitoring.exporters.$NAME.ssl.cipher_suites
(Static)Supported cipher suites vary depending on which version of Java you use. Forexample, for version 12 the default value is
TLS_AES_256_GCM_SHA384
,TLS_AES_128_GCM_SHA256
, TLS_CHACHA20_POLY1305_SHA256
,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
, TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
,TLS_RSA_WITH_AES_256_GCM_SHA384
, TLS_RSA_WITH_AES_128_GCM_SHA256
,TLS_RSA_WITH_AES_256_CBC_SHA256
, TLS_RSA_WITH_AES_128_CBC_SHA256
,TLS_RSA_WITH_AES_256_CBC_SHA
, TLS_RSA_WITH_AES_128_CBC_SHA
.For more information, see Oracle’sJava Cryptography Architecture documentation.
X-Pack monitoring TLS/SSL key and trusted certificate settingsedit
The following settings are used to specify a private key, certificate, and thetrusted certificates that should be used when communicating over an SSL/TLS connection.A private key and certificate are optional and would be used if the server requires client authentication for PKIauthentication.
When using PEM encoded files, use the following settings:
xpack.monitoring.exporters.$NAME.ssl.key
(Static)Path to a PEM encoded file containing the private key.
If HTTP client authentication is required, it uses this file. You cannot usethis setting and
ssl.keystore.path
at the same time.xpack.monitoring.exporters.$NAME.ssl.key_passphrase
(Static)The passphrase that is used to decrypt the private key. Since the key might notbe encrypted, this value is optional.
You cannot use this setting and
ssl.secure_key_passphrase
at the same time.xpack.monitoring.exporters.$NAME.ssl.secure_key_passphrase
xpack.monitoring.exporters.$NAME.ssl.certificate
(Static)Specifies the path for the PEM encoded certificate (or certificate chain) that isassociated with the key.
This setting can be used only if
ssl.key
is set.xpack.monitoring.exporters.$NAME.ssl.certificate_authorities
(Static)List of paths to PEM encoded certificate files that should be trusted.
This setting and
ssl.truststore.path
cannot be used at the same time.When using Java keystore files (JKS), which contain the private key, certificateand certificates that should be trusted, use the following settings:
xpack.monitoring.exporters.$NAME.ssl.keystore.path
(Static)The path for the keystore file that contains a private key and certificate.
It must be either a Java keystore (jks) or a PKCS#12 file. You cannot use thissetting and
ssl.key
at the same time.xpack.monitoring.exporters.$NAME.ssl.keystore.password
xpack.monitoring.exporters.$NAME.ssl.keystore.secure_password
xpack.monitoring.exporters.$NAME.ssl.keystore.key_password
(Static)The password for the key in the keystore. The default is the keystore password.
You cannot use this setting and
ssl.keystore.secure_password
at the same time.xpack.monitoring.exporters.$NAME.ssl.keystore.secure_key_password
xpack.monitoring.exporters.$NAME.ssl.truststore.path
(Static)The path for the keystore that contains the certificates to trust. It must beeither a Java keystore (jks) or a PKCS#12 file.
You cannot use this setting and
ssl.certificate_authorities
at the same time.xpack.monitoring.exporters.$NAME.ssl.truststore.password
(Static)The password for the truststore.
You cannot use this setting and
ssl.truststore.secure_password
at the sametime.xpack.monitoring.exporters.$NAME.ssl.truststore.secure_password
Elasticsearch can be configured to use PKCS#12 container files (
.p12
or .pfx
files)that contain the private key, certificate and certificates that should be trusted.PKCS#12 files are configured in the same way as Java keystore files:
xpack.monitoring.exporters.$NAME.ssl.keystore.path
(Static)The path for the keystore file that contains a private key and certificate.
It must be either a Java keystore (jks) or a PKCS#12 file. You cannot use thissetting and
ssl.key
at the same time.xpack.monitoring.exporters.$NAME.ssl.keystore.type
jks
or PKCS12
. If thekeystore path ends in '.p12', '.pfx', or '.pkcs12', this setting defaultsto PKCS12
. Otherwise, it defaults to jks
.xpack.monitoring.exporters.$NAME.ssl.keystore.password
xpack.monitoring.exporters.$NAME.ssl.keystore.secure_password
xpack.monitoring.exporters.$NAME.ssl.keystore.key_password
(Static)The password for the key in the keystore. The default is the keystore password.
You cannot use this setting and
ssl.keystore.secure_password
at the same time.xpack.monitoring.exporters.$NAME.ssl.keystore.secure_key_password
xpack.monitoring.exporters.$NAME.ssl.truststore.path
(Static)The path for the keystore that contains the certificates to trust. It must beeither a Java keystore (jks) or a PKCS#12 file.
You cannot use this setting and
ssl.certificate_authorities
at the same time.xpack.monitoring.exporters.$NAME.ssl.truststore.type
PKCS12
to indicate that the truststore is a PKCS#12 file.xpack.monitoring.exporters.$NAME.ssl.truststore.password
(Static)The password for the truststore.
You cannot use this setting and
ssl.truststore.secure_password
at the sametime.xpack.monitoring.exporters.$NAME.ssl.truststore.secure_password
Elasticsearch can be configured to use a PKCS#11 token that contains the private key,certificate and certificates that should be trusted.
PKCS#11 token require additional configuration on the JVM level and can be enabledvia the following settings:
xpack.monitoring.exporters.$NAME.keystore.type
- (Static)Set this to
PKCS11
to indicate that the PKCS#11 token should be used as a keystore. xpack.monitoring.exporters.$NAME.truststore.type
- (Static)The format of the truststore file. For the Java keystore format, use
jks
. ForPKCS#12 files, usePKCS12
. For a PKCS#11 token, usePKCS11
. The default isjks
.
When configuring the PKCS#11 token that your JVM is configured to use asa keystore or a truststore for Elasticsearch, the PIN for the token can beconfigured by setting the appropriate value to
ssl.truststore.password
or ssl.truststore.secure_password
in the context that you are configuring.Since there can only be one PKCS#11 token configured, only one keystore andtruststore will be usable for configuration in Elasticsearch. This in turn meansthat only one certificate can be used for TLS both in the transport and thehttp layer.« Machine learning settings in ElasticsearchNode »
Most Popular
Introducing EVGA Precision X1. With a brand new layout, completely new codebase, new features and more, the new EVGA Precision X1 software is faster, easier and better than ever. When paired with an NVIDIA Turing graphics card, the new EVGA Precision X1 will unleash its full potential with a built in overclock scanner, adjustable frequency curve and RGB LED control.
New OC Scanner
Test the next generation of EVGA's GPU stress testing utility with additional testing options and test modes.
Multi-GPU Fan Control
Adjust the fan speed, fan curve, or simply set a profile. Adjust the fans on each of your graphics cards using a more simplified interface.*
*Fan options may vary depending on the graphics card.
RGB LED
All-new RGB LED control for both graphics cards and NVLink Bridges!
- Brand new GUI that is faster and easier to use.
- Real-Time wattage monitoring (on supported EVGA graphics cards).
- Full support for GeForce RTX graphics cards (GTX support coming soon)
- RGB LED Control supporting graphics cards and/or NVLink Bridge.
- LED Sync that syncs with other EVGA RGB components.
- Dynamically set independent voltage/frequency points for ultimate control.
- New OC Scanner for finding the best stable overclock.
- On-Screen-Display (OSD) shows your system vitals at a glance.
- GPU Clock, Memory Clock and Voltage Control.
- Custom fan control and fan curve.
- Profiling system allowing up to 10 profiles with hotkey.
- In game screenshot function.
- + More!
- Supports GeForce RTX, Geforce GTX 16 Series, and GeForce GTX 10 Series Graphics Cards
- Windows 10 64-Bit
- Windows 8 64-Bit
Download Standalone for 30/20 Series ONLY
Download EVGA Precision X1 (Non-30 Series)
EVGA Precision X1 (30/20 Series) Version History
Version 1.1.0.11 for 30/20 Series ONLY
Release: 10/16/2020
- Adds compatibility for 20 Series functions
- Color Cycle & Color Stack allow user to select color number from 2 to 7
Download Links
Version 1.1.0.9 for 30 Series ONLY
Release: 10/8/2020
- Adds Precision UI Light Bar in General Setting
- Checks for GPU Fan Control
- Reduces CPU/GPU usage while PX1 is running
- Various bug fixes
Download Links
Version 1.1.0.2 for 30 Series ONLY
Release: 9/21/2020
- Update for XC3 firmware to reduce fan noise. (No impact to performance, or cooling.)
- Improved fan detection.
- DO NOT DOWNLOAD for previous series graphics cards
Download Links
Version 1.1.0 for 30 Series ONLY
Release: 9/17/2020
- Initial PX1 release for 30 Series ONLY
- DO NOT DOWNLOAD for previous series graphics cards
Download Links
EVGA Precision X1 Version History
Version 1.0.7
Version 1.0.6
Release: 5/21/2020
- Fix Save profile crash issue on certain cards
Download Links
Version 1.0.4.0
Release: 3/27/2020
- Adds support for additional RTX 2080 SUPER cards
Download Links
Version 1.0.3.0
Release: 2/26/2020
- Update firmware for RTX 2080 Ti FTW3 HYBRID.
- Fixed where NVLink LED could not be controlled if the VGA does not support LED function.
Download Links
Version 1.0.2.0
Release: 10/29/2019
- Improvements to the 'Apply Previous Settings on Load' option. Now when this option is selected without selecting 'Start with OS', Precision will auto load the last applied settings on system start.
Download Links
Version 1.0.1.0
Release: 10/17/2019
- Fix Framerate Limiter bug.
- LED Sync support on RTX 20 Series.
- Fix profile deleted on new install issue.
Download Links
Version 1.0.0.0
Release: 9/20/2019
- Improvements to 'Boost Lock' feature for compatibility. To set a locked clock, once you enable Boost Lock, you set the clock using offsets.
- Now shows 4 digits on system tray OSD.
- Various other fixes.
Download Links
Version 0.4.9.0
Release: 9/5/2019
- Improvements to 'Boost Lock' feature to ensure max overclock.
- Improvements to EVGA GeForce RTX 2080 Ti K|NGP|N OLED display
Download Links
Version 0.4.8.0
Release: 8/1/2019
- Adds new 'Boost Lock' feature, this feature will allow you to lock the graphics card frequency to the highest performance state. Please note that SLI is not currently supported in this feature.
Download Links
Version 0.4.4.0
Release: 7/18/2019
- Improves RTX 2080 Ti K|NGP|N Support
- Adds support for AMD Ryzen CPU temp monitoring
- Support for Z10 RGB LCD display
- Adds ability to disable splash screen on startup
Download Links
Version 0.3.19.0
Release: 6/14/2019
- Adds support for Frame Rate Limiter (Frame Rate Target)
- Various other fixes
Download Links
Version 0.3.17.0 BETA
Release: 5/13/2019
- Adds animated GIF support for K|NGP|N OLED
- Fixed bug where power target was not saving
- Improved fan control and support
- Fixed VGA2 voltage incorrect
- Various other fixes
Download Links
Version 0.3.16.0 BETA
Release: 4/24/2019
- Fix online update error.
- Improved GeForce GTX 1660 Ti support
- Updated GeForce RTX 2080 Ti K|NGP|N Firmware
- Improved Compatibility with EVGA Z10 Keyboard
- Various other fixes
Download Links
Version 0.3.15.0 BETA
Release: 4/16/2019 Firestream 1 23 – upnpdlna media server.
- Improved SLI compatibility with EVGA GeForce RTX 2080 Ti K|NGP|N
- Fixes bug with VF curve
Download Links
Version 0.3.14.0 BETA
Release: 4/11/2019
- Various fixes for EVGA GeForce RTX 2080 Ti K|NGP|N
- Precision performance enhancements
Download Links
Version 0.3.13.1 BETA
Release: 4/9/2019
- Adds full support for EVGA GeForce RTX 2080 Ti K|NGP|N and OLED control
Download Links
Version 0.3.12 BETA
Release: 2/27/2019
- Adds support for Windows 8.1 and Windows 7
- Improved LED support
- Fixed voltage showing incorrectly on OSD
- Improved support for GeForce GTX 10 Series
- Improved support for GeForce RTX 2060
- Fixed “Start with OS” working directory set incorrect
- Improved support for EVGA NVLink SLI Bridge RGB
Download Links
Version 0.3.11 BETA
Release: 12/26/2018
- Improved GeForce GTX 10 Series support
- Improved support for EVGA HYBRID cards
- Fix profile crash issue
- OC Scanner Improvements
- Adds support for Traditional / Simplified Chinese language
Download Links
Version 0.3.10 BETA
Release: 12/7/2018
- Adds BETA support for GeForce GTX 10 Series cards. Please note this release does not yet support iCX Monitoring or LED functionality for 10 series.
- Adds support for Intel CPU temperature monitor.
- Adds “Stealth” mode in fan curve preset to allow for lower fan noise.
- Improve OSD hook functionality.
Download Links
Version 0.3.9 BETA
Release: 11/28/2018
- Fix issue with MCU updater not properly updating some cards
Download Links
Version 0.3.7 BETA
Release: 11/15/2018
- Improvements to MCU updater
- Improvements to OSD
- Fix for profiles not saving on some system setups
Download Links
Version 0.3.6 BETA
Release: 11/13/2018
- UI improvements on MCU updater
- Fixed external fan RPM error
- Update temperature hysteresis range from 0°C to 15°C
- Fix issue with saved profiles being lost
- Various other fixes for fan control
Download Links
Version 0.3.5.1 BETA
Release: 11/2/2018
- Fix issue with MCU updater sometimes not properly updating
- Fix issue with Profiles not saving fan speeds
- Add support to see which version of MCU's are applied
Download Links
Version 0.3.4 BETA
Estatistica 4 2 1 – Advanced System Monitoring Devices
Release: 10/29/2018
- Fix issue with MCU updater sometimes not properly updating
- Fix issue with RGB color disappearing for some users
- Fix issue with RTX 20-Series FTW3 cards and fanspeed control
Download Links
Version 0.3.3 BETA
Release: 10/19/2018
- Fix issue with not detecting card on some occasions
- Supports real time power consumption for FTW3 cards
- Minor GUI Update
Download Links
Version 0.3.2 BETA
![Estatistica 4 2 1 – Advanced System Monitoring Estatistica 4 2 1 – Advanced System Monitoring](https://4.bp.blogspot.com/-BTaa2qTGwfE/WnU9q1gcQjI/AAAAAAAAABw/3m3_pQJHoQUwlPsEvB61fR8pTgLjF2XDwCLcBGAs/s1600/traffic.jpg)
Release: 10/12/2018
- Profile will now be highlighted when set (Use right mouse button to delete profile)
- OC Scan and Test results are saved to profiles
Download Links
Version 0.3.1 BETA
Release: 10/10/2018
- Add full support for iCX2
- Save/Load buttons are now used to save and load profiles.
- Fix issue with Hot Keys
Download Links
Version 0.2.9 BETA
Release: 10/2/2018
- Please note this version ONLY supports GeForce RTX graphics cards. GeForce GTX support coming soon.
- Adds support for Framerate and Frametime monitoring.
- Improved RGB LED support.
Download Links
Version 0.2.8 BETA
Release: 9/26/2018
- Please note this version ONLY supports GeForce RTX graphics cards. GeForce GTX support coming soon.
- Improved RGB LED control
- Fix issue with savings not applying after reboot
- Various other fixes
Download Links
Version 0.2.6 BETA
Release: 9/21/2018
Estatistica 4 2 1 – Advanced System Monitoring System
- Please note this version ONLY supports GeForce RTX graphics cards. GeForce GTX support coming soon.
Estatistica 1
Download Links
Version 0.2.5 BETA
Release: 9/20/2018
Estatistica 4 2 1 – Advanced System Monitoring Systems
- Initial release – Please note this version ONLY supports GeForce RTX graphics cards. GeForce GTX support coming soon.
Estatistica 2
Download Links