Admin Corner

TrendMiner does not support changing the (interpolation) type of a tag in the data source. This implies that for example when you change a tag from linear to stepped interpolation in your historian the tag will not load anymore in TrendHub and an error will be shown. You will also notice that the tag index can no longer be updated and goes to a STALE state.TrendMiner support can typically derive this from the logfiles, but if you already know this is the root cause of the problem then there are a few steps you can perform to resolve the issue.Refresh the tag cache manually in ConfigHub for the data source the tag is synced from (or wait up to 24h for the changes to be synced automatically) Restart the tm-compute service in ConfigHub or Edge Manager. Keep in mind that restarting tm-compute will entail downtime for the users (typically a few minutes). Re-index the tag. Edit and save all calculated tags and searches which depend on the changed tag (it is not required to make any chang

On June 20th, we hosted an admin webinar to prepare our admins for the upcoming 2024.R2.0 TrendMiner release. With this release, we are moving to a new Operating System (OS) given the end-of-support for Red Hat Enterprise Linux 7 (RHEL 7) and the derived CentOS 7.Two actions will be needed to upgrade your TrendMiner setup to version 2024.R2.0 once it is publicly released:The creation of a new TrendMiner server based on the new OS A migration of the application data to the new serverThis webinar details the prerequisites and steps to be taken to complete these actions.Additionally, it explains the migration options, including the new and highly recommended full system backup/restore functionality with secure storage on your own AWS S3 or Azure Blob Storage, which includes index migration. A detailed demo of this process is provided.Finally some important considerations and recommendations for planning the migration are outlined.Check out the recording below and refer to the "OS Migratio

In Edge Manager → Diagnostics the available disk space and the total disk space of TrendMiner can be checked. The disk space shown there shows the space on the /mnt/data volume (the volume on which the TrendMiner appliance is installed and on which TrendMiner stores its data).Next to the /mnt/data volume there is also the root volume, on which the OS and system services are running. Both the root volume and the /mnt/data volume can run out of disk space which in both cases will result in service interruption.The root volume total disk space and usage is not shown in Edge Manager since TrendMiner does not actively use this volume. Disk space issues should not occur on this volume if the system requirements are met.The /mnt/data volume is used by the TrendMiner application for storing data. This data mainly consists of: Info stored in the database, e.g. saved work from users. Index data Logically, the more usage of TrendMiner and the more tags are being indexed, the more disk space wil

Sometimes we get contacted by admins who are concerned about the memory usage of their TrendMiner installation. In Edge Manager -> Diagnostics you can check the amount of memory (RAM) available for the TrendMiner server and the percentage of memory which is used. In most cases, when you check these numbers you'll notice that the usage is over 90%, often even close to 100%.  Rest assured, this is not an issue. Linux (the OS on which TrendMiner runs) uses all available memory for optimal performance, instead of leaving it unused. If you are interested to read up on all the details we can advise to check this site: https://www.linuxatemyram.com (disclaimer: this is an external website, unaffiliated to TrendMiner and TrendMiner is not accountable for the site nor its content).  So how does TrendMiner use its available memory?Each microservice in TrendMiner gets assigned a fixed amount of memory based on the needs of the service. Our engineers make sure everything fits within the minimal

Red Hat Enterprise Linux 7 (RHEL 7) and the derived CentOS 7 are nearing their end of support. To ensure continued reliability and security for TrendMiner, we are transitioning TrendMiner to run on to the long-term supported Red Hat Enterprise Linux 9 (RHEL 9) and AlmaLinux OS 9 distributions. Infrastructure can already be prepared based on these new OS’s and the new system requirements. A new pre-packaged virtual appliance image based on AlmaLinux 9 has been made available for this purpose.Migration optionsThere are 2 options to migrate the existing server data to the new instance:Full migration including index data based on remote backup & restore (Azure Blob Storage or AWS S3 Bucket are the supported options) Work migration excluding index data based on local backup & restoreThe full migration is highly recommended as it will ensure the smoothest migration path with the least disturbances for end-users.Full details, with additional considerations, can be found in our documen

On April 9th, 2024 we hosted an exclusive webinar to discuss relevant topics for TrendMiner admins related to the 2024.R1.0 and upcoming releases (recording below).The following topics were covered:What’s new in 2024.R1.0?A quick overview of functional updates and newly available connectivity options. In 2024.R1.0, we added connectivity for Eschbach Shiftconnector, Wonderware 2020 and 2023 and Aspen APRM v14. A complete overview of supported connectivity options is available here.Admin roles comparedTrendMiner 2024.R1.0 introduces a new admin layer to better separate Infrastructure, System and Application administration tasks. Refer to this topic for a complete overview.About the upgradeThe 2024.R1.0 release introduces some major security improvements in ConfigHub and the way you can access ConfigHub. Refer to this documentation article to learn how to access ConfigHub after the upgrade by resetting the admin user password via Edge Manager. It is advised to only use the admin user for

Since TrendMiner version 2023.R3.0 configuration settings have been split up between Edge Manager and ConfigHub. This way, tasks specific to infrastructure admins and system admins are clearly separated and access permissions can be aligned with your organizational structure.Edge Manager is the TrendMiner interface for infrastructure admins. It mainly contains functionality to keep your TrendMiner installation healthy and up-to-date. Edge Manager is not available to SaaS customers as infrastructure administration is taken care of by the TrendMiner team. On virtual appliances, some additional menus for virtual appliance configuration will be available, which do not appear on self-managed single node or private cloud setups. The following tasks can be done from Edge Manager:Checking the health status of TrendMiner services Downloading appliance logs for troubleshooting purposes Gaining insights into memory usage, disk usage (including adding more disk space), CPU usage and time settings

The TrendMiner setup knows 3 different administrator roles:Infrastructure administrator (taken care of by TrendMiner for SaaS setups) System administrator Application administratorThe table below provides an overview of these roles, required skills and access permissions, example tasks and where to perform these tasks in the TrendMiner User Interface.Obviously, one person can take up multiple admin roles, but as different types of tasks are typically distributed over multiple people or teams, these roles permit to match TrendMiner administration to your organizational structure.  ​ ​ ​ ​ Infrastructure administrator ​ ​ System administrator ​ ​ Application administrator ​ ​TrendMiner UI Edge Manager ​ConfigHub​ TrendHub, ContextHub, TrendMiner API ​Description ​The infrastructure admin is responsible for installation and maintenance of the TrendMiner servers on infrastructure, network and security l