Available under Settings | Account Information, the Account Information page has three pages of settings:
On the Contacts page, basic information about your portal, account contacts, and resource counts/usage is available.
LogicMonitor deploys new versions approximately every three weeks. You can view the current version of your portal at the top of this page.
The Usage Summary tables on this page provide usage information for monitoring activities and account features that have usage limits such as device monitoring or dynamic thresholds. There are four tables, each devoted to a different aspect of LogicMonitor’s operations.
Note: Counts for the various resources in monitoring represent all resources that have been added into monitoring, regardless of their current status. For example, a device that has been disabled (or is considered dead by LogicMonitor due to inability to access) or a device for which monitoring is disabled is included in this table’s counts.
|Devices||The devices count is a count of all devices that have been added into monitoring. A device is any resource that is monitored by a standard LogicMonitor Collector. Upon expansion of this row, you can see the overall device count broken down by standard devices and public cloud resources.
Note: Although Kubernetes resources are monitored by standard LogicMonitor Collectors, they are not included in the devices count; Kubernetes resources have their own dedicated count.
|Cloud Resources||The cloud resources count is a count of all resources monitored via LogicMonitor’s Cloud Collector. Upon expansion of this row, you can see the overall cloud resources count broken down by the three major public clouds.
Note: Cloud resources monitored by a standard LogicMonitor Collector are counted in the devices count, not the cloud resources count.
|Config Devices||The config devices count is a count of all resources to which ConfigSource LogicModules have been applied. (This count is only applicable for portals with the ability to monitor and alert on configuration files. If this capability is not currently available in your LogicMonitor platform and you would like to learn more, reach out to your customer success manager.)|
|Kubernetes Resources||The Kubernetes resources count is a count of all Kubernetes, nodes, deployments, services, and pods in monitoring.|
|Services||The services count is a count of all services created in LogicMonitor. A service is a grouping of instances across one or more monitored resources. This count is only applicable for portals with the LM Service Insight feature.|
|Websites||The websites count is a count of all monitored websites. This includes web checks and ping checks, both internal and external.|
|Instances*||The instances count is a count of all DataSource instances monitored across all device, cloud, and Kubernetes resources. A single resource represents at least one instance, but may represent more if a DataSource discovers multiple instances per resource. For example, a single resource could have multiple disks, server volumes, interfaces, or other identical components requiring monitoring and each of these would be considered an instance. Upon expansion of this row, you can see the overall instance count broken down by DataSource.|
|Resource Groups*||The resource groups count is a count of all resource groups, as created from the Resources page. Upon expansion of this row, you can see the overall group count broken down by static groups and dynamic groups. Additionally, for each group type, you can see the total number of properties set at the group level.|
|Dashboards*||The dashboards count is a count of all existing dashboards—public and private.|
|Widgets*||The widgets count is a count of all widgets across all dashboards. If the same widget is cloned or added to multiple dashboards, each addition becomes its own unique widget and is counted individually.|
|Reports in last 24 Hours*||The reports count is a count of all reports successfully generated in the past 24 hours—either manually or via a report schedule.||*Updates to those counts denoted with asterisks are performed every four hours so, unlike other counts, changes may not be immediately reflected.|
LM Definitions Table
|Saved Maps||The saved maps count is a count of all saved topology maps.|
|Root Cause Analysis Rules||The root cause analysis rules count is a count of each saved root cause analysis definition. This count is only applicable for LogicMonitor Enterprise portals.|
|Alert Rules*||The alert rules count is a count of each saved alert rule definition.|
|Open Alerts||The open alerts count is a count of current open alerts.|
|Previous Day Alerts||The previous day alerts count is a count of all alerts triggered for the previous day (from 12 a.m. to 12 p.m.).|
|*Updates to those counts denoted with asterisks are performed every four hours so, unlike other counts, changes may not be immediately reflected.|
|User Roles*||The user roles count is a count of saved roles.|
|Session Users||The session users count is a count of all users currently accessing the portal via the UI.|
|External API Users||The external API users count is a count of all users currently (within last five minutes) accessing the portal via the REST API.||*Updates to those counts denoted with asterisks are performed every four hours so, unlike other counts, changes may not be immediately reflected.|
LM Computations Table
The counts provided in the LM Computations table are explained next.
|Dynamic Thresholds||The dynamic thresholds count provides a count for both the current number of dynamic thresholds in use as well as the maximum number allowed for your account (these counts are only applicable for LogicMonitor Enterprise portals). The number of total current dynamic thresholds represents the number of times your configured dynamic thresholds are potentially evaluated, meaning that if a dynamic threshold, even if only configured once, is inherited across multiple instances, each instance contributes to the total.
The maximum number of allowed dynamic thresholds per account is limited to eight per monitored resource (in this context, per monitored resource is the total of all monitored devices; cloud and Kubernetes resources; and services). This limit is an aggregate limit, enforced at the account level, not the per-resource level. For example, if you are monitoring 100 total resources, 800 total dynamic thresholds are permitted across your portal.
Note: If you’d like to see where dynamic thresholds are applied across your portal, run the Alerts Thresholds report, ensuring the Only show custom thresholds option is checked.
|Total Datapoints*||The total datapoints count is a count of all datapoints (normal and complex) in use. This count represents the number of times your datapoints are potentially collecting data for a resource. For example, a DataSource with five datapoints that is applied to five total instances will increase this count by 25.|
|Complex Datapoints*||The complex datapoints count is a count of complex datapoints in use. You can infer the count of normal datapoints by subtracting this count from the total datapoints count.|
Use the Contacts page to establish primary and secondary contacts for your LogicMonitor account. Notifications related to upcoming upgrades, billing issues, and other important account communications will be delivered to these contacts.
Portal Settings Page
As shown (and discussed) next, there are eight primary settings you can establish on the Portal Settings page.
To set a time zone, hover over the map and click a highlighted region or select a time zone from the drop-down menu.
Note: Only time zones tied to a city name (e.g. “America/Los_Angeles” as shown in the above screenshot) will auto-update according to Daylight Saving Time schedules; time zones that are prepended with “UTC” will not.
Note: As discussed in Users, time zones can additionally be configured on a per-user basis. This allows users to view and configure time-based data and settings relative to their local region.
Company Display Name
The company name entered here displays throughout your LogicMonitor account interface.
From this area of the tab, check one or both of the options to include acknowledged and/or SDT (scheduled down time) alert counts in the dynamic alert count that displays in the left-hand main navigation menu and the Alerts page.
If you wish to restrict the IP addresses that can access your LogicMonitor account, you can define a whitelist of allowed IPs from this area of the tab. The whitelisted IP addresses entered here must represent the public Internet facing IP addresses, not those used internally to an enterprise that are translated to public IP addresses.
You can identify addresses using any of the following formats:
- Hostname (e.g. mycomputer.mybusiness.com)
- IP address (e.g. 192.168.1.1)
- Network/mask (e.g. 192.168.1.0/24)
- Network range (e.g. 192.168.1.100-255)
Note: While you will be warned if your current IP address will be locked out upon saving the whitelist, it is quite possible to make a typing error and lock yourself out. In the event of this, contact support.
Enable Remote Session
Check or uncheck the Enable Remote Session option to disable or enable Remote Session on an account-wide basis. (For more information on Remote Session, see Remote Session.)
Require Two-Factor Authentication for all Users and Roles
Check or uncheck the Require Two-Factor Authentication for all Users and Roles option to disable or enable two-factor authentication on an account-wide basis. (For more information on LogicMonitor’s use of two-factor authentication, see Two-Factor Authentication.)
Note: Currently, two-factor authentication is not enforced when logging in through our mobile client.
User Session Timeout
To ensure the security of your account and data, select an appropriate default timeout value for users from the drop-down menu. Inactivity for the specified length of time will result in a user account being logged out. By default, this length of time is set to four hours.
Upon login, users have the option to check the “Keep Me Signed In” option. If this option is left unchecked, they will be returned to the login screen after the specified period of inactivity has passed.
If your account has single sign-on (SSO) enabled, this setting still applies. The “Keep Me Signed In” option is ignored since session timeouts are also governed by your SSO identity provider. If you have a wall TV setup or another account that needs to remain logged in longer than the timeout value, there are two options available to you:
- Use a Local Login account with a username and password and click “Keep Me Signed In” upon logging in.
- Enable the Restrict Single Sign On setting found under Settings | User Access | Single Sign On. The account will still be subject to any session timeouts enforced by the SSO IDP, but if that timeout is longer than the one configured here, the session should re-authenticate and renew with the SSO system upon the LogicMonitor timeout (although this behavior can’t be guaranteed within every environment).
Upload files for your account’s heading and login logos from this area of the Portal Settings tab.
- Update your payment information
- View the past 12 invoices for your LogicMonitor account