The error 'schemas: Unmatched child node' indicates a schema mismatch or incorrect node order in the Geneos gateway setup. Resolution involves verifying compatible schema versions, checking integration solution requirements, and contacting ITRS Support if needed.
A warning triangle on a Managed Entity indicates issues like disconnected NetProbe or licensing problems. Check gateway, netprobe, and license daemon logs, and use entity Properties and Gateway-licenseUsage plugin for details.
Netprobe disconnections from the gateway can occur due to delayed sampler or plugin processing, often caused by large files or complex configurations. Troubleshooting involves enabling SAMPLING debug options in Gateway Setup Editor to identify slow samplers and reviewing their configurations.
A Windows Netprobe's timezone can differ from its host's timezone if a TZ environment variable is set on the host. This issue can be resolved by removing or correctly setting the TZ environment variable using the tzset format.
The Windows Processes sampler in Geneos cannot detect a process if the Windows Management Instrumentation and WMI Performance Adapter services are not running. To resolve this, start these two Windows services and check the Netprobe log for related entries.
Actions in Geneos may not fire properly due to incorrect configuration, timing restrictions, unmet rule conditions, or action timeouts. Troubleshooting involves checking Gateway logs, validating action definitions, verifying active time settings, and ensuring scripts or commands run correctly.
Actions trigger user scripts based on rules, while active times control data item activity. Configurations affect when actions execute, including queueing behavior and rule or sampler active states.
Active/Passive monitoring ensures a service runs on exactly one server in a cluster. A gateway rule with count() and Path Alias triggers alerts if the service is down or running on both servers.
Active Console uses the system timezone by default but can be changed manually. You can override the timezone by adding the user.timezone JVM flag in the activeconsole.gci file.
The Infrastructure Monitoring Dashboard in Geneos provides a Linux-specific template showing CPU, hardware, network data, alerts, and snoozed items. It guides users through importing files, configuring a Linux probe, and setting up managed entities to create a functional monitoring dashboard.
Creating an alert on one cell based on another cell's value uses Path Alias 1. Define a rule with the target cell and reference the other cell using a path alias to trigger alerts.
Active Console does not support changing colors for color blindness directly. Users can add numeric severity values next to items and select Severity as Number mode as a workaround.
Duplicate dataviews appear in the View Selector of the Metrics dockable due to repeated sampler definitions. Removing the duplicate sampler from the Managed Entity or Type resolves the issue.
Active Console dataviews can be filtered using built-in sampler filters or the Filter Table feature, but temporary filters are lost on closing. Creating a persistent filtered metric dockable via Metrics Overview allows saving, sharing, and retaining filters after restarts.
Gateway connection issues occur due to process downtime, incorrect settings, access denial, or version mismatches. Solutions include verifying process status, network connectivity, user permissions, and ensuring compatible Gateway and license daemon versions.
Gateways disconnect when the Active Console starts due to overload from simultaneous connections. Solutions include refactoring List Views and adding the -queueConnections flag to connect Gateways sequentially.
Gateway Hooks allow customization of gateway configuration validation when saving through Gateway Setup Editor. Users can create a validate-setup script to perform additional checks on the gateway XML setup file during validation.
The Active Console allows listing attributes and their values for Managed Entities and Samplers in Details mode. Users can also export this attribute data to a CSV file for further analysis.
Filtering rows or columns in Active Console 2 data views is done through the Filter Table option accessed by right-clicking the dataview. You can apply, clear, and save filters to customize and persist the data view display across Netprobe restarts.
Setting up notifications with a custom sound alert in Geneos Active Console is done through the Notifier Manager. Users can select specific audio files for alerts and configure different sounds per user or user list within the workspace settings.
Docking a Manage entity group in the Active Console requires assigning it a specific attribute. After setting the attribute, you can use the Dockable Manager to drag and dock the Manage entity group content within the console.
Active Console allows users to hide columns in a dataview by right-clicking and unchecking column names. To make these changes persistent, users can save the settings as data view defaults or use the Visibility tab in newer versions.
Active Console creates multiple recovery files daily due to its auto-save and recovery feature, not because of crashes. To prevent unnecessary recovery files, disable or set the autosave period to zero in Tools > Settings > General > Persistence.
The EXCEPTION_ACCESS_VIOLATION error in Active Console occurs due to User Account Control conflicts or corrupted applications on Windows Vista and 7. Resolving this involves disabling UAC, scanning for malware, using Windows Troubleshooter, or adjusting Data Execution Prevention settings.
The Active Console output window grabs focus when it updates by default, interrupting other applications. You can disable this behavior using the toggle button in the top left of the output tab to prevent it from taking focus.
Active Console startup issues can result from incompatible DLLs, memory allocation, or Windows settings. Solutions include updating drivers, adjusting memory settings, disabling DEP, and running the program with administrator rights or compatibility mode.
Active Console cannot be opened on MacOS because Apple cannot check it for malicious software. The issue is resolved by removing the quarantine extended attribute from the executables using the xattr command.
Active Console may show the error "LoadLibrary failed with error 126" or crash due to a faulty graphics card on the host machine. The resolution involves having desktop administrators or IT assess and repair the graphics card hardware or drivers.
Passing arguments to Knowledge Base articles in Active Console only works with HTTP/HTTPS URLs, not with local file:/// paths. To pass parameters successfully, host the articles on a web server or use User Commands for local script execution.
Profiling the Active Console's performance involves using the JDK's built-in profiler, VisualVM, on Windows systems. This process helps monitor CPU and memory usage to assess console load and understand Java memory behavior.
Active Console List Views containing XPaths with Non-Identifying Predicates can cause performance issues and Gateway disconnections in large environments. The FAQ explains how to refactor these XPaths by removing predicates and using Filters to reduce load and improve responsiveness.
The "displayConversionInformation(Unknown Source)" error occurs when the last workspace is corrupted. Fix it by editing the configuration.xml file in the %appdata%\ActiveConsole directory to toggle a setting from true to false.
The managed entity name does not show by default in the Active Console status overview. To display it, configure the list view settings by enabling the Entity and Name property with local inheritance.
Active Console performance issues occur when the application becomes slow or unresponsive due to high load from multiple Gateways, Entities, Dataviews, and Active Dashboards. Reducing active Gateway connections and monitoring by exception can help manage load and improve responsiveness.
Active Console State Tree may not show attributes due to incorrect Managed Entity configuration or viewpath settings. Verify and update Managed Entity attributes and viewpath in Workspace settings to resolve the issue.
The Active Console icon pinned to the Windows taskbar does not change color to reflect severity and remains blue. To resolve this, unpin the icon from the taskbar, avoid using Windows shortcuts, or adjust the Taskbar Combine buttons setting.
Active Console error icons and visual indicators represent statuses such as cross bar, snoozed parent or child, inactive, and snoozed. Each icon meaning helps interpret monitored item states correctly.
The Active Console popup error indicates that a high percentage of Java virtual memory is used without garbage collection. To resolve this, avoid running in Debug mode and contact ITRS support with diagnostics if lock-ups or disconnects occur.
Severity changes on snoozed cells are not reported on the Event Ticker because snoozing prevents severity propagation and event reporting by default. To report these changes, configure the Gateway's tickerEventLogger severityChangeEventRestrictions snoozing setting to alwaysFire.
Connecting Express Reports to a MS SQL server named instance can fail due to dynamic port assignment. Configure the datasource to use a fixed port instead of the named instance to ensure stable connections.
The error "Failed to load native library, exiting" occurs when Active Console encounters an incompatible DLL version in the system path. Adding the flag -appendsyspath false to the ActiveConsole.gci file resolves this issue by preventing path conflicts.
Active Console shows an error when importing a dashboard created in a newer version than the console. Dashboards must be created and used within the same or compatible Active Console versions to avoid import issues.
Active Console cannot save workspace files due to permission issues, conflicting multiple sessions, or version incompatibility. The FAQ provides solutions including checking folder permissions, configuring unique working directories, and using compatible Active Console versions.
Active Console crashes occur due to outdated versions, overload, or workspace corruption. Updating the console, monitoring CPU usage, cleaning temporary files, and using a fresh workspace can help resolve these issues.
Active Console shows grey when Gateways, Managed Entities, or samplers are disabled or misconfigured. Troubleshoot by checking Gateway connections, Managed Entity status, sampler setup, and severity rules in Active Console settings.
Active Console may fail to load due to outdated versions, corrupted files, or Java conflicts. Solutions include updating Active Console, cleaning temporary files, checking installation paths, and verifying environment variable settings.
Active Dashboard allows creation of dashboard controls that function like cells in a metric view with minor differences. Custom Modifiers and downloadable tools enable adding these interactive cells to your workspace via import and drag-and-drop.
The Active Dashboard allows creating custom dashboard tools that display the contents of a table cell or headline. Custom tools can be imported via File > Import and then used directly from the dashboard palette.
Active Dashboard issues can cause un-selectable orphan lines with identical start and end points, affecting dashboard editing and scrolling. These bugs are fixed in GA5.1 and later, and upgrading resolves dashboard corruption problems.
Creating a dashboard control to show alert counts in a dataview summarizes alert levels effectively. Use computed cells and rules to count warnings, criticals, and display the highest alert level on the dashboard.
Active Dashboard does not have a built-in tool to directly plot a dataview table. You can create a custom Table Cell tool and use it to quickly add multiple dataview cells to the dashboard, with row names added manually.
Ungrouping a grouped item on the Active Dashboard requires the 'Atomic group' property to be turned off. If issues persist, the problem may involve orphaned lines that need XML modification to resolve.
Active Dashboard lets you display a list of items matching a modifier path as a comma separated list. This is done by using the 'label linked to data item name' modifier on a dashboard object.
Active Dashboard allows adding a URL to an external web page by configuring the Links property of a dashboard object. The URL is added through the path editor by selecting "WWW Page," entering the full URL, and applying the changes.
Using X-Path links in Geneos Active Dashboard objects allows matching specific data-items like warning or critical severities. Adding these links in the Object Attributes enables quick access to matching dataviews via a Search dockable.
Custom modifiers are copied and embedded when connected to a Geneos dashboard object. Imported dashboards in a new workspace retain existing modifier copies but require re-importing custom modifiers for new connections.
Active Dashboard items may appear grey due to issues with Gateway, NetProbe, License Daemon, or invalid x-paths. The solution involves verifying these components are running and ensuring x-paths return valid data and severities.
Alert Governance Identification Template in Geneos helps identify sources of high or false alert levels to reduce alert noise and improve monitoring effectiveness. It provides configuration steps and criteria to detect common false alert types and guide alert tuning.
Managing alert overload in Geneos involves minimizing false alerts and ensuring actionable notifications. This requires tuning alert frequency, severity, embedding expert knowledge, and ongoing maintenance to keep monitoring effective and manageable.
Enabling API plugin debug in Geneos netprobe logs helps identify errors or issues with the API plugin. This is done by creating an API module in the probe's debug configuration to generate detailed debug entries.
Applying different Active Times on a Rule monitoring cells across multiple Managed Entities requires using variables for Active Time. The variable must be added to each Managed Entity and referenced in the rule to apply distinct Active Times per entity.
Extractor functions in Geneos use XPath 1.0 to parse XML files efficiently. Useful functions include iterating child nodes, retrieving element text, and accessing attribute values.
Scripts for creating database logging tables are available for MySQL, Oracle, PostgreSQL, SQL Server, and Sybase in Geneos. These scripts are located in the Gateway binary folder under /resources/databases/ and include schema creation and update files.
Assigning permissions or roles by group in Geneos involves creating a role with defined permissions and linking it to a user group via the Role Properties name. This setup ensures all users in the group inherit the specified role permissions.
Allowing users to edit setup while preventing changes to authentication in Geneos is done by segregating roles and using section permissions. Enable section permissions on the Authentication section and create roles that exclude access to this section for specific users.
Configuring user permissions for modifying include files in Geneos involves setting roles with specific section and setup permissions. The process varies based on the location of the Rules section and includes enabling section permissions and assigning users to roles.
Authentication in Geneos allows disabling or restricting specific commands for selected users or roles. Use the Gateway Setup Editor's Permissions field to set command access levels such as None, View, or Execute for users and roles.
Bloomberg B-Pipe plugin shows N/A or corrupted values due to old NetProbe versions or permission issues. Upgrading NetProbe and ensuring correct user entitlements with Bloomberg Support resolves these errors.
Path Aliases in Geneos cannot refer to items on other Gateways and only access data within the same Gateway. To use data from another Gateway, you should use the Gateway Sharing feature instead.
A single Netprobe can monitor multiple MQ Managers by updating the Mq server option in the plugin's Advanced tab. Ensure Netprobe and MQ Client versions are current to avoid connection errors like RC2103 MQRC\ANOTHER\Q\MGR\CONNECTED.
Variables can be used in the Toolkit plug-in's Sampler script field if resolvable. The variable must follow the rules of Variable Scoping and Resolution to work correctly.
Encryption of the database cannot be configured within the Geneos Gateway itself. Database encryption and secure connectivity must be managed on the database side by a DBA, with careful handling of encryption keys.
Geneos does not have a built-in integration with Moogsoft. Alerts can be sent to Moogsoft using Events Integration via REST POST or through ITRS Analytics using a Webhook endpoint.
Dashboard URLs can be made dynamic by linking them to cell values in Geneos. Importing a custom modifier and populating a cell with URLs enables dashboard objects to launch different views or web pages.
Geneos can run in the cloud and on containers if the underlying operating system is supported. Installation follows standard procedures, and dynamic instances can be monitored using self-announcing probes configured in cloud images or containers.
Running two Active Consoles on the same machine is possible with specific configuration requirements. Each instance must use a unique workspace and separate directories for configurations and logs, set using the -wsp flag.
Hot standby Gateways in Geneos can synchronise specific external files but do not support wildcards for directories. To synchronise multiple files, use an external process like rsync scheduled via cron or Gateway Setup Editor.
.dat files created by Database Logging store updates not yet inserted due to gateway-database disconnection. These files should not be deleted and can be moved or processed manually once the connection is restored to avoid data loss.
Deploying Geneos configuration files via automated deployments using Microsoft ADO is not supported out of the box. ITRS offers consultancy services for custom solutions, and there are no immediate plans to migrate Geneos XML files to YAML format.
Cannot connect to the database when creating history charts due to version, access, or missing files. Verify database library, test network connection, and add MySQL JDBC jar if needed to resolve issues.
Geneos processes plugin displays each process only once, even if configured multiple times. To resolve missing processes, refine search strings to avoid overlapping process descriptors and ensure unique identification.
Changing the port for MS SQL Server had no effect in older Netprobe versions. Upgrading to Netprobe GA5.6 or later fixes this, or use a workaround by appending the port to the Server Name.
Restricting access to individual command arguments in Geneos requires removing permissions for the original command and creating new commands with limited arguments. Additional steps can remove popups by using silent mode and specifying argument values to control command behavior.
The connection between Geneos gateways and imported gateway views uses a proprietary stream-based protocol called EMF2 over standard TCP/IP (IPv4). By default, connections are unencrypted but can be secured by enabling TLS between components.
The CPU plugin on AIX collects data using OS commands and the native perfstat library. It calculates CPU usage, online status, and clockspeed based on perfstat\cpu values and command outputs.
CPU plugin on Linux reads CPU details from /proc/cpuinfo and /proc/stat files. Average CPU utilization and percentWaitTime are calculated using differences between CPU tick samples and specific formulas.
CPU plugin on Solaris collects CPU usage data using the kstat system API and command-line utility. Netprobe calculates CPU usage by comparing tick counts across CPU states between samples and displays percentages for the sample period.
Windows CPU plugin retrieves CPU metrics using Windows Performance Monitor counters and Registry API. It relies on deprecated Win-CPU plugin code and displays data from PerfMon counters on Windows systems.
Create a regular expression for remote or local ports by referencing a variable using the syntax $(VariableName). This method allows monitoring different ports on multiple managed entities with the same TCP-Link sampler.
Monitoring a Webserver using the JMX-Server plugin requires modifying the Webserver start script to enable JMX flags and configuring the JMX-Server Sampler in Geneos. This process allows the plugin to access MBean attributes like Memory for monitoring Java applications.
Dashboard design in Geneos focuses on creating flexible, user-built dashboards tailored to specific monitoring needs. The guidelines emphasize simplicity, audience understanding, and alerting by exception to ensure effective and actionable information display.
Setting links on dashboard objects allows invoking data items, dockables, tabs, or external URLs by double-click or right-click. Links can be hard coded in tool properties or dynamically set in custom tools using modifiers like Link URL to Data item.
Geneos does not provide a standard report for critical and warning alerts generated by gateways. You can write and run SQL queries on the event table in the database to retrieve and export this alert data.
The timestamp column in the ITRS Geneos database uses Unix Epoch time in UTC. Examples and commands for converting timestamps across various databases and Linux are provided.
Duplicated items with the same time stamp occur when the database schema allows it. Using the gateway’s Advanced tab to log netprobe sample times can prevent these duplicates.
Database logging may fail to work in Geneos, showing errors like a red cross on the database icon or database export issues. Troubleshoot by verifying the Gateway-DatabaseLogging plugin status and connection, and check the Gateway log for errors.
Sampling Status shows "Script timeout" when a toolkit script takes too long to run in Geneos. To resolve this, check the script for efficiency or adjust the script timeout option, keeping scripts under a few seconds if possible.
Disk sampler errors occur when it fails to retrieve stat values for specific NFS partitions, causing timeouts. Exclude the problematic partition path and provide diagnostic files if the issue persists for further investigation.
Disk plugin in Geneos monitors total and free inodes on partitions using auto-detect or manual configuration. For specific inode monitoring, use a custom script with the Toolkit sampler to integrate inode data.
The Disk plug-in error "Fail - Partition blocked" occurs when it cannot verify if a partition is valid, often with NFS or remote disks. Upgrading Netprobe to version GA3.5.0 resolves this by changing how the plug-in gathers partition data.
The Disk Plugin in Geneos can exclude DVD/CD-Rom drives from the Disk sampler by configuring partition exclusions for UDF file systems. This is done by setting AUTODETECT to TRUE and specifying excludePartitions and fileSystem parameters in the GSE configuration.
Disk plugin errors related to "cpuacct" and "net_prio" appear in the log file. The log file details help identify causes and guide troubleshooting steps for these errors.
The StateTracker plugin detects log file rolls by inode changes, not the Rewind setting. Avoid using vi or similar editors that rewrite files; instead, append lines with shell redirection to prevent false file roll detection.
The FKM plugin auto-detects log file rolls by identifying file replacements with new inode numbers. To avoid confusing results, only append lines using shell redirection and do not edit log files with vi or similar editors.
Geneos and ITRS Analytics require Unified Storage or block/file storage for core runtime operations, not Blob Storage. Blob Storage is only used for secondary tasks like log archiving or backups, and proper Kubernetes Persistent Volume configuration is essential.
Geneos supports only four severity levels: Undefined, Ok, Warning, and Critical. To manage alert volume, it recommends reviewing and reducing alerts rather than adding more severity levels.
The MQ-QINFO plugin does not read messages on the queue. It operates without requiring the +get permission as detailed in the MQ Queue Info documentation prerequisites.
The order of FKM keys affects Netprobe performance because keys are processed sequentially until a match is found. Sorting keys by likelihood and using ignore keys early can optimize scanning and reduce processing time.
The SQL-Toolkit plug-in in Geneos does not connect to the database on loading in manual sampling mode. Database connections are only initialized when sampling occurs, starting from version GA5.5 and above.
The var_ref value in Database Logging has a maximum limit of 2,147,483,647 before it becomes negative. The Gateway detects this error condition since version GA4.2 to prevent incorrect var_ref values in user tables.
Downloading ITRS packages using curl requires durable download links and login credentials. The process involves copying URLs from the ITRS Resources site and using query parameters to specify package details.
Duplicate or out of time email alerts occur due to overlapping Rule-Action and Alerting-Effect pairs or FKM sampler file monitoring behavior. Reviewing Gateway log entries and adjusting configurations or external email scripts helps identify and resolve these duplicate alert issues.
Email alerts in Geneos may not be received or can be delayed due to configuration settings or system issues. Adjusting action firing options and checking logs helps resolve or identify causes of email alert problems.
The error occurs when the first column of a dataview contains duplicate row names. You can resolve it by disabling duplicate row alerts in Gateway Setup Editor or removing duplicates from the first column.
Rule configuration errors occur due to syntax issues, invalid paths, or missing references. Solutions include correcting code syntax, verifying path aliases, and ensuring active times exist in the rule settings.
Error 0x800705B4 in the NetProbe log file is caused by the Hardware plugin's NTP monitoring on Windows servers. You can compare output using w32tm commands and hide timeSyncSource and timeSyncOffset rows in the Hardware sampler's Visibility tab.
The ERROR: ProcessContext::initialise Unable to get group info : Success(0) message appears in the NetProbe log when the running user lacks rights to query group info. This message indicates no actual error occurred and does not impact monitoring functionality.
The error java.lang.UnsupportedClassVersionError occurs when the netprobe uses an older Java version. To resolve it, use OpenJDK version 11 and update the netprobe startup script accordingly.
Extractor plugin in Geneos allows direct data extraction from JSON files by converting JSON into XML format. The process adds a top layer and changes structure, enabling data rotation and value extraction using XML paths.
Extractor debug menu options may be missing if Gateway Command Permissions are enabled and required commands lack Execute permission. Ensure commands like Show Source, HTML to XHTML, and JSON to XML have Execute permission to restore the debug option.
The error occurs when SetupManager cannot create a converter for an invalid text encoding during startup. The solution is to find and correct the typographical error in the XML configuration file causing the encoding issue.
Configuring inputTextFilters in FIX Analyser 2 allows ignoring specific FIX messages or texts. This helps filter out unwanted messages by setting precise text filters in the plugin configuration.
FIX Analyser 2 shows a PENDING status when it cannot find unique FIX message pairs. The plugin determines session status by searching the target FIX log for these message pairs.
The FIX Analyser 2 Netprobe restarts or crashes when the Order Cache Size setting increases virtual memory beyond limits. To prevent restarts, reduce the Order Cache Size, split samplers across Netprobes, or increase the Netprobe's maximum virtual memory setting.
FIX Analyser 2 may fail to open its database file due to insufficient file or directory permissions. Ensuring the Netprobe has read, write, and execute permissions on the .db file and its parent directory resolves this error.
FIX Analyser 2 requires correct regex, timestamp format, field separators, and noise filtering for accurate FIX log parsing. Proper configuration prevents parsing errors like incorrect message direction and misleading activity metrics.
Assigning a filter in FIX-Analyser 2 Message Detector view requires using a Filter List template. Ensure the filter is defined correctly to avoid errors when using the Jump to button.
FKM samplers may not appear in the dataview if special or non-ASCII characters are present in the sampler configuration. To resolve this, delete the sampler config, restart the NetProbe, and create a new sampler config without pasting from external sources.
FKM samplers cannot detect files due to permission issues or missing files and folders. Ensure the Netprobe user has correct read and access permissions and verify file paths and regex patterns.
FKM multiline settings capture the entire block of a multiline error in triggerDetails. Use regex start and end patterns and enable Parse trigger details to display relevant error lines.
The FKM plug-in can monitor keywords from the Windows Event Viewer and offers an Extended NT event log output option for detailed event text. Enabling this option outputs additional fields like EventID with prefixed field names for each event.
Clearing triggers that contain specific IDs or keys in Geneos FKM requires configuring clear keys with regex and capture groups. Modifying the setKey and clearKey values enables automatic clearing of triggers based on matched IDs or keys.
Monitoring multiple instances of files with the same extension can be done using the dynamic files option in the FKM sampler. This allows each file to be displayed uniquely on separate rows, with optional alias configuration.
FKM cannot monitor or parse the contents of compressed files like ZIP or GZ on Unix systems. For monitoring file arrival and timestamps, the FTM plugin is recommended instead of FKM.
The FKM plugin sends the log entry containing the error keyword with an alert through the triggerDetails cell. To send additional log entries, users must create a custom alert script that retrieves extra lines and triggers an action or effect.
The ignoreKey in the FKM plugin does not work if it is not placed at the top of the FKM table. Moving the ignore keys to the top in the Gateway Setup Editor ensures they are recognized correctly.
FKM unable to access monitored files due to missing files or insufficient Netprobe user permissions on files or directories. Ensure the file exists in the correct directory and Netprobe has read access to the files and parent directories.
Active Time settings in the FKM plugin should be set on the File or Table level. Setting Active Time on the Sampler level can cause false alerts due to paused sampling and delayed error detection.
FKM may not pick up strings correctly due to misconfigurations in file source paths, key table settings, permissions, or active time settings. The FAQ provides detailed causes and solutions to verify configurations, permissions, regular expressions, and keyword settings.
FKM samplers may show old or unexpected alerts due to reading files from the beginning or active time settings. Adjust active time on file entries or use default file active time to prevent repeated or out-of-time alerts.
The FKM plugin can limit the number of error messages shown per key using the maxConditionsPerKey property. Defining multiple specific keys and enabling maxConditionsPerKey ensures only the latest error message for each key appears in the dataview.
FKM reading a file from the beginning can cause repeated alerts on old entries. Adjust the Rewind option and Wildcard monitor all matches setting to prevent re-reading and duplicate alerts.
The FKM sampler cannot dynamically monitor files based on a changing date range over the last X days. Instead, placing all files in one directory and using the Wildcard monitor all matches function allows monitoring all files there.
The File Keyword Monitor (FKM) status shows as INACTIVE when the current time is outside the configured ActiveTime period. Ensure the sampler is set to monitor the log file during the specified active time to avoid the INACTIVE status.
The FTM plug-in can monitor files with paths that contain spaces on both Windows and Linux systems. Examples show how to specify file paths with spaces for Windows Netprobe and Linux Netprobe configurations.
Null arrivalTime and currentFileSize values occur when using the yesterday function with midnighttomidnight monitoring periods. Setting the monitoring period to Noontonoon resolves the issue by avoiding the midnight boundary condition.
FTM's date keyword filename functions allow automatic substitution of dates in file names. Use formatting codes to customize the date format, ensuring filenames update dynamically with the current date.
FTM's activePeriod defines a time window around the expected file arrival time to recognize and respond to file arrivals. When activePeriod is enabled, FTM monitors only within this window, showing null arrivalTime and currentFileSize outside it while continuously incrementing Delay.
The FTM Plug-In monitors files on weekdays by default if Monitored Days is not set. Updated guidance and documentation are available in the latest File Transfer Monitor (FTM) topics online.
The Gateway may crash after logging a "Too many open files" error due to system resource limits. Adjusting user, global, or SystemD service file limits resolves this by increasing allowed open files and processes.
Gateway database logging errors occur when the maxRequestQueueSize buffer is exceeded, preventing immediate logging to the database. Adjusting the maxRequestQueueSize value in the Database Logging Advanced settings can resolve this by increasing the buffer size.
The Gateway Docker integration in Geneos does not include its own database and requires an external database connection. To resolve connection errors, you must install necessary database client libraries or create a custom Docker image with required components.
Gateway Database Logging requires the full Oracle client and does not officially support or test the Oracle instantClient. It is recommended to install the full Oracle client for proper functionality.
Gateway database logging issues occur due to connectivity, authentication, performance, or configuration problems affecting live data writing. The gateway automatically creates, replays, and deletes dump files once issues resolve, with tunable parameters to optimize performance and manual replay options available.
Gateways disconnect from Active Console due to crashes, performance issues, network problems, XPath list views, or third-party tools like Zscalar. Solutions include addressing crashes, improving data quality, fixing network issues, refactoring list views, and disabling interfering third-party tools.
Hot standby gateways share one licence daemon without needing separate licences for backup gateways. Recommended setups ensure licence caching and continuity during server failures, maintaining monitoring with limited configuration changes.
Active times set on a sampler and a dataview within the sampler are handled using different server times if timezones are not set. The Sampler uses NetProbe Server time, while the Rules use Gateway Server time.
Calculating the last value of a cell involves understanding how the previous value function works. Using the rate function and sampling rate helps accurately determine value changes between samples.
The Gateway Load plugin helps find invalid targets by showing matching items in rules. Use the directoryStats category to identify rules with zero or unexpected matching items.
Geneos database housekeeping involves managing and archiving data to maintain performance and storage efficiency. This FAQ directs users to specific housekeeping strategies and documentation for SQL Server, Oracle, Sybase, Postgres, and MySQL databases.
Specifying the Minimum Active Console version requires entering a valid version expression in the Gateway's Connections tab. The system validates the format using a regular expression and shows errors if the entry is invalid.
Using multiple data sources in Gateway SQL involves combining dataviews with the Xpath table as the source. The process includes setting up Xpath, defining columns, querying the source table, and optionally filtering results in the SQL query.
Computing the difference in days between the current date and a given date uses Rule functions. The process involves converting dates to epoch, subtracting, dividing by 86400, and formatting the result as days.
Configuring Hot Standby Gateways with the same ports on different servers involves setting up primary and secondary gateways. The process includes installing the primary gateway, configuring hot standby settings, transferring setup files, and starting both gateway processes.
Missing email alerts in Geneos Gateway can result from snoozed data items, rule throttling, or mail server issues. Troubleshoot by checking active snoozes, reviewing rule throttling, and verifying mail server delivery beyond the Gateway.
Displaying plugin counts per probe or managed entity on a Geneos gateway involves using the Gateway-SQL plugin with specific SQL queries. The sampler must be run manually to populate data, as it does not sample automatically due to performance considerations.
Displaying the size of dataviews on a Geneos gateway involves using the Gateway-SQL plugin to count table cells in each dataview. The sampler must be run manually due to its 0 sampling interval and potential performance impact.
Filtering out null values in Gateway SQL requires using a specific syntax. The correct method is to use the "" syntax to exclude null entries from query results.
The error "FATAL: Gateway New <INSECURE/SECURE> listen port <port> is unavailable" occurs when another process is already using the specified port. To resolve this, identify and stop the conflicting process or configure the Gateway to use a different port.
The Trusted API Host field in Geneos Gateway can accept multiple hosts using three methods. You can specify hosts individually, use the wildcard \ character, or use the ? character to define multiple hosts.
Alerting on a date-stamped cell that has not updated within a specific time requires parsing and comparing date values. Use the parseDate and now() functions in a Rule to evaluate if the timestamp exceeds the defined time threshold.
Gateway can send email updates with screenshots of dataviews using a Perl script. Configure Webslinger, create an action and rule, then modify the script to capture and email dataview images.
The Gateway log message "Self-Announced Probe Limit reached" indicates that the maximum number of Self Announcing Netprobes allowed to connect has been reached. To resolve this, check and adjust the selfAnnouncingProbes > probeLimit setting as needed.
Modifying the Gateway setup XML file directly allows changes such as disabling authentication or automating updates without using the Gateway Setup Editor. To apply these changes without restarting, execute the kill -USR1 command to reload the configuration.
The Gateway computes time zone offsets inversely due to POSIX-style sign conventions. Using IANA time zone names like America/New_York or Europe/London avoids this reversed offset behavior.
Gateway snooze information can be viewed using the Gateway-snoozeData plugin or the database. Snooze data is logged if database logging is enabled and schema version is 1.6 or higher.
The error occurs when the startTime is not earlier than the endTime in active time settings. Disabling the endTime in the first schedulePeriod allows active time to span through midnight correctly.
The error "Legacy Netprobes cannot support second resolution in activeTime" occurs when ActiveTime settings use seconds instead of whole minutes. The issue can be resolved by removing seconds from ActiveTime schedules or enabling Gateway controlled Active Times for per-second accuracy.
Signal 15 in the Netprobe/Gateway log indicates the process was terminated by an external kill command using SIGTERM. This FAQ explains that Signal 15 requests a graceful shutdown and advises investigating which process issued the kill command.
The error message "ERROR: SQL Error in Stage: 'Extract xxx'" indicates issues with dataview sources or SQL syntax. Resolution involves checking source availability, license tokens, duplicate rownames, and escaping reserved keywords like Group.
The gateway log error occurs when the alert’s target data item is missing or renamed. This happens if the target cell is removed or renamed during alert evaluation.
The message "data exceeds connection max limit" means the gateway connection buffer is overloaded. Adjust the gateway configuration, increase the buffer size, or split the gateway to resolve this issue.
Sample on Startup controls whether the sampler performs an initial sample when the gateway sends configuration to Netprobe. Setting it to false prevents immediate sampling on startup, delaying data collection until specified sample times occur.
The warning message indicates the gateway rule target contains non-identifying predicates that cannot be evaluated at setup. The guidance advises revising the rule using operators and functions like regMatch to enable proper evaluation.
Geneos evaluates rules using the time zone of the Gateway server unless gateway Controlled Probe active times are enabled. When enabled, active times can specify time zones and use the Gateway host time zone by default unless otherwise defined.
Gateway files are created in the working directory where the Gateway binary is executed. These files include license information, cache data, user assignment data, and snoozed item details.
The error "ERROR: TRANSLATOR Unhandled message of type 5678" occurs when the Gateway receives a non-Geneos or non-http message. To resolve this, identify the IP address in the log and investigate the source, such as unsupported components or port scans.
Multi-line descriptions in Geneos dataviews require HTML tags to format text across lines. Using tags like <br> enables line breaks and proper display in the Description field.
The GSE error "Administrator role contains redundant permission entries" occurs when permissions are set for the "Administrators" role. The role inherently grants full Gateway access, so configuring additional permissions is unnecessary and causes this error.
Snoozing a specific DataItem in Geneos Gateway requires using the /SNOOZE:time command with correct time arguments. The command supports durations in minutes, hours, or days by specifying appropriate argument values.
Gateway crash occurs when the Geneos Gateway unexpectedly stops running and may generate a core dump. Troubleshooting involves checking logs, reviewing release notes for known issues, and verifying environmental factors like system resources.
Gateway handles data from NetProbe using in-process memory queues and C++ data structures. Active Console displays current data from Gateway memory and historical data from Analytics or database logging.
Gateway database logging can cause large data storage due to frequent dataview cell changes. Reducing logged items and running maintenance scripts to delete old data helps manage table size.
Gateway Hub API metrics cannot be fully listed; each metric has a unique path to verify. Use the Gateway Hub Web Console to find metric paths and query metrics with POST requests.
Gateway Hub recovers the apid service automatically after failures by applying unconsumed Kafka records during startup. If recovery fails, users can increase the ready\timeout parameter or manually delete and recreate the entity snapshots Kafka topic to restore service.
Recreating the Postgres database on a faulty Gateway HUB node involves stopping the Hub, copying data from a healthy node, and restarting services. The process includes tarballing database files, manual Postgres start and stop, and finally restarting the Hub normally.
Java heap space errors occur when the Gateway Hub exceeds its configured maximum memory allocation. Increasing the heap size in the gateway-hub configuration file helps resolve these out of memory issues.
Gateway Hub installation can fail due to zookeeper binding only to localhost addresses. Editing and updating the /etc/hosts file and cloud-init templates resolves this issue before reinstalling the Hub.
Timescale compression and data retention periods affect disk usage and data management in Gateway Hub. This explains how to check if compression and retention keep up and how to adjust settings for optimal performance.
Gateway stale or unresponsive issues occur when data is outdated or the Gateway stops responding. Monitoring maxDataAge, adjusting Rule Threads, splitting Gateways, and increasing resources can improve responsiveness.
Gateway performance issues caused by overloaded data queues can lead to slowness and old data. Conflation is an optional feature that discards outdated cell updates, allowing the gateway to process only the latest values.
Gateway Sharing can cause conflicts when shared probes have the same names as configured probes, preventing import. Adding a unique prefix in the Import Data Advanced settings resolves conflicts by distinguishing shared data names.
Dynamic targets with a value as a rule target cannot be integrated directly in Gateway SQL. A workaround involves configuring Gateway SQL to monitor data across multiple columns and trigger severity based on its presence or absence.
Gateway SQL allows administrators to build source data tables using XPath expressions for flexible data querying. This feature enables creating portable sampler configurations that tailor dataviews relative to the plugin location using row and column XPaths.
Gateway SQL can extract the last row from a DataView that continuously appends new rows. This is done by creating a new DataView using Gateway-SQL with SQL parameters to select the maximum rowID value.
Gateway unable to start can be caused by port conflicts, missing setup files, permission issues, or system library problems. Troubleshooting involves verifying port availability, file locations, user permissions, disk space, and correct Gateway package usage.
The Gateway-SQL plugin requires defining columns and their types in the table definition for the "order by" statement to work. Once columns and types are defined, sorting will occur automatically in queries.
GatewaySQL monitors a specific static value across dynamic rows to trigger alerts if missing. The example shows configuring rules to compare columns and set severity based on the presence of the value.
Snooze history in Geneos is recorded through the gateway's audit function and saved to a database, XML, or flat file. You can configure multiple output locations and formats, and also use a sampler with gateway-Snoozedata for snooze data.
The Geneos gateway fails to start due to issues with the cache setup file. To resolve this, shut down the gateway, move the cache folder to a different location, and then restart the gateway.
Geneos 7 license keys are mostly compatible with previous versions but may require updates. Upgrade notes and support details guide license management, compatibility, and component downloads for Geneos 7.
The Geneos Fundamentals course provides foundational training on Geneos overview, operation, configuration, and administration. New users should complete this course before taking the Foundation in Geneos Accreditation Exam, which is available under Legacy courses in the training portal.
Geneos-utils provides scripts to manage multiple Geneos components and versions on a single server. The tools help install, configure, start, stop, and control Geneos components using a specific directory structure and command scripts.
Hot Standby configuration error occurs when the Gateway host does not match the specified primary or secondary hotstandby hosts. Ensure the actual primary and secondary hostname or IP address are correctly used in the configuration.
Sessions from the SQL Toolkit to a database are managed by connection pooling or disconnection settings. Adjusting the "Close connection after query" option controls connection reuse and helps manage session limits like Oracle's SESSION\PER\USER.
The E4JMS Queues and Topics information in Geneos is derived using Tibco libraries, specifically the TopicInfo and QueueInfo classes. Geneos retrieves message and byte rates for inbound and outbound traffic by calling getInboundStatistics and getOutboundStatistics functions from these classes.
Using a generic FKM can result in seeing unavailable files across different servers. You can avoid this by configuring Sampler Includes per server type or using a hide rows variable in the Visibility tab.
Capturing the username when running a command in Geneos requires using a client-side xpath argument /geneos/client/runtimeParameters/@Username. This method works only for commands executed interactively in the Active Console, and background actions have no Username defined.
Capturing the username in a command requires adding the argument xpath: /geneos/client/runtimeParameters/@Username. This XPath retrieves the username without the domain name and can be passed as a parameter in commands like Putty.
Creating a rolling average for a metric in Geneos involves using the compute engine and history periods. The process includes adding a cell in the dataviews section and configuring history periods and rules to calculate the average.
Creating custom tools in the Active Console 2 Dashboard involves grouping shapes and saving them to the palette for reuse. Tools can include modifiers to dynamically update properties based on gateway data, enabling interactive and customizable dashboard elements.
Extracting a large number of gateway events from the database can cause performance issues in the Active Console event ticker. Running the import in debug mode reveals the SQL query used, allowing direct database queries for full event extraction.
Computed columns in Geneos data views are often hidden by default to avoid clutter in the Active Console. Using a column name starting with '/' via a variable allows these computed columns to be hidden automatically when the view is reloaded.
The repeating action in Geneos is cancelled after snoozing and unsnoozing a target data item unless the state changes. To continue the repeating action after unsnoozing, enable the Queue until restricted option in the Action advanced tab.
Merging data from two columns into a single column using the First column in Geneos involves configuring the sampler's advanced tab. The process requires entering the exact names of both columns under Dataviews > Name > First column to combine their data.
The error in Active Dashboard Manager indicates that Active Gauge is not licensed. Verify the configuration.xml file in the ActiveConsole directory to ensure the license status is set to accepted.
Showing the overall state of Managed Entities as a Dashboard Object uses Compute Engine and Rules. Create a headline, apply a rule for severity, then drag it to the Active Dashboard Manager.
Command Groups in Gateway authentication act as a permissions filter and do not automatically grant access to all commands within the group. Users can only execute commands explicitly listed in the Command Groups assigned to their Role or User permissions.
Adding another dataset to an existing dashboard gauge in Geneos involves using a drag and drop operation. Drag a data cell onto the gauge and select 'Gauge Dataset' from the Tools & Modifiers popup to add the dataset.
A flashing or flickering effect on the Geneos stateTracker can occur due to specific plugin settings. Adjusting the rewind setting and enabling "Skip mid-sample updates" in the stateTracker plugin resolves this visual issue.
Expensive XPaths in Geneos slow down the console and Gateway by causing excessive event processing during state changes. Use fully qualified, specific paths and avoid relative components, wildcards, and path variables to optimize XPath evaluation performance.
The Netprobe's default log file size is 10MB and can be changed to a value between 1MB and 4096MB. To resize it, adjust the Max log file size setting in GSE under Probe's folder > Your Probe's Name > Advanced.
The timezone of a Geneos webserver can be changed by setting the TZ environment variable in the webserver's start or run script. This allows charts and other time displays to reflect the desired timezone, such as Europe/London.
Comparing cells in different samplers in Geneos involves using path aliases to reference each cell's XPath. The process includes selecting a main sampler, obtaining XPaths for state cells from both samplers, and creating rule logic in the Rule Block.
Controlling the sampling time using an external file in Geneos is done with the File Trigger feature in the sampler's Advanced tab. This feature monitors file modification times to trigger sampling, allowing control over sampling frequency based on file updates.
Web Dashboards can be displayed directly in full-screen mode using a specific URL format. Adding '?fullscreen#WebDashboard:Name' to the URL automatically opens the dashboard in full screen without extra configuration.
Aggregated severities on a Gateway can be displayed using the Gateway-severityCount plugin. This plugin shows the number of severities per category and allows configuration of attributes for detailed views.
Enabling WebServer/WebDashboard debug requires editing the log4j.properties file in the config folder. After modifying the log4j.rootLogger parameter, save the file and restart the WebDashboard to apply changes.
Varname duplicates in Database Logging can cause conflicts in data processing within Geneos. The updated documentation provides guidance on resolving these duplicates to ensure proper database logging functionality.
Web Dashboard startup issues after version upgrades often occur due to outdated startup scripts and config files. Users should update their startup scripts, config directories, and OS startup locations following the Web Dashboard documentation to resolve these issues.
The total number of metrics for a given gateway can be obtained using the Active Console's diagnostics route. Creating a diagnostic file in a blank workspace provides this statistic in the summary.txt file.
Getting the total number of rows returned in a Geneos rule involves creating a headline cell. Configure a gateway rule using the count() function and Path Alias to display the row count.
Importing multiple dashboard files in Geneos requires using .ado files, which contain entire dockables. Export dockables via Dockable Manager and import .ado files through File > Import, ensuring no duplicate dockable names exist.
Input a comment in a Geneos rule by using the "//" symbol before the comment text. Comments cannot currently be inserted within an if statement, and this limitation is noted in an open PEBL request.
Limiting the number of displayed triggers in multiple trigger mode for FKM dataview is done using the maxConditionsPerKey parameter. Setting this parameter restricts the FKM dataview to show only the latest defined number of trigger rows per key.
Manually unlocking a locked gateway.setup.xml file involves renaming the gateway.setup.xml.lock file on the gateway host. This process allows modifications in the Active Console and requires restoring the lock file after saving changes.
Virtual memory on Windows can be monitored using perfmon counters or WMI classes. Use the netprobe tool to list accessible perfmon counters and check for virtual memory metrics.
Passing a parameter from one cell to a command in Geneos involves using XPath expressions to extract cell values. This can be done by creating a command with the appropriate XPath and running it from the desired cell.
Reformatting dataviews and grouping multiple rows can be done using the Gateway-SQL plugin. The plugin uses SQL syntax and functions like group\concat() to combine data by severity.
The Processes plugin in Geneos has a hard limit of 1000 rows, causing the warning about reaching the max row limit. To manage this, apply thorough filtering and relational grouping to reduce the number of displayed rows.
Rendering ghost images from Active Gauges in Web Dashboard occur due to the default tile size being too small. Increasing the tile width and height to 500x500 in the web-dashboard config.xml and restarting the web-server resolves the issue.
Restarting a netprobe in Geneos can be done using the RMS option to issue a restart command from the gateway interface. The process shows success in output and log files, and can be scheduled for multiple servers using scheduled commands.
Setting up Refinitiv Contex monitoring involves configuring the Stathandler and creating specific samplers in the Geneos Gateway Setup Editor. The process enables streaming of stats and logs for real-time monitoring using API and FKM plugins.
Using Node.js with the API plugin requires installing Node.js, npm, and the xmlrpc package on the server. The process involves setting up an API sampler and running a Node.js script to create a view on your netprobe.
Viewing previously accepted alerts in FKM involves using Gateway Database Logging to track FKM details and status. You can cross-reference the Geneos event table and audit table to review alert and command history within the gateway.
The rate function in Gateway Rules calculates the rate of change between the current value and the previous sample's value over time. It is used to monitor value changes, create computed columns, and trigger alerts if values remain unchanged.
The Disk Plugin calculates totalSpace of a Linux partition using the statfs() function. It sums the "Used" and "Available" columns, which may differ from the "1K-blocks" value due to reserved root blocks.
The process plugin computes percent CPU in Linux using values from the /proc/[pid]/stat file. It calculates CPU usage by comparing jiffies between samples and adjusts for logical CPUs, with debug options available for detailed data.
Environment variables are accessed in Python scripts using os.environ['VARIABLENAME']. The example shows how to retrieve variables within a Toolkit Sampler Dataview script.
TimeDifference in the Hardware plugin reports the time difference in seconds between the Gateway host and the monitored host. Newer versions support NTP and related fields like timeSyncOffset for more accurate time synchronization measurements.
Geneos is not affected by the Windows WMI/DCOM Server Security Feature Bypass (CVE-2021-26414) changes. Netprobes run WMI queries locally without using remote procedure calls, so no remote WMI connection security is needed.
The Active Console can connect to up to 1,024 Gateways from version GA4.9.0 onwards. Connecting many Gateways may cause performance issues due to large data volumes.
The number of Netprobes per Gateway depends on data volume and usage, not a fixed limit. Typically, about 100 Netprobes per Gateway is a general guideline based on performance considerations.
Accessing object properties in Active Console Dashboard is streamlined using the Object Inspector feature. The Object Inspector allows side-by-side viewing and multi-object selection to quickly review and update dashboard objects.
User configured commands in Geneos can be set to display a confirmation prompt before execution. This is done by using the userInput option with a boolean parameter to require confirmation in the Active Console.
Adding a time zone to a date before comparing it in a rule ensures accurate time-based evaluations. Use the rule's concat function to append the time zone abbreviation to the cell value before parsing or conversion.
Adding an additional row or column to a dataview in Geneos involves configuring the sampler's Advanced tab. You specify the sampler name in the dataviews section and select the desired rows or columns with their names under additions.
Adding custom commands on Authentication > Roles > Permissions allows specifying both Gateway and user-defined commands, including those with wildcard characters. You can enter commands manually or use the Add New button to restrict access effectively.
The netprobe name or port number can be included in filenames by defining a variable in Manage Entities or Environment Section. This variable, set to macro, netprobeName, or netprobePort, can then be used as part of the filename.
The error occurs when the Citrix password is not encrypted by the Netprobe user. Encrypt the Citrix password using the Netprobe user to resolve the issue.
The error "ConvertTo-SecureString: The system cannot find the path specified" occurs in Geneos Citrix Integration. Running the Netprobe as the user who encrypted the Citrix password resolves this issue.
Geneos can be configured to automatically restart a process if it goes down using a Processes sampler and defined rules. This involves detecting process failure, running a restart script, and escalating if the restart does not succeed.
The Local ports field in the TCP Links plug-in uses PCRE regex syntax and by default matches patterns with wildcards at the start and end. To capture an exact port like 5002, you must specify the pattern without wildcards.
The default initial download size on the FKM plug-in View File function controls how much data is retrieved initially. You can change this size by creating a custom command with a specified download size in the XML configuration.
The maximum database connections value in a self-announcing Netprobe cannot be set in configuration files. It must be defined as a variable in the Netprobe start script using export MAX\DATABASE\CONNECTIONS.
The version attribute of a Windows file can be checked using the WMI plug-in in Geneos. The WMI sampler configuration extracts file version data from the CIM\DataFile namespace based on specified conditions.
Checking the version of Gateway and Netprobe components in Geneos is done via command line options. Running specific commands in their installation directories displays version and build details, also logged in gateway.log and netprobe.log files.
Combining data from multiple Netprobes to create a new dataview can be done using the Gateway-SQL plug-in in Geneos. This plug-in uses an in-memory SQLite database to merge and transform dataviews with SQL queries, supporting joins and grouping.
Comparing cells on the same row requires creating a rule using path aliases with relative paths. This involves adding a column, defining path aliases, and setting a rule targeting those aliases for comparison.
Comparing values between two dataview columns can be done using the Gateway-SQL plugin. Queries can find matching, similar, or non-matching values, but may impact performance and require manual sampling.
Comparing a timestamp with the current time in Geneos gateway rules can be done using the parseDate() and now() functions. You set rules by parsing the date string to epoch format and comparing it to now(), adjusting formats as needed.
Comparing two dates and displaying their difference on the Active Console involves using the parseDate() function in gateway rules. This process converts dates to epoch time, calculates the difference in seconds, and updates a target cell with the result.
Comparing Unicode characters in Geneos gateway rules can be challenging due to Active Console's limited Unicode display support. Using the regMatch() function with hex-encoded Unicode patterns provides a workaround for matching characters like Chinese, Japanese, and Korean.
Configuring a sampler to use variable timezones allows flexible time settings across entities. Use active time variables and assign them in sampler and managed entity settings to apply different timezones.
Clear Key in the FKM plugin can be configured to match multiple keywords using regular expressions. This allows automatic clearing of detected triggers by referencing captured groups and patterns in log entries.
Configuring escalation and repetition via an alerting hierarchy manages alert notifications without modifying rules. This setup uses alerting levels to escalate and repeat alerts based on timing and severity conditions.
Configuring Hot Standby Gateways with different ports requires disabling the Listen Port setting. The process involves modifying start scripts with the -port flag and transferring setup files between servers.
Configuring Self Announcing NetProbe with Collection Agent involves setting up compatible versions and defining mappings. The process includes using example configuration files, ensuring plugins are defined, and running test programs to expose data.
Configuring systemd scripts enables automatic startup of Geneos Gateway, Netprobe, and Licence Daemon services. Examples and steps for creating, placing, and enabling .service files with systemctl are provided for Linux systems.
The Gateway Setup Editor requires manual loading of include files by default in Geneos. Adding specific lines to the ActiveConsole.gci file automates loading all include files when the gateway setup is opened.
The Self-Announcing Netprobe feature allows Netprobes to start without pre-configuration on the Gateway using a Netprobe Setup File. This setup file specifies Probe and Managed Entity names, enabling immediate default monitoring and supporting advanced features across Geneos versions.
Configuring the trapmon sampler for SNMP version 3 involves setting up net-snmp on a RHEL system. This includes creating a user with authentication, adding the engineID, and specifying the config file in the Geneos sampler settings.
Disk sampler freeSpace values are displayed in MB by default and can be converted to GB. You can add a new column in the Disk sampler and use a gateway rule with the format() function for conversion.
Creating a diagnostics file for the Active Console involves using the Help menu options specific to your Active Console version. This generates a zip file that can be attached to a help desk ticket for support teams to diagnose issues.
Creating a List View and Notification filter shows data items assigned to your username. Use specific XPath expressions and import example files in Active Console to configure these views and filters.
Creating a right-click command in Active Console can include a drop-down box for data selection using xPathOptions. This feature evaluates specified XPaths to present multiple choice selections based on entity properties or cell values.
Creating an exportable report with values involves configuring a list view using XPath in Active Console. The list view can then be exported as a CSV file containing the matched data cells.
Defining a JMX attribute with a dot in its name requires special syntax in Geneos. Use quotation marks around the attribute name, like $1."Runtime.freeMemory", to ensure correct definition.
Application log filenames with dates can be defined using date codes like yesterday, today, or tomorrow. A pop-up window allows you to select options and view the file content.
Detecting if a named row is missing from a dataview involves using the sampler's expectRows setting. This setting helps monitor row presence by marking absent rows in the Availability column and triggering alerts accordingly.
Determining if a cell value is a number or a string involves using inList and regMatch functions. These functions help check numerical ranges or patterns and set severity based on matching rules in Geneos.
Additional Gateway Info Managed Entity appears by default after upgrading to GA5.4.0 or later. To disable it, tick the Self Monitoring Setup disable checkbox in the Operating Environment Basic tab.
The manual snooze function in Geneos can be disabled by creating roles that exclude manual snooze commands while allowing other access. This involves assigning a custom role without manual snooze to users and managing role properties accordingly.
Disabling the dataview's Sample Now button in Geneos is done by enabling Gateway Authentication and assigning a role that restricts the /PLUGIN:sampleNow command. This configuration causes the Sample Now button to be greyed out for users with that role.
Disabling a user from accessing the Gateway Setup Editor (GSE) involves modifying their permissions and role properties. Remove all permissions and role properties, then enable only "Allow login" and "Allow system auth" for that user.
Displaying date and time on a Geneos dashboard requires adding a headline cell with a rule using Compute Engine. This cell can then be dragged to the Active Dashboard to show formatted date and time with time zone information.
Displaying the FKM keys in use for each log file involves searching for all FKM logs in the Active Console. The Show Tables command generates a tab listing the FKM keys for each file, with options to filter long lists.
Displaying samplers with their sampling intervals from a gateway requires using the Gateway-SQL plug-in. The sampler must be run manually to retrieve data since it does not sample automatically and has a zero sampling interval.
Enabling the Web-Mon debug setting in Geneos involves adding CURL as a module on the Probe's Debug tab in the Gateway Setup Editor. After sampling, remove the debug setting and attach the netprobe log to the support ticket.
Enforcing users to enter a comment when using the snooze function in Geneos varies by version. Versions GA4.10 and above offer a Require Snooze Comments option, while older versions use the Gateway Snooze Data plugin and rules.
Two different self-announcing Netprobes cannot be forced to connect to the same Gateway because the Gateway selection is determined by load-based scoring. The Gateway score system ensures load balancing by directing each Netprobe to the least loaded Gateway automatically.
Estimating database size depends on metrics, storage interval, and archiving strategy. Use guidelines and formulas to calculate size and minimize storage by limiting data and adjusting logging intervals.
Extracting a Managed Entity's attribute involves using XPath to retrieve specific attribute values. The extracted attribute value can then be used as an argument in a command within Geneos.
Extracting JSON into Geneos can be done using Extractor or Rest-Extractor plugins. Extractor uses xpath with JSON converted to XML, while Rest-Extractor uses simpler JQ queries for JSON extraction.
Extracting the samplingStatus headline cell of all samplers running in a Gateway requires configuring a Gateway SQL sampler. Use GW\SQL\samplingStatus.xml or GW\SQL\samplingStatus\NOT\OK.xml and adjust sampleInterval to reduce Gateway utilization.
Fine tuning FKM plugin performance involves optimizing log file monitoring and regex configurations. Adjusting sampler settings, regex order, and using PCRE can improve resource consumption and reduce delays.
The "Could not load remote setup for gateway" error occurs when opening the Gateway Setup editor in Geneos. To fix it, stop the gateway process, delete the gateway and editor cache folders, then restart the gateway and console.
The warning appears when gateway rules use wildcarded XPath in secondary variables. It advises revising paths to avoid wildcards or use first() with wpath for correct data selection.
Active Dashboard links open in another tab after upgrading Active Console due to dockable name changes. Creating a new dockable named "activedashboard" restores link functionality for imported dashboards.
Exit code 126 in Geneos actions indicates missing execute permissions for the script by the gateway or netprobe user. Exit code 2 means the script header is incorrect or missing, requiring a proper shell interpreter line.
The ORB_SYNCH_FAILED_EVENT error occurs when the Licence Auditor tool's Client connection requirements specify a newer version than the tool itself. To fix this, set the minimum Active Console version to match the Licence Auditor tool version being used.
SQL-Toolkit in Geneos may display date/time without seconds if the SQL query lacks proper formatting codes. To fix this, amend the query to include date/time format specifiers like '%Y-%m-%d %H:%i:%S' for correct display.
The error "FAIL: Unable to initialise MQ libraries." occurs when Netprobe cannot find MQ Client library files. The solution involves verifying the presence of required MQ libraries and checking Netprobe logs for related errors.
The Toolkit plugin error occurs when scripts write output to stderr instead of stdout. Troubleshooting involves checking logs, running scripts manually, and silencing progress bars in commands like curl.
Forcing a snooze for a set period ensures specific users can only snooze items for a defined time. Creating a custom command and role restricts snooze options to enforce this default period.
Snoozed cells in Geneos do not trigger actions by default when their severity changes. To force alerts, set the Snoozing option to Always fire in the action restrictions or use the Ticker Event logger for event notifications.
Generating a list of samplers on a Gateway involves using the Reporting option in the Active Console. You create and schedule a report with search criteria set to Sampler and specify a filename for the results.
Generating an alert when an SQL-Toolkit query returns zero rows requires handling initial data states correctly. Using the 'Expect row' option in sampler configuration allows writing rules that detect zero rows only after query completion.
Generating and extracting the Gateway diagnostics file captures all setup files used by a Gateway for issue investigation. The diagnostics file is created via the Active Console and located on the Gateway Server for upload to support.
The open files limit on Solaris probes and gateways can be raised using the extended FILE facility. This involves enabling the facility and increasing the file descriptor limit in the shell before launching the application.
The OS, Gateway, and Netprobe versions can be found without accessing the server directly. Use the Active Console's search function to locate version details for the connected Gateway and Netprobe.
Working set memory of a Windows process can be obtained directly from the OS using Performance Monitor. This value can then be compared against the working set column in the Geneos processes plugin for monitoring accuracy.
SQL-Toolkit plugin does not support certain data types like BLOB, CLOB, and Long Binary. Use SQL functions such as CAST and SUBSTR to convert these data types into readable formats.
Database Logging sources with issues display a red error symbol in the Active Console, indicating logging failures. Use the Reporting tool to create and schedule reports that identify and monitor these database logging failures.
Including the current date in email subject lines uses the printDate function in the Rule block. Define %(CURRENT\DATE) in the subject and format the date within the printDate function.
Integrating gateway setup XML files with source control systems uses the Gateway Hooks feature to trigger custom scripts during gateway events. Scripts like post-setup-apply can automate pushing changes to Git by running after setup application.
The correlated version of SSO-Agent and Geneos is not explicitly specified in release notes or compatibility matrices. You can find SSO-Agent release details in the Geneos release notes or raise a ticket to check compatibility.
The Gateway uses the local time zone if no time zone is set in Operating Environment or TZ variable. The Gateway log shows the time zone used, and removing the setting ensures local time zone usage.
The Control-M plugin in Geneos allows users to limit job output by applying filters and setting a maximum number of job records retrieved. This helps focus monitoring on critical jobs by customizing views and reducing displayed job data for alerting.
The JMX sampler in Geneos can limit the number of digits rendered using custom masks. This involves creating and deploying a custom mask class, enabling Masks in the sampler, and applying the mask with the desired format string.
Listing all users on a Windows host can be done using a custom PowerShell script with the Toolkit plugin. The provided sampler lists users and session status, enabling rules to alert based on user activity or permissions.
Mimicking the display name to match Active Console state tree hierarchy with Webslinger tree hierarchy addresses inconsistent Gateway Entity display. Adding an extra attribute to each Gateway Entity enables unique and logical display in the Webslinger state tree.
Monitoring files with date codes in filenames requires using the FKM plugin's date format patterns. The FKM plugin detects files daily by matching filenames with embedded date codes like y-m-d.
The Extractor plugin monitors local HTML or XML files on Netprobe using the Source File Name option. It parses file content into headline and table cells for display on the Active Console.
Monitoring a log file for a specific number of errors within a timeframe uses the FKM sampler. This involves configuring rules and actions to trigger alerts or reset monitoring based on error occurrences and timing.
Monitoring a web page with basic authentication in the Web-Mon plug-in requires selecting only the Basic method. The Authentication settings must have Basic checked and NTLM and GSS-Negotiate unchecked for proper operation.
Monitoring the existence of folders can be done using the Windows WMI plugin by querying the Win32\Directory class. The plugin supports filtering folder names with the Restriction field using the LIKE keyword and wildcards, with configuration examples provided.
Monitoring log files for specific patterns helps track application events and statuses effectively. Using Geneos FKM and StateTracker plugins, you can configure pattern detection, timeouts, and alerts tailored to various log monitoring scenarios.
Monitoring the absence of a string in a log for a set time is not possible with the FKM plugin. Instead, use the State Tracker plugin to report an error state if the string is missing for the specified duration.
Monitoring log files for Unicode characters in the FKM plugin requires special configuration. Use PCRE regex and hex codes to match Unicode patterns, as Active Console cannot fully display these characters.
Monitoring IBM mainframes like AS/400 with Geneos involves using remote Netprobe connections since no Netprobe runs directly on these systems. Geneos supports IBM i monitoring via the JTOpen library and other mainframes through customizable generic plugins and available APIs.
Monitoring multiple IBM DB2 database instances requires specifying the DB2INSTANCE environment variable for each instance. To do this, start one Netprobe process per instance with the DB2INSTANCE variable set before startup, noting this does not apply to Windows Netprobes.
Monitoring new rows arriving in the sql-toolkit plugin involves tracking the number of rows returned. Enabling the Show headlines option lets you set a rule on the rows returned cell and use rate of change to detect new rows.
Monitoring the number of files in a folder can be done using the FKM or Toolkit plugin. Enabling wildcardMonitorAllMatches in FKM includes all files and directories on the specified path.
Monitoring processes running under a specific user account in Geneos is done through the Processes plugin by applying a user filter. The filter is set in the Advanced tab under Process Filter options, where you select UserNames or UserIDs.
Monitoring SNMP devices with the MIB Monitor plugin involves using SNMP GET requests and verifying network connection and permissions. Configuration requires testing SNMP security with snmpwalk and setting options under the Advanced tab in the MIB-Mon plugin.
Monitoring JVM heap size involves using the JMX Plugin to retrieve MBean attribute values. Configuration requires setting the serviceUrlRmi variable with the correct JMX service URL details.
Monitoring the latest file version with a date in its name uses wildcards or date functions. The FKM plugin settings control how the newest file is selected by changed or modified timestamps.
Monitoring the latest version of dynamically named files in a dated directory requires using the Dynamic Files option in FKM. The setup involves configuring the path, regex, and date functions to capture the newest files automatically.
Monitoring batch job duration uses State Tracker and Compute Engine features in Geneos. State Tracker tracks job states while Compute Engine calculates start time, end time, and duration using custom rules.
Monitoring the ulimit command output on Linux shell requires reformatting its data for the Toolkit plugin. The solution uses sed to remove commas and insert delimiters, enabling the Toolkit plugin to parse and display ulimit information correctly.
Monitoring server certificate validity for websites can be done using the Toolkit plugin. The Toolkit supports Linux with openssl and Windows with PowerShell scripts for easy configuration.
The Web-Mon plugin monitors plain text web page content and searches for keywords or phrases. The Extractor plugin displays this content on the Active Console by parsing and transferring data from Web-Mon.
Windows Scheduled Tasks data can be exported using GUI, schtasks.exe, or PowerShell cmdlets for monitoring. The Geneos Toolkit plug-in captures command output, with example VB Script and configuration to filter or display all scheduled tasks.
Opening PuTTY sessions directly from the Active Console requires configuring a command targeting the desired cell. The process involves setting the PuTTY executable path and running the command via right-click on the target cell.
Parsing FKM's status and triggerDetails columns requires enabling specific plugin settings and configuring Tags at the FKM key level. This approach allows customization of displayed text in metrics views by using the Parse trigger details option and Tags settings.
Parsing JSON output from a website using the REST Extractor plugin involves configuring the URL and entering jq queries. The plugin supports direct JSON parsing with jq syntax and allows column reordering for customized data views.
Parsing JSON output from websites using Webmon and Extractor plugins requires Netprobe GA4.4 or later. This process involves configuring Webmon for data transfer and Extractor for JSON tag extraction and display.
Path Alias values can be passed to a shell script by storing them in userdata as environment variables. This process involves creating a rule, an action, and a shell script to utilize the Path Alias values effectively.
Querying SQL Server Agent Jobs retrieves job setup, execution, and schedule information. The SQL-Toolkit plug-in uses updated queries and a sampler XML file for configuration.
Raising a new alert when an issue persists involves configuring escalation or repeat intervals in an Action. These settings trigger alerts after a set time if the problem remains unresolved.
Reading a file in Windows using the Toolkit plug-in requires invoking cmd.exe first. The "type" command must be run through cmd.exe with the syntax: cmd.exe /c type.
Receiving email updates with dataview screenshots uses Gateway REST service and scripts. Configuration involves setting Gateway version GA5.14+, REST commands, and email scripts on a Linux server.
Refactoring XPaths with wildcard characters in Active Console dashboards requires using the Refactor tool's Advanced Mode. This mode allows bulk renaming of Managed Entities and ensures correct syntax handling for efficient dashboard reconfiguration.
Reformatting an existing datacell in Geneos involves changing the display unit using the compute engine functionality. This is done by adding custom columns in the sampler and creating rules to compute and format the values accordingly.
Refreshing suspended Toolkit checks in bulk involves using the sampleNow command to restart Toolkit samplers on the Gateway. This can be automated by configuring a scheduled command that runs sampleNow on all Toolkit samplers during specified periods.
The repeat interval option controls how often an action repeats if the triggered rule condition remains valid. Setting the repeat interval to 1800 seconds repeats the action every 30 minutes in Geneos.
The error occurs because the Netprobe version is lower than 5.2.x and does not support dynamic managed entities. Upgrading Netprobe to GA5.2.0 or higher resolves the issue and enables support for dynamic entities.
The error occurs when the filename for the downloaded file is not relative to the Netprobe working directory. The filename must use a relative path starting with ./ or just the filename itself to resolve the issue.
The error occurs when a script tries to access parent directories without proper permissions or missing files. Ensure the Netprobe user has access to execute commands and scripts to resolve this issue.
The error occurs when the MDM nyxt adapter lacks a valid middleware bridge. Correct the mama.properties file by setting geneos.middlewarelist to include the required middleware libraries like lbm.
Restricting user access to files monitored by the FTM plugin involves configuring Authentication roles in the gateway. Assign specific permissions for 'View file' and 'Accept File Delay' commands and verify the 'combineMode' setting to control permission inheritance.
Restricting which data a user can view from a Geneos gateway involves controlling access beyond basic authentication. The Gateway Sharing feature allows configuring Exported and Imported Data options to limit visible dataviews for specific users or groups.
Right-clicking on a cell with a URL in Geneos opens the page in a web browser using a client-side command. The command uses the browser's full path or explorer to launch the default browser with the cell's URL value.
Rounding off decimal numbers in the JMX plugin can be done using arithmetic expressions instead of Custom Format Masks. This method requires Netprobe GA6.7.0 or above and involves subtracting remainders or adding 0.5 before rounding down.
Running a PowerShell script from the Active Console requires configuring Gateway Commands with runLocation set to Netprobe. The user must have permission if Gateway Authentication is enabled, and the target data items must belong to a Windows Netprobe.
Running the RMC Replayer involves downloading, configuring, and executing the Geneos RMC Recorder with hostname modifications. The process includes setting the hostname in the RMC-interface plugin and running the Replayer before starting the probe.
Scheduling password protected commands in Gateway requires providing the plain text password as an argument in the scheduled command. The Gateway encodes this password using the netprobe's salt before sending it, ensuring proper authentication and execution.
Sending an alert for 3 trigger keys detected within 1 minute in a FKM sampler requires configuring a rule with the rate function. The setup involves adjusting sampleInterval, triggerMode, and triggerCount settings in the FKM sampler and rule files.
Sending email notifications using Linux sendmail in Geneos involves configuring Gateway userdata variables as an alternative to the Gateway's libemail feature. This guide provides a quick setup method but notes that Linux sendmail is not officially supported by ITRS Geneos.
Setting an alias for a hostname in Geneos probe setup requires proper hostname resolution. You must define the alias-to-hostname mapping in the gateway machine's /etc/hosts file or create a DNS CNAME record for the alias.
Setting a multiline Ignore Key in FKM involves using Start and End patterns with Ignore Key. This method filters specific multiline error sequences using regex to exclude them from the dataview.
Setting up a command to run a bash script with variables requires using shell -c and variable definitions. The command must concatenate arguments into a single string to pass to the script correctly.
Gateway Sharing in Geneos allows exporting and importing datasets between Gateways running version GA4.x or higher. The setup involves creating Export datasets on the source Gateway and Connection entries on the target Gateway with matching dataset names and credentials.
Notifications in the Active Console are set up using the Notifier menu, allowing on-screen pop-up alerts for critical and warning cells. You can enable, disable, or customize these notifications and filters through the Notifier settings.
Setting up the Toolkit plug-in to display PowerShell script output requires calling powershell.exe explicitly. The output must be formatted as CSV for parsing and displayed in a dataview within the Active Console.
Setting up a calendar with holiday active times prevents alerts from triggering during holidays. You create a holiday schedule using the Override checkbox and reuse it in active times for rules, actions, and plugins.
Gateway authentication for a generic user requires specifying at least one authentication method. Enable either password or system authentication in the Gateway Setup Editor to resolve validation error messages.
The maximum number of events shown in Event Tickers can be changed in Gateway Setup Editor. You can also enable event caching to keep events after a gateway restart.
This FAQ explains how to show the environment variables of a running Netprobe process in Linux. It provides instructions to find the Netprobe PID and use a command or add a Toolkit sampler to display environment variables as a dataview.
Snoozing a Gateway in Geneos cancels all actions, preventing them from firing until there is a change in state or severity. To queue actions during snooze, enable the Queue until unrestricted option in the Action Advanced Tab.
Common HTTP error codes in the Geneos REST API plugin include 400, 404, 405, and 505. Solutions involve verifying JSON format, correct ports, HTTP methods, and encoding spaces in URLs.
Connectivity issues in the Control-M plugin occur due to port, SSL, or user authorization problems. Solutions include verifying port settings, SSL certificates, and user permissions with Control-M administrators.
Database client installation issues occur when the SQL-Toolkit plugin cannot locate required clients on Netprobe. Resolution involves verifying client versions, environment variables, permissions, and matching 32-bit or 64-bit architectures with Netprobe.
The ORA-00911 error in the SQL-Toolkit plugin occurs due to an invalid character, typically a semi-colon, in the SQL statement. The error is resolved by removing the semi-colon since it should not be used when calling statements directly.
Error locating libmysqlclient_r.so occurs when SQL-Toolkit plugin cannot find MySQL client libraries. Installing the correct database client or creating a symbolic link resolves the issue for Netprobe versions GA5.0.0 and above.
Login issues in the SQL-Toolkit plugin often stem from incorrect credentials, locked accounts, or compatibility problems. Users should verify database credentials, check Netprobe and client compatibility, and ensure the Netprobe version supports password encryption.
Mapping Errors in Collection Agent Plugin occur when no mapper matches certain metrics, causing invalid metrics to appear in the Dynamic Entities dataview. To resolve this, use Show Dynamic Mappings to compare and update your configuration mappings accordingly.
Oracle connection issues in the SQL-Toolkit plugin often stem from client installation or configuration errors. Solutions include verifying Oracle Client setup, environment variables, and database parameters to resolve common Oracle error messages.
The error occurs when the Gateway or Netprobe cannot locate Sybase's lib3p64 folder required for database connection. To resolve it, define the absolute path of the lib3p64 folder in the LD_LIBRARY_PATH environment variable in the start script.
The error "Unable to complete login process due to delay in opening server connection" occurs in SQL-Toolkit plugin. Solutions include checking connectivity, enabling MultiSubnetFailover, and updating Netprobe to version GA6.2 or above.
The error WMIInterface::GetInstances Failed to get the next class (WBEM_E_OUT_OF_MEMORY) occurs when the Windows Server runs out of memory during process monitoring. This issue originates from the operating system and requires investigation by Windows system administrators.
Specifying the dashboard folder determines where the Web Dashboard server loads dashboards on startup. You can set this folder by editing the config.xml file in the /config directory to include the dashboard path.
Upgrading the Geneos Database Schema involves identifying your current schema version and applying the latest update script. The process includes disabling database logging, verifying the latest schema version, and running the appropriate SQL update script.
Using a client certificate enables SSL authentication in the Web-Mon plugin for Netprobe. Configure certificate files in PEM format on the Netprobe machine and verify them with the curl command.
Using a path variable lets you enable or disable rules based on a custom dataview's rule status. This method adjusts rule logic dynamically without using active times or manual rule disabling.
Using a path variable in Geneos rules allows snoozing or unsnoozing managed entities. This involves referencing snooze status in a toolkit dataview and triggering actions based on that status.
Using a rule to capture headline names with zero values in a dataview involves path aliases and string functions. The rule block example shows how to display these headline names in a specific "OrderValue 0 Instance" headline.
Using a Windows account with the Geneos REST API requires password-based authentication when the gateway is not using SSO. Configure the Windows account with a user-defined password and assign appropriate permissions in the Gateway Setup to enable REST API access.
Custom Format Masks in JMX allow output values from MBeans to be reformatted using Java code. You must build, compile, and deploy a Java program as a custom mask, then apply it in the JMX plugin configuration.
Extractor plugin monitors webpage content by extracting data using configured XML files. A template using the licensing page example is provided for consistent monitoring setup.
Multiple IDs can be used in the State Tracker's Dynamic Tracker with Templates for compound identification. The tracker identifier is created by joining values from named capture groups with underscores.
Using Managed Entity properties in rules enables evaluation based on attributes and parameters. Rules can reference multiple properties to compare values across different Managed Entities for targeted monitoring.
Using Python with the API plug-in requires Python version 2.7 or higher. The example script sends data to netprobe via the API plug-in after setting up a Managed Entity and API sampler.
The REST API can be used to find the connection state of Netprobes in Geneos. You can query the Gateway for the Netprobe's Connection State Runtime Parameter to identify Netprobes with "Up" or "Down" states.
The REST API in Geneos allows querying the Gateway for a snapshot of a specific dataview. This feature is available from GA5.14 Gateway version and enables publishing the dataview output using defined syntax.
Pausing and resuming database logging in Geneos is done using REST Service commands after enabling the REST Service on the gateway. Successful commands update the gateway log and UI icons, with connection status reflecting actual database activity.
RMS commands automate upgrading Windows Netprobes using batch files and configuration in Geneos Gateway. The process transfers installers, validates settings, and runs silent uninstall and install commands for seamless upgrades.
Rules cannot be applied directly to the first column of a dataview because it serves as a unique row identifier. Use a path alias pointing to @rowname and define a variable to perform calculations or comparisons within your rule logic.
Configuring the SSO Agent to work with a KDC using AES256 requires specific Java and Active Directory settings. Proper encryption types, SPN registration, and user ID formats ensure successful Kerberos ticket authentication.
HTTPS server verification in Geneos on Ubuntu and SLES may fail due to the default CA bundle store path mismatch. Specify the actual CA bundle path in GSE settings or create a symbolic link to the correct CA bundle location.
The email.pl script sends alerts to email addresses defined in a managed entity's attribute using userdata "eMail" in the rule block. It explains how to pass these email addresses to the email.pl action script for alert delivery.
Verifying available entitlements of the current LICD license involves checking license usage and reporting. You can use the Licence Usage plugin or access the Licensing Reporting page via a web browser for accurate license usage details.
Netprobe connectivity to IBMi plugins depends on the JTOpen library and requires multiple open ports for communication. Users can verify connection using the JPing utility and should consult Geneos plugin documentation and their IBMi administrator for configuration.
Viewing all functions available when setting up a rule involves accessing the Functions menu from the rule Block section. This menu provides a complete list of functions, with detailed explanations found in the Functions section of Rules, Actions, and Alerts.
LDAP error code 49 with data 52e indicates authentication failure for the Query User credentials in Hub's LDAP Config. Verify the username and password format, and use ldapsearch to test LDAP credentials and server connectivity.
Gateway Hub SSO with LDAP and Kerberos can cause request header size errors for some users. Adjusting maximum request header sizes in start-up scripts resolves these errors across all cluster nodes.
Actions in Geneos do not fire when an item is snoozed because snoozing stops severity propagation and blocks actions by default. To fire an action after snoozing, change the action's Restrictions setting to "Always Fire" under the Action Advanced tab.
The priority of IBM i jobs created by Geneos plugins is controlled by the IBM i system, not the plugins themselves. Lowering job priority can delay query results, and your IBM i sysadmin can adjust priorities if needed.
IBMi Plugins using the JTOpen API secure communication through encrypted SSL ports, ensuring confidentiality, integrity, and authentication of data transmissions. Port 449 is not encrypted but functions as a non-sensitive server port mapper.
The value captured when an Action with Repeat Interval or Escalation runs depends on whether USERDATA or the \VALUE variable is used. USERDATA remains the same during repeats, while \VALUE updates each time the action fires.
No variable automatically detects the Gateway name in post setup apply scripts. The available environment variables do not include any that identify the Gateway server.
Integrating ServiceNow with Geneos automates alert messages and enables ticket management within Geneos. Configuration guidance is available via an open-source solution on GitHub, with customization offered through Professional Services.
Gateway load statistics help identify Geneos monitoring performance bottlenecks. Gateway-Load plugin data can be collected, reset, sorted, and analyzed by categories like Rules and XPathStats.
Data transmission between netprobe and gateway in Geneos is not encrypted by default. Users can enable Transport Layer Security (TLS) to secure communication and are advised to use updated versions with enhanced security features.
The API plug-in in Geneos does not support a 'Sample Now' feature because updates are controlled by user-defined code in the sampler configuration. Data is pushed from the application you write, rather than being collected on demand by Geneos.
Locating all users with Administrator permissions across multiple Geneos gateways requires extracting data from each gateway setup. This can be done by parsing gateway.setup.xml files or enabling the User manager webpage with proper HTTP connection settings.
Active Console is shipped with its own JRE and does not depend on the OS Java version. Users can maintain their own Java by using the no-jre version and should refer to the Geneos Compatibility Matrix for supported Java versions.
The FKM's ignore key has a 500-row display limit in the Gateway Setup Editor to prevent performance issues. You can view more rows in XML mode or create multiple FKM tables to manage additional entries.
The SQL-Toolkit plugin allows checking the status of SQL queries. You can enable the Show headlines option in the plugin's Advanced tab to view query status.
The rmc-interface plugin can display numeric values with extra text like "per second" by default. Disabling the "Show as Rate" setting in the GSE sampler removes the extra text and shows only the number.
The NetProbe command timeout controls how long a command can run before timing out, with a default of 30 seconds. You can increase this timeout by configuring the setting under the Probe’s Advanced tab.
Linking a tool's background color to another Dashboard's severity level shows overall state visually. Use the Background color linked to Severity modifier and set a URL path to connect the dashboards.
Showing the client login time in Active Console requires calculating the connection duration using a rule. This is done by applying a gateway connection plugin and converting epoch time to a readable format.
Snoozing a managed entity by an action from a rule on another entity requires two gateway rules. One sets severity, and the other counts severity to trigger the snooze action using path aliases.
There is no web version of Active Console available in Geneos. Web-Dashboard, Web-Slinger, and ITRS Analytics offer web-based views but do not replace Active Console functionality.
Creating a dashboard for a specific screen size in Geneos requires designing for the most common display resolution. Use a dashed rectangle shape as a visual guide to match the desired screen dimensions during design.
Displaying MBean object names in the JMX sampler requires using a colon ":" instead of a period ".". Use the syntax "$1:attribute" in the row template to show specific object name values.
JMX authentication errors occur when the username or password is invalid or misconfigured. The issue can be resolved by verifying login credentials, selecting the correct password type, and properly configuring JMX remote access and password files.
Monitoring JBoss with the JMX plugin requires a workaround since direct support is unavailable. This involves configuring Netprobe with jboss-cli-client.jar and using JConsole to extract MBean objects and attributes.
The error "Access denied! Invalid access level for requested MBeanServer operation" occurs due to insufficient permissions when invoking an MBean method. To resolve this, edit the jmxremote.access file and set the user's permission to readwrite.
Java RuntimeException occurs when opening a KBA link without the full http schema in the URL. Including the complete URL with the http:// schema resolves the error and allows the KBA to open correctly.
FIX Analyser 2 Netprobe versions GA7.3.x and GA7.4.x may crash intermittently due to issues with the PCRE2 library. The problem is fixed in Geneos version GA7.5.0, and users should upgrade cautiously.
Libraries not found errors occur when starting Geneos components due to missing library dependencies. The FAQ advises verifying that all required libraries and their dependencies are installed and compatible with the operating system.
License FORMAT: OLD and License FORMAT: 2026 are incompatible with mismatched License Daemon (LICD) versions, causing decode and decryption errors. Always match your LICD version when requesting licenses to ensure proper format compatibility and avoid errors.
License installation in Geneos involves replacing the license file on the license daemon host. The process requires stopping the daemon, backing up the old file, installing the new file, and restarting the daemon.
Managing load in Geneos involves understanding data views, sample rates, and sampler configurations. Guidance covers hardware recommendations, load monitoring, and strategies to optimize performance across probes, gateways, and the Active Console.
The Market Data Monitor shows an InvalidUsageException error when subscribing to fields not in the data dictionary. Verify you are using the correct or updated data dictionaries, including custom ones, and update Netprobe binaries if needed.
SSO Agent INFO log entry with an Error indicates token authorization issues due to IP mismatches. This occurs when Active Console IP differs from the token source or when the SSO Agent is not running.
The Message Tracker plugin's lost messages dataview can show duplicate messageIDs due to how messageIDs are generated. To resolve this, add more tags in the Swift Reference messageTrackerTagMapping to ensure messageIDs are unique.
The Query Timeout setting in the MIB Monitor plugin defines the time limit for network session queries before retrying. It is configurable with a minimum of 5 seconds and determines when the plugin initiates another query after a timeout.
Microsoft Kill is included in the Windows Netprobe package to provide tools for managing processes and registry tasks. You can safely delete kill.exe if it is not needed by your team, though an investigation is ongoing.
The minTLSversion parameter is not present in the Windows netprobe service startup options because it is added to the netprobe's registry keys instead. To configure minTLSversion manually, remove the /verysilent installation option and select it through the installation GUI.
Monitoring a small subset of a gateway involves viewing specific managed entities or dataviews within Geneos. This can be achieved by configuring Gateway Sharing with appropriate Exporting and Importing sections or by creating a separate gateway for targeted monitoring.
Monitoring for RMDS / TREP / RTDS covers the Geneos integration for out-of-the-box monitoring of the RTDS platform and related applications. It provides configuration files, dashboards, and samplers to monitor core RTDS components and supports customization for detailed site-specific needs.
Monitoring Solace systems using Geneos provides real-time visibility and management of Solace routers, including hardware status, message rates, and configuration details. The Geneos Solace plug-in enables centralized monitoring, alerts, and control of multiple Solace appliances from a single management environment.
MQ connection fails with reason code #2035 due to missing Netprobe user permissions. Grant required put, inq, and get permissions using setmqaut commands to resolve the authorization error.
MQ Queue Info plugin requires specific permissions to fetch queue details from IBM MQ. The necessary permissions are +connect, +inq, and +browse for proper data access.
MQ binding mode is supported by Geneos Netprobe for connecting to MQ. To enable binding mode, set the MQ\LIBRARY\FILE environment variable to the appropriate mqm library file.
Dashboard object properties revert to previous settings due to configuration conflicts or permission issues. Adjusting user permissions or resolving conflicts can prevent property changes from reverting unexpectedly.
Database logging issues occur when the Gateway cannot connect or write to the database. Solutions include checking paths, permissions, network, paused status, table versions, and database configurations.
Information needed before reporting a Geneos gateway or netprobe crash includes machine identity, core file timestamp, gateway diagnostics file, netprobe log, binary platform, and optionally a gdb backtrace. Gathering these details helps ITRS investigate the crash efficiently.
Geneos licence expiration issues occur when a renewed licence is not received before the expiry date. The FAQ advises checking with the licence owner and contacting Client Services with hostname and hostid details for resolution.
Notifications not popping up in Active Console can occur if notifier settings are disabled, inactive, or incorrectly configured. Ensure notifications are enabled in Notifier General Settings, notifiers are active, and paths and properties are correctly set.
The Active Console output window may not be visible or maximized from the taskbar. Creating a new workspace or using the taskbar Move option can restore the window to the screen.
A Sampler not showing any dataview in Geneos can be caused by improper configuration, license issues, or plugin and version mismatches. The FAQ provides guidance on setting up the Java environment, verifying licenses, and ensuring compatible plugin and netprobe versions.
The FKM Default Ignore File name option does not work if Content Type is set to Unicode Autodetect. This issue occurs with UTF-8 or UTF-16 files and is tracked under bug report COL-5759.
The NetProbe FKM right-click Accept option does not appear when multiple files are from different Gateway versions. This issue occurs if selected files include both GA4.5 and earlier Gateway versions.
Access to NetProbe ORB pages requires setting the TRUSTED\DEBUG\HOSTS environment variable in the NetProbe start script. Defining export TRUSTED\DEBUG\HOSTS="+" allows any host to access the NetProbe ORB page.
Changing the Netprobe server port in Windows can be done without reinstalling by editing the registry key NET\PORT. Alternatively, use the na\setenv.exe utility in the NetProbe installation folder to update the port setting.
Monitoring files with changing names can be done using the Dynamic Files option in Geneos NetProbe's FKM. This method uses a regular expression to identify files based on specific naming patterns.
The netprobe fails to start due to a non recoverable error caused by port 7032 being in use. Changing the netprobe to run on a different port resolves the startup issue.
NetProbe allows checking if a log file has not been updated within a specified time period using the Not Updated In key. This key triggers alerts based on the configured time interval in seconds to monitor file update status.
Configuring the Perfmon plugin to monitor SynchronizationNuma counters may show a blank dataview due to required text string values. The workaround is to use the text names for objectID and counterID instead of their numeric IDs.
Monitoring a custom event log in Windows using Geneos NetProbe involves configuring the File Kernel Monitor (FKM) to track specific log files. The process includes setting up FKM to read and report events from the custom log for effective monitoring.
NetProbe date formats can include a leading zero in the day of the month by default. To remove this leading zero, use %-d on Linux and %#d on Windows in the date format string.
NetProbe's net-snmp module writes messages to standard error, causing output to appear on standard output when configuring the Trapmon plugin. To prevent this, redirect standard output to a separate log file using shell commands like those supported in bash.
Changing a Windows Netprobe from Insecure to Secure mode requires stopping the Netprobe service, backing up and editing the registry ImagePath to add SSL parameters, then restarting the service. This process ensures the Netprobe runs with secure communication settings.
Upgrading a Linux Netprobe in Geneos can be done using a sequence of RMS commands executed as a single "Upgrade" command on the gateway. This process transfers the binary, extracts it on the Netprobe server, and restarts the Netprobe automatically.
Netprobe connections to the Gateway can be validated using SSL certificate chains to ensure secure communication. The Gateway uses the -ssl-certificate-chain option to verify Netprobe certificates, allowing connections only from trusted certificate authorities.
The Netprobe error occurs because libnsl.so.1 is missing while libnsl.so.2 is present. Installing the libnsl package resolves the issue by providing the required libnsl.so.1 library and creating necessary symlinks.
Netprobe crashing can cause disconnections and missing monitored data in Geneos. The FAQ details possible causes like server issues, memory protection restarts, errors, resource shortages, and security policies, with guidance on diagnosing and resolving each.
Netprobe disconnections occur when the Gateway cannot connect to the Netprobe due to process crashes, unresponsiveness, license issues, or security policy enforcement. Troubleshooting involves checking Netprobe process status, logs, license availability, and ensuring antivirus or SELinux configurations allow Netprobe operation.
Netprobe connection rejection occurs when a Netprobe cannot connect to a Gateway due to configuration or network conflicts. Resolution involves verifying port settings, ensuring the correct Gateway is active, and checking logs for connection details.
Netprobe automatically restarts due to a memory protection feature that prevents memory leaks from Netprobe or its plug-ins. To resolve this, upgrade Netprobe to a version with memory leak fixes as noted in the Release Notes.
Netprobe versions up to GA5.9 support RHEL 6 OS libraries for Geneos. Support for RHEL 6 and GA5.X ended on July 31st, 2021.
NetProbe RMC plugin reads shared memory from RTDS components like ADH, ADS, and ATS. Troubleshooting uses RMC recorders and Refinitiv tools to check memory segments and resolve common errors.
Running Windows Netprobe as an Active Directory user requires proper permissions and group memberships. Adjust the Netprobe service logon account and add the user to local admin or performance monitoring groups to ensure full functionality.
Self-announcing netprobe setup files support configuring a list of gateway types. This allows minimal setup file configuration while managing gateway types primarily on the gateway side.
Netprobe on 64-bit operating systems may show high virtual memory usage due to JVM allocation, especially when running a JMX plugin. This is normal behavior and not a problem, as virtual memory size is largely irrelevant on 64-bit systems.
The Processes plugin reports a timeout error when it fails to execute properly. Adjusting regexMode, file descriptor limits, and advanced tab settings can resolve this issue.
Netprobe startup issues can be caused by incomplete libraries, port conflicts, insufficient system resources, or plugin crashes. The FAQ provides troubleshooting steps including verifying library dependencies, checking port availability, ensuring adequate resources, and isolating problematic plugins.
NetProbe Webmon reports responseCode 401 due to Windows Loopback Protection on local machines. Disabling the Loopback Check registry key or using 127.0.0.1 in sampler config resolves local authentication failures.
Netprobe runtime states indicate the connection status between the gateway and a netprobe process, including states like Up, Down, Unreachable, and Rejected. Each state provides specific information or parameters to help monitor and alert on the probe's connection health.
Actions associated with alerts are removed when the Netprobe containing those alerts goes down or disconnects. Users can verify this by checking the gateway log for messages showing actions fired, Netprobe down, and action removal.
A timing record in Geneos is used to monitor the shared memory segment status accessed by the RMC plugin during its workflow. It helps identify issues like faulty shared memory caused by improper process restarts, ensuring reliable data retrieval.
SSL Security Errors can occur in SQL-Toolkit Windows samplers querying MS SQL Server databases. Updating SQL client libraries and matching Netprobe SSL settings with the DBA's server configuration can resolve these errors.
The message 'FKM stopped on this file - excessive update rate detected.' relates to NetProbe file monitoring limits. Users should refer to the latest documentation on docs.itrsgroup.com for updated guidance and solutions.
Netprobe shows an invalid password error when the password is missing or incorrect. Passwords can be set via Gateway Setup Editor, startup scripts, or Windows Registry depending on the OS.
The "View Netprobe Log" error "STDOUT:NOT-FOUND" occurs when netprobe is started without a logfile defined. This happens if netprobe runs with the -nolog option, causing logs to be written to stdout instead of a logfile.
Netprobe connection rejection occurs when it is already connected to another gateway. Check netprobe and gateway logs to verify connections and ensure unique ports for each netprobe.
Netprobe disconnections can occur due to running out of license slots or the Licence Daemon (LICD) being in a shutdown or disconnected state. Monitoring the Licence Daemon using the Gateway-licence usage plug-in helps track license usage and prevent disconnections.
The processes plugin instance count may show 0 after upgrading NetProbe due to incorrect parent-id configuration. Correcting the Search String configuration resolves the issue by aligning with the updated plugin behavior in GA4.10 and above.
The Netprobe log contains information about startup, shutdown, gateway connections, sampler initialization, and error messages to assist in troubleshooting Netprobe issues. It provides general guidance on log contents and suggests enabling debug settings only when advised by ITRS personnel.
Netprobe consuming high CPU occurs when plugins extract large amounts of data, causing sustained high CPU usage. Solutions include monitoring by exception and splitting samplers across multiple Netprobes to balance CPU load.
Zombie processes are terminated child processes that remain in the process table until reaped by their parent. Geneos detects and monitors long-running zombie processes using the Hardware plug-in and user scripts to help identify potential issues.
Netprobe running X-* plugins with setuid or capabilities ignores LD_LIBRARY_PATH, causing shared library loading failures on Linux. Workarounds include separate Netprobe installations for X-* plugins, symlinking libraries, or updating system ld.so.cache with required directories.
The message means a Netprobe script produced no output on standard output (stdout). To see output in Netprobe, ensure the script writes directly to stdout without redirecting output elsewhere.
Netprobe samplers not running at the sampling interval can cause outdated data in the Active Console. Enable debug on the Netprobe to identify slow samplers and check Gateway logs for overload or stale data issues.
Netprobe sends sample data efficiently to the Gateway using Dataviews and selective updates. Proper row naming and stable column order help optimize performance and reduce Gateway load.
Netprobe unable to connect to Gateway can result from network, version, or configuration issues. Troubleshoot by verifying connectivity, checking versions, correcting connection settings, and ensuring Gateway is trusted by Netprobe.
Netprobe unable to connect to Gateway can result from network, configuration, or version issues. Troubleshoot by verifying connectivity, settings, licensing, and compatibility between Netprobe and Gateway versions.
Netprobes appear greyed out in Active Console due to connection, service, crash, license, or rule issues. Troubleshoot by checking network connectivity, service status, license validity, and severity rule configurations.
The Network Plugin populates cardSpeed and duplex values from system files by default, not ethtool. If files are inaccessible or unknown, the plugin shows unknown values unless ethtool runs with elevated privileges.
PercentRecvErrors is calculated by dividing error packets by total received packets and multiplying by 100. This uses network interface data, such as Linux ifconfig command output, to determine error percentage.
The Network plugin can display virtual network interfaces by default. To hide virtual bonded interfaces, uncheck the "Show virtual interface" setting in the plugin.
The Network plugin matches each Windows interface to only one IP address. It ignores additional IPs by matching GetIfTable with GetIpAddrTable entries.
Newer Geneos Webserver and Web Dashboard versions require Java 11 and are not compatible with Java 8. Using Java 8 causes startup errors because the application was compiled with a higher Java version.
Access issues occur after authentication changes prevent gateway setup editor access or cause login failures. Solutions include verifying user account definitions, permissions, case sensitivity, and resetting the gateway connection.
OldestMsgAge is not displayed when the MSGAGE Queue attribute is blank for a message stuck in the queue. This occurs because the MSGAGE attribute holds the oldest message age, which can be empty based on the queue status.
Oracle indexes do not shrink automatically after deleting data from a table. Regular index rebuilding is recommended, and Geneos provides guidelines on index compression without altering table structures or query results.
Password retrieval from HashiCorp Vault in Geneos occurs when a netprobe connects and the Gateway requests the token and password. Cached external passwords can now be refreshed regularly or on setup reload starting from version GA7.1.0.
Performance issues and disconnections can occur due to Gateway overload or network interruptions. Adjusting Rule Threads, splitting Gateways, or increasing system resources can improve stability and data freshness.
Database logging may experience delays or fail to write records due to maxRequestQueueSize errors and cache files. Monitoring connection status and cache metrics helps identify issues, while involving a DBA can resolve database-level problems.
Phantom netprobe processes can keep the netprobe port locked due to Windows utilities like JIT debugger or Windows Error Reporting maintaining the process environment. Acknowledging the JIT debugger prompt releases the trapped process environment and frees the port for restart.
The Windows Perfmon plugin monitors Windows Disk I/O metrics using sampler configurations. It provides example configurations for setting up Disk I/O monitoring with Perfmon samplers.
The process plugin allows filtering processes by user ID using the username option in the process filter section. Setting the value to root displays only root-owned processes, and instance count filtering is available via displaymode settings.
The processes sampler can automatically run a restart script when a monitored process stops, but the script may fail without clear log errors. Checking file ownership, permissions, and the netprobe environment helps identify and resolve restart script failures.
The maximum number of characters for a process descriptor that Geneos Processes Plugin can match is over 10,000. Upgrading to Geneos GA5.5 or later with the fixed Netprobe version resolves issues with long process names.
The Netprobe captures CPU information for individual Windows processes using the Win32\Process WMI class. It calculates PercentCPU by combining UserModeTime and KernelModeTime values relative to total CPU time across all processes.
The Processes plugin monitors all instances of a process by defining a common process name string. To monitor each instance separately, unique search strings must be defined for each process variation.
The Processes plugin may show "PROCESS SAMPLE WARNING Unable to obtain tgid" messages in the NetProbe log file. These warnings are harmless timing issues and do not impact monitoring or the environment.
The REST API can be used to obtain a list of all snoozed objects such as managed entities, dataviews, and table cells. Examples show how to query the XPath for snoozed data items using the API.
The REST API can return a list of managed entities with warning or critical severity states. Severity states are defined by numeric codes, with 2 representing warning and 3 representing critical.
The REST API in Geneos can be used to run the /GATEWAY:reloadSetup command to reload configuration files. You can reload all files by default or specify a particular include file and verify changes using the Gateway-includesData plugin.
The Rest-Extractor header value can include both static values and supported variables such as plainTextPassword, provided they are properly defined and populated. Variables must be plain text or encoded tokens, and unsupported types like stdAESPassword may cause errors.
REST-Extractor plugin requires Netprobe, Gateway, Licence Daemon v4.11+, and a compatible Java environment. It helps extract JSON data from URLs and provides guidance on setup, common errors, and query validation.
A rest-extractor sampler in Geneos may display a blank dataview if the Java environment is not configured correctly. Ensure the JAVA, LD_LIBRARY_PATH, and PATH variables are set to the correct directories for your Java installation.
The Processes Plug-in may not find certain processes on RHEL 7+ because systemd replaces init and changes process ownership. Configuring the plug-in with the correct process parameters and PPID settings helps track systemd-launched processes accurately.
The Geneos netprobe used for monitoring TREP components should ideally run as the application user owning the shared memory, typically the radmin user. The netprobe only reads shared memory content and does not perform write operations, making it non-intrusive.
Rule blocks in Geneos are greyed out due to illegal formatting in the rule code. To resolve this, switch to XML mode, clear the block content, and manually re-enter the rule statements.
Rule examples in Geneos demonstrate how to create and manage Gateway rules using XPath expressions. They provide guidance on triggering actions, comparing values, converting units, and monitoring specific conditions within rules.
Rule variables in Geneos may not resolve correctly due to incorrect XPath setup or misspelled variable names. The FAQ guides verifying and correcting XPath paths and ensuring consistent variable naming to fix these issues.
Rules in Geneos handle non-standard numeric formats by interpreting strings that start with a number as that number and all other non-empty strings as zero. This allows rules to apply values correctly even when data appears as non-numeric strings.
Comparing two values from the dataview uses Path Alias with a Relative Path in rules. The rule block section then compares these values to determine the status on the dataview.
Rules can trigger actions during two specific periods if values stay above thresholds. Define active times and set severity to critical only within those periods to manage alerts effectively.
Excluding a Rule target without modifying the original Rule in Geneos is done by creating a new rule with higher priority and enabling stopFurtherEvaluation. Alternatively, adjust the original rule's target XPath to exclude specific dataitems using the not() function.
Stopping further rule evaluation after a specific rule runs requires configuring rule priority and enabling the "Stop further evaluation" option. Set the preferred rule with higher priority and activate this option in the Rule > Advanced tab.
Loops cannot be directly used in the rule block section of Geneos rules. Instead, use available Geneos Operators, Functions, or action throttling to repeat actions or implement simple algorithms within rules.
A computed cell retains its severity outside the Active time because its active state is a logical OR of all affecting rules. To remove severity after Active time ends, disable "Active time affects cell" in the rule's Advanced tab.
The Secondary Gateway in a Hot-Standby Geneos setup may report missing actions due to absent scripts, missing definitions, or invalid script paths. Resolving this involves replicating scripts, synchronizing configuration files, and correcting script paths on the Secondary Gateway.
Running multiple License Daemon (LICD) instances on the same host is not allowed in Geneos. Attempting to use a different LICD port results in the duplicate instance terminating with an error message in its log file.
Security and identity management information includes documentation on security testing, penetration tests, disaster recovery, and user roles. Contact compliance@itrsgroup.com for details on certifications, test summaries, and current system user roles.
Seeing MBean N/A occurs when JMX MBean names are missing on the target server. Verify JMX connectivity and MBean availability using the command line with the JMX-Server plugin.
The Gateway hostname is not available as a built-in variable in Geneos and must be manually defined. Users can create and access this variable in environments or managed entities for use in Sampler Toolkit scripts and rules.
Settings from an include file in Geneos Gateway are not applied when nested include files are used, as nested includes are not supported. To resolve this, define the settings directly in an include file or in the main setup file.
Email notifications are not recommended as the primary method for signaling alerts in Geneos. The primary alert notification should come from interaction with the Active Console, with email used only as a secondary tool.
The File Keyword Monitor (FKM) does not show a count for each trigger when using multiple-trigger mode. To display a count for each trigger, change the trigger mode to Single in the Gateway Setup Editor under the FKM Advanced tab.
FKM displays only the latest trigger by default due to single trigger mode settings. Changing the trigger mode to Multiple in the Gateway Setup Editor allows showing every trigger instead of just the latest.
The CNPI plugin does not support identical statistics on different STATS-LIST definitions, causing conflicts in multiple views. The issue stems from the CNPI API and must be resolved by Corvil, as ITRS cannot control it.
The SQL Toolkit sampler port field shows a greyed out default port value but does not use it automatically. The sampler obtains the port from the database client, so users must specify a different port if the default is incorrect.
SQL-Toolkit plugin may encounter login timeout expired errors when connecting to MS SQL Server 2022. Upgrading Geneos to version GA7.5.0 or later and ensuring the correct OLE DB driver resolves these connectivity issues.
Sybase connection issues in Geneos often result from client installation or environment variable misconfigurations. Solutions include verifying Sybase client setup, environment variables, and matching configuration files for successful database connections.
SQL Toolkit password authentication issues occur because passwords are encrypted and tied to specific machine environments. To resolve this, enter the original plain-text password in the Geneos configuration editor on the target server to generate a new encrypted string.
The SSO Agent does not automatically rotate its sso-agent.log file and requires manual configuration. Log rotation can be set up using Logback's RollingFileAppender with SizeAndTimeBasedRollingPolicy for effective log management.
Automatically starting and stopping a Windows service can be done using Geneos Win Services Plug-in. This involves creating a command, action, and rule to start the service when its status is Stopped.
The State Tracker plug-in only re-reads a file if the file's inode changes. Overwriting file content without changing the inode does not trigger a re-read, but moving or copying the file does.
The State Tracker plugin allows monitoring of lines with unique IDs using Dynamic Tracking with Templates. This involves marking the Tracker as a Template and defining identifiers with named groups in each key.
The "File Truncated" message indicates the monitored file has been shortened, usually by housekeeping tasks. To suppress it, enable "fileTruncateResetsTrackers" in the Advanced tab to reset trackers after truncation.
Stop and start commands are missing in the Processes plugin if the alias includes a pound character. Avoid using the pound character in process aliases to ensure these commands remain available.
Templated dashboards in Geneos enable faster deployment by providing pre-built widgets and tools for dashboard creation. Users must install template files, configure samplers, and customize SQL queries to integrate their own monitoring data.
The web dashboard may not display live data due to authentication issues between the gateway and the Web dashboard. Checking and aligning authentication settings in the Gateway Setup Editor and Web Dashboard configuration resolves the connection problem.
A question mark appears beside the Sampler name and "Nothing to Display" shows on the Metrics dataview when customized. To resolve this, verify and correct the Xpath in the Metric Table Properties for the dataItem.
Filename date expansion variables are built into FKM and FTM plugins but not directly available in the Toolkit plugin. Toolkit users can achieve similar functionality by using Linux or UNIX shell script date commands within the file path.
Adding line numbers and row counts in Toolkit script output applies to Linux/UNIX shell script toolkits. Use the GNU awk command to post-process output and append a pipe command to your sampler script execution.
Monitoring Google Cloud native databases like BigQuery in Geneos requires using the Google Cloud SDK instead of sql-toolkit. The Google Cloud SDK outputs SQL query results in CSV format, which can be integrated with Geneos using the toolkit sampler.
Passing environment variables set on a managed entity using the toolkit plugin enables script access. The toolkit plugin calls the script path and retrieves the environment variable defined on the managed entity.
Toolkit column sort order determines how data is organized and displayed in Geneos dashboards. Maintaining the correct sort order is essential for accurate data interpretation and effective monitoring.
The Toolkit plug-in in Geneos executes scripts asynchronously on a separate thread within the Netprobe. This prevents blocking other plug-ins and allows sequential or simultaneous execution based on the maxToolkitProcesses setting.
The Toolkit plugin scripts are stored in the Netprobe working directory on the host. These scripts are generated and updated each time the sampler configuration is saved or changed.
Tools missing from the Active Dashboards palette occur when they are manually removed and cannot be recovered. The recommended solution is to create a new workspace with a complete palette and import exported dashboards and views.
The Trapmon plugin allows testing SNMP trap message handling on Linux servers. Users can manually generate SNMP traps using the snmptrap command from the Net-SNMP packages to simulate alerts.
Trapmon plugin may show IP addresses instead of hostnames in the Source column. Verify DNS settings and SNMP trap configuration to ensure consistent hostname resolution and display.
SQL Server ODBC connection issues occur when the driver library is missing or misconfigured. Resolving this involves installing the correct Microsoft ODBC driver and setting necessary environment variables properly.
Creating Historical Charts from an MS SQL Server named instance can fail due to dynamic port usage. The solution is to connect using a fixed port number instead of the instance name to ensure stable connections.
Multiple snooze commands on a single item in Geneos are resolved by the earliest condition taking precedence. The item will unsnooze when the first specified time period ends or when the first severity change occurs.
The use of a load balancer for Geneos license daemon (LICD) servers is not officially supported but has been tested successfully by some users. Gateways continue to function during license daemon outages by using cached licenses, which persist across restarts.
Converting seconds to days, hours, and minutes using a Geneos rule is explained. The provided convertrule.xml file demonstrates how to perform this time conversion within Geneos.
Userdata declared in a rule block cannot be directly used as arguments in an Action. To use userdata, call it from a script file triggered by the Action, as userdata becomes an environment variable after action preparation.
Variable scoping in Geneos determines which variable value is used when defined in multiple places. The resolution follows specific rules based on sampler location and variable definition hierarchy within the Gateway Setup Editor.
The View NetProbe Log command in Geneos may not work if the LOG\FILENAME variable is not set in the start netprobe script. To resolve this, ensure the LOG\FILENAME variable is correctly configured in your NetProbe startup script.
Apache Log4j vulnerabilities affect specific Geneos components, requiring attention to security risks. Upgrading to Geneos GA5.12 or applying recommended workarounds mitigates these vulnerabilities and protects affected integrations and services.
WARN: RuleManager Flushing jobs messages in the Gateway log indicate that Rules are consuming significant processing resources, potentially causing Gateway performance degradation. Use Gateway Load Monitoring to identify slowdowns and refer to the Gateway Performance Tuning guide for solutions.
Dashboards get deleted after restarting the Web Server or Web Dashboard if they are not referenced in the config.xml. To prevent this, follow the upgrade steps outlined in the Web Dashboard guide.
The Web Dashboard error "Address already in use (BindException)" occurs when port 8080 is occupied by another process. To resolve this, identify and stop the conflicting process or change the Web Dashboard port by editing the GWSPORT variable.
Keytool error occurs when keystore password is incorrect or contains unsupported characters. Ensure passwords match and avoid unsupported characters to resolve the issue in Geneos Web Dashboard.
A blank web dashboard or object after upgrading to GA4.12 and above is caused by missing fonts recognized by OpenJDK Java. Installing the required font packages and restarting the Web Dashboard process resolves this issue.
Web Dashboard connection issues occur when the maximum thread count is reached. Adjusting maxThreads or using a load balancer can help manage user connections and improve performance.
SSL certificates may fail in Web Dashboard due to keystore format, password, or port conflicts. Solutions include using PKCS12 format, avoiding unsupported password characters, and configuring different secure and insecure ports.
Web Dashboard log entries show error codes 32 and 104 indicating connection issues. Solutions include installing a 64-bit Web Dashboard, splitting load, and monitoring Gateway and Web Dashboard performance.
Changing default Web Dashboard settings can affect visualization and functionality. The linked documentation details possible outcomes and consequences of modifying these settings.
Web Dashboard's MBeans enable remote monitoring of GatewayMonitor and DashboardMonitor via JMX. Use provided sampler XML files and adjust serviceURL for your Web Dashboard hostname and JMX port.
Web server fails to start due to inability to create a temporary directory. Modify the run script to set -Duser.home= to a writable directory like /tmp/webserver.
The Web-Mon plugin fails to load libcurl, causing monitoring errors in Netprobe. The issue can be resolved by verifying LD_LIBRARY_PATH and addressing elevated privilege configurations as described in the documentation.
The Web-Mon plugin requires the Expression and Conditions fields to match for the 'match content using success criteria' feature to work properly. Ensure both fields in the successCriteria response section contain identical values to resolve the issue.
The GLIBC_2.4 not found error occurs when Geneos Web Server runs on an outdated operating system. Users should verify system compatibility and update to a supported GLIBC version per the Compatibility Matrix.
Webmon's serverState headline cell and scenario status column display different values. These differences occur because each cell uses separate command outputs to determine its status.
The TIB-RV plug-in listens to advisory messages on specific RV subjects with wildcards. It uses RV.WARN.>, RV.ERROR.>, and RV.INFO.SYSTEM.HOST.STATUS.> to build dataviews via the TIBCO RV API.
The FKM clear key removes triggers set by matching FKM fail keys in monitored log files. It clears alerts based on timing and sampling scenarios, with detailed behavior explained and verifiable via the FKM2 debug setting.
Common error codes when monitoring HTTPS websites with the Web-Mon plugin relate to SSL/TLS protocol mismatches and outdated Netprobe versions. Upgrading Netprobe and verifying protocol compatibility help resolve these errors and ensure successful website monitoring.
The OS Type field in the Active Console shows the operating system as a number. Each number corresponds to a specific OS, such as Windows, Linux, or Solaris.
Severity mappings for the event_table in Geneos databases define status levels as OK, Warn, Fail, or Item deleted. These mappings use numeric codes 0, 1, 2, and -1 respectively to indicate event severity.
Netprobes go into suspended mode when the Gateway detects data input exceeding its processing capacity. The Gateway suspends connections temporarily based on Data Quality settings, which can be adjusted or disabled in the Operating Environment > Data Quality tab.
Geneos supports only ASCII characters between 32 and 126 for component communications using the EMF2 protocol. Active Dashboard can display Unicode for object labels since Active Console GA4.0, but user data must remain within the ASCII range.
The X-Traffic plugin uses Npcap or libpcap.so libraries to obtain network metrics. It requires Netprobe to run with elevated permissions such as root or administrator access depending on the operating system.
The DISK plugin uses the statfs function to determine available inodes on Solaris. It calculates inode usage by dividing free file nodes by total file nodes and multiplying by 100.
CPU utilization and PercentMemory use in AIX are collected using performance APIs. CPU uses perfstatcputotal and memory uses perfstatmemorytotal functions with data from vmstat and lsps commands.
ERROR: SM EMF2 PlugIn WIN-CLUSTER not found occurs when the plugin runs on Linux. The win-cluster plugin supports only Windows and requires a domain account with admin rights.
The "EMF2 PlugIn DEVICEIO not found" error occurs when the DeviceIO sampler Plugin is attached to a Windows Managed Entity, which is unsupported. To resolve this, un-attach the DeviceIO sampler from the affected Managed Entity.
UserManager Authentication with remote component Client failed means the Importing Gateway is using an incorrect username or password to connect to the Exporting Gateway. To resolve this, update the Authentication settings in the Importing Gateway with the correct credentials.
ActionManager Cancelled execution of command means a triggered command was stopped because the original threshold cleared before completion. The command’s script still runs to completion despite the cancellation message in the gateway log.
The error "Fail - MySQL server has gone away(2006)" indicates a lost connection with the MySQL database. It occurs because the default wait_timeout for a connection is eight hours, causing disconnections after this period.
The error indicates the Gateway failed to find a data item during database logging, causing potential invalid log states. Users should investigate database connection performance and Gateway load to address frequent occurrences and improve logging reliability.
Load Average in the CPU plugin shows CPU load over 1, 5, and 15 minutes on UNIX systems. These values come directly from the operating system without modification by the plugin.
The Netprobe log entry indicates a failed attempt to execute an Action on a remote Netprobe's imported dataview. This error occurs because actions cannot run on imported dataviews unless the Netprobe is on the Gateway server.
The XPath ancestor::* represents all ancestor elements of the previous XPath in GatewayLoad sampler reports. It shows high invocation and totalTime values because it includes all XPath evaluations within the gateway and cannot be edited or optimized.
A # character in a Geneos dataview causes rows to display as indented sub-rows. To avoid indentation, remove the # character from your Toolkit or Rest-API plugin script.
Include.history files are backups of configuration files created after saving config changes. Include.download files are backups of failed saves or hotstandby transfers and can be deleted if the system runs normally.
The limit of characters per cell for a Collection Agent plugin in Geneos is 1024 characters. To display more data, you should split your query into subsections since this limit is hardcoded and does not apply to regular plugins.
The FKM plug-in requires specific troubleshooting steps before opening a support ticket. Users should consult the FKM Technical Reference Guide, User Guide, FAQs, and error message resources, and provide detailed information if issues persist.
Locked out from the Geneos gateway after changing authentication settings can occur if the configuration is incorrect. To regain access, revert the setup XML files to a backup, remove the cache directory, and restart both primary and standby gateways.
The stringList variable is used in Gateway Setup Editor fields that accept multiple values. It works in Sampler's Expect Row, Visibility tab, and inList() function from Gateway GA4.2.0 onward.
NameValueList variables are used in specific areas within the Gateway setup to replace sections with name-value pair data. They can be applied in the rmc-interface plugin, Market Data Monitor, FLM Plugin, and Message Tracker Plugin configurations.
The license expiry date for Control-M, VMware, and Nirvana integration solutions is not managed by the Geneos License Daemon. You can find the expiry date by searching the integration's log file and set monitoring alerts for timely renewal.
The MQ Channel plugin shows which host connections are coming to the queue manager. Updating the Display format to Summary and Details on the Advanced tab reveals detailed host information.
Active Console and Web Dashboard fonts differ because the Web Dashboard server lacks the fonts used by dashboard objects. Installing the required Microsoft TrueType or ClearType fonts into the Web Dashboard's JRE/lib/fonts folder resolves this issue.
Netprobe crashes with the error message indicate a memory protection trigger caused by potential memory leaks or delayed plug-in start-ups. The resolution involves upgrading Netprobe, enabling debug options to monitor memory usage, and providing detailed logs when contacting support.
The Extractor plugin can return "ERROR: Could not parse source" when JSON fails XML validation. Enabling the debug menu helps locate errors, and using the REST Extractor plugin avoids XML conversion issues.
The "Unreachable" status in the X-Ping plugin occurs when the monitored host is down or network access is blocked. Troubleshoot by checking host availability, firewall rules, IP filtering, and configuring the Source IP in the plugin's advanced settings.
Parentheses in Geneos rule blocks disappear when they are not logically necessary. The setup editor automatically removes unnecessary parentheses, displaying them only if required for logical clarity.
The error occurs when using timezone settings without enabling gateway-controlled sampler active times. Enabling this setting shifts control to the gateway, allowing samplers to support timezones properly.
Gateway SQL requires unique column names and does not include source table prefixes automatically. Using aliases to create unique column names resolves issues with missing column data in query results.
Item deleted -1 occurs when a cell value is removed, causing severity to change to undefined. This results in an item deleted message in the event ticker and database logging event table.
The Web Dashboard flickers and shows blank areas because it renders images via ajax during each refresh. Adjusting the tileCacheSize and updateRate settings in the config.xml file can reduce flickering and improve rendering performance.
Netprobe disconnections can occur when the Control-M plugin causes delays due to multiple REST API calls and network latency. Troubleshooting involves locating Netprobe near the Control-M API server, limiting dataviews per sampler, and enabling SAMPLING debug for detailed timing analysis.
The path editor in the Gateway Setup Editor may not match data items due to missing flags in the GatewaySetupEditor.gci file. Adding specific flags without trailing spaces resolves the issue and enables proper path evaluation.
The Solaris netprobe on 32-bit systems can rapidly increase zombie processes due to a 256 file descriptor limit imposed by the Solaris stdio library. To exceed this limit and prevent the issue, a supplemental library must be loaded.
Inverted scheduled periods in Active Time are combined using a logical "OR," causing them to be active continuously. Using the Override option is recommended to properly manage active times instead of combining multiple inverted periods.
FKM shows "WARNING: Being used exclusively by another process" when a file is locked by another process. Use Microsoft Process Explorer to identify the locking process and ensure Netprobe has read-access permission.
The gateway requires a valid license file or connection to the Licence Daemon to operate. Licensing can be managed via the Licence Daemon or a temporary license file using the -licence parameter.
WebDashboard appears blank on Red Hat Enterprise Linux 7.4 or higher due to Java font issues. Installing additional fonts or configuring font settings resolves the blank display and Java errors in WebDashboard.log.
Netprobe may fail to start on Windows Server due to perfmon counter issues or ntdll.dll errors. Rebuilding counters or rebooting the server can resolve these startup problems.
The Gateway Setup Editor reformats rule blocks when saving because it converts the rules into XML, enforcing a standard formatting that removes user-defined spaces and white space. This formatting behavior is fixed and cannot be configured or disabled.
TOP plugin may show dead processes when the PPID is killed or tail off period is enabled. The tail off period setting keeps processes visible for a set time after breaching the threshold parameter.
ntpAvailability shows "NA" in the Hardware plugin when the NTP service is not running or ntpq is inaccessible. To resolve this, ensure the NTP service is active and Netprobe can run the ntpq command on the monitored host.
The FKM sampler in Geneos is designed to monitor new lines in large log files without scanning the entire file, minimizing performance impact. Parameters like maxSamplesLagging and maxLinesProcessed help manage performance for files with high growth rates.
Windows Netprobe shows ERROR: HARDWARE PdhEnumObjectItems() failed due to Perfmon counter issues. Upgrading to version 7.4.0 or using a restart workaround can restore hardware sampler functionality temporarily.
Identifying the Windows NIC device name required by Netprobe for X-plugins monitoring is not documented. You can obtain the NIC device name by running the NetprobeNT executable with the -if option in the Netprobe binary directory.
X-Multicast computes dataRecvRate by dividing data size by sampling interval and converting to KB/sec. MsgRecvRate is calculated by dividing message count by the sampling interval.
XPath usage in Geneos describes how to locate and extract values from gateway items using predicates, functions, and operators. This guide provides examples of XPath syntax, predicate functions, operators, and attribute listings for accessing state, managed entity, and runtime parameters.
No FAQs match your search.