BMC Software Claimed Company
Transform your digital enterprise with BMC IT solutions. From mainframe to cloud to mobile, we'll help you drive... read more
EMPLOYEE
PARTICIPANTS
88
TOTAL
RATINGS
970
...

BMC Software FAQs

BMC Software's Frequently Asked Questions page is a central hub where its customers can always go to with their most common questions. These are the 186 most popular questions BMC Software receives.

Frequently Asked Questions About BMC Software

  • TrueSight Pulse subscriptions automatically renew at the end of each subscription period. Subscription periods may be either monthly or yearly.

    To cancel your subscription to TrueSight Pulse:

    Customer may terminate the Agreement by providing BMC with written notice at least 30 days prior to the beginning of the next Order term. Customer may notify BMC of its intent to terminate by emailing BMC at <a rel="noopener,nofollow" target="_blank" href="mailto:[email protected]">[email protected]</a>

    Please copy us at <a rel="noopener,nofollow" target="_blank" href="mailto:[email protected]">[email protected]</a> so that we can followup on your request.

    View Article
  • Display CPU and Memory usage for specific processes with this TrueSight Pulse Process plugin.

    Note

    This plugin replaces the Process Memory and Process CPU plugins.

    Prerequisites

    Supported OS: Linux, Windows, OS X

    TrueSight Pulse meter 4.5.0-778 or later

    To install new meter go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected

    cpu_process

    mem_process

    open_handles

    process_count

    Installing the plugin

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">BMC TrueSight Pulse console</a>.

    2) Go to Settings &gt; Plugins

    3) Click on 'Get Plugins'.

    4)Scroll to 'process' and click 'Install'.

    <a rel="noopener,nofollow" target="_blank" href="http://www.rexegg.com/regex-quickstart.html">Regex Cheat Sheet</a>

    5) Pulse provides a list of meters to associate to the plugin. Please select a meter. Now an "Add a plugin..." drop down box will display. Please click and select 'process':

    6)You will be prompted to "Add a Process".

    7) Type the required details, use the available tool-tips for help. Click 'OK'.

    Field Name

    Description

    Source

    The source name to display in the legend for the CPU &amp; Memory data.

    Process Name Regex

    The regular expression used to match the name of the process.

    Process Path Regex

    The regular expression used to match the path of the process.

    Process CWD Regex

    The regular expression to match the CWD (Current Working Directory) of the process.

    Process Args Regex

    The regular expression to match the arguments of the process.

    Polling Interval

    A numeric value representing the polling interval time in miliseconds.

    Reconcile option*

    The method used to determine the method used to reconcile processes when multiple processes match the specified regex parameters.

    *Select one of the following values for the Reconcile option.

    Reconcile option

    Description

    All Source Average

    Display a single source for each matching unique process name. It will show an average value of metrics along with count of processes for the source. This option is useful when focus is on the number of processes running or average utilization of particular processes.

    All Individual Source

    Display all unique sources (unlike average, even if multiple processes have the same process name, they are distinguished with index. For example, processname1 .. processnameN). This option is useful when individual process monitoring is crucial.

    Longest Running

    Display the single source that matches the process running for the longest period of time.

    First Match

    Display the first process that matches the regex parameter.

    Parent

    Display the parent processes that matching the regex parameters.

    8)The following dashboard will be created:

    Process

    Process Examples

    Here are a few examples of process configurations.

    #1 Process name 'arserver.exe' using Process Name Regex (arserver):

    #2 If the process is one of many JAVA processes running on the system you can useREGEX ARGS to define the configuration in order to capture data.

    For example, let's configure the plugin to capture a JAVA process we know is associated to "C:\Program Files\BMC Software\ARSystem\pluginsvr\fts\primary".

    We can find or confirm theJAVA process command line path by using the following PowerShell command:

    PS C:\Users\Administrator&gt; $process = "java.exe"

    Get-WmiObject Win32_Process -Filter "name = '$process'" | select Name,ProcessId,CommandLine | Format-Table -Property Name,ProcessId,Commandline -Wrap -AutoSize

    Using 'Process Args Regex' the configuration looks like this (.+primary):

    #3 Another JAVA example using Jenkins process and 'Process Args Regex'. The value in the Process Args Regex is ‘.+jenkins’:

    #4 If you decide to use the 'Process Path Regex' or 'Process CWD Regex', be sure to properly use regex conventions. For example, for the following path:

    C:\Program Files (x86)\Jenkins\jre\bin

    use 'Process Path Regex':

    C:\\Program\sFiles\s\(x86\)\\Jenkins\\jre\\bin

    References

    <a rel="noopener,nofollow" target="_blank" href="https://github.com/boundary/meter-plugin-process">Process plugin on GitHub</a>

    View Article
  • The Windows Performance Counter provides a framework whereby ad-hoc counter information can be collected.

    Prerequisites

    Supported OS: Window

    TrueSight Pulse meter 4.7.1-858 or later

    To install a new meter go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version, see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics collected

    Metric Name

    Description

    User Defined

    Dependent on user defined counter path

    <a rel="noopener,nofollow" target="_blank" href="https://github.com/boundary/meter-plugin-windows-performance-counter#available-windows-performance-counters"></a> Available Windows Performance counters

    Using the windows command prompt, type TypePerf.exe -q to see the available performance counters. Type TypePerf.exe -q &gt; counters.txt to send a list of all the counters to a text file.

    <a rel="noopener,nofollow" target="_blank" href="https://github.com/boundary/meter-plugin-windows-performance-counter#monitoring-multiple-counters"></a> Monitoring multiple counters

    We can monitor multiple counters by creating multiple instances of the plugin with each specifying one counter each. Once the meter detects the valid counters, they will be monitored and the metrics will be available in the metrics page. To view the metrics on a dashboard we may need to edit a dashboard and add the metrics to it.

    Note: If any of the counters specified is invalid, none of them will be shown.

    Installing the plugin

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">BMC TrueSight Pulse console</a>.

    2) Go to Settings &gt; Plugins.

    3) Click 'Get Plugins'.

    4)Scroll to 'WMI' and click 'Install'.

    5) Pulse will provide a list of meters to associate to the plugin. Select a meter.

    6) Select 'wmi' from the "Add a plugin..." drop down box and click 'Next'.

    7) Click 'Add a Windows Counter', type the required details and click 'OK'.

    Field Name

    Description

    Metric Name

    The name of the metric for the counter

    Counter

    The counter path for windows performance metric

    Factor

    The multiplication factor for the metric

    Poll Interval

    The collection interval in seconds

    7)The following dashboard will be created:

    WIN PDH

    References

    <a rel="noopener,nofollow" target="_blank" href="https://github.com/boundary/meter-plugin-windows-performance-counter">Windows Performance Counter plugin on GitHub</a>

    View Article
  • Introduction

    BMC TrueSight Pulse'sdirect integration to Amazon Web Services (AWS) collects and displays metricsfrom AWS CloudWatch. To get started you must have credentials that provide the proper privileges so thatTrueSight Pulse can extract and display metrics from the cloud services you deploy.

    The <a rel="noopener,nofollow" target="_blank" href="http://en.wikipedia.org/wiki/Principle_of_least_privilege">principle of least privilege</a> dictates that a user, process, or program must be able to access only the information and resources that are necessary. This article describes how to configure your AWS account using this principle, to generate the minimal access credentialsrequiredto integrate your AWS account withTrueSight Pulse.

    AWS provides Identity and Access Management (IAM) service, whichallows customers to manage user and permissions in AWS. If you are unfamiliar with this service, please visit <a rel="noopener,nofollow" target="_blank" href="http://aws.amazon.com/documentation/iam/">http://aws.amazon.com/documentation/iam/</a> for additional details. Instructions that follow assume that you have a basicunderstanding of IAM.

    Creating IAM Credentials for BMC TrueSight Pulse

    A pair of keys (Access Key ID and Secret Access Key) are required to provide access toBMC TrueSight Pulse to extract and display data from AWS CloudWatch. The steps that follow provide instructions on how to generate the required keys.

    Prerequisites

    Before getting started the following items are required:

    Existing AWS Account

    Required credentials to login to the AWS account.

    Sufficient privileges to modify the IAM service details.

    Overview

    The high-level steps required to complete the generation of the keys are as follows:

    Login - Gain accessto the AWS console with your credentials

    Create a User - Generatea new user, the keys will be associated with this user.

    Create a Group - Generatea group and associate a policy that grants the permissions to allowBMC TrueSight Pulse to extract and display metrics.

    Assign the User to the Group - Associates the group that has require permissions with the user that has the required keys.

    Login

    Sign in to the AWS Management Console and open the IAM console at <a rel="noopener,nofollow" target="_blank" href="https://console.aws.amazon.com/iam">https://console.aws.amazon.com/iam</a>.

    The IAM dashboard should be displayed.

    <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/115003538889">Integrating with AWS</a>

    Create a User

    This step will create atruesight user that will have the keys that are required.

    From the left hand menu bar select Users. The User editor will be displayed.

    Click on the Create New Users button

    In the first field of Enter User Names type: truesight

    Leave the checkboxGenerate an access key for each user selected.

    Click on the Create button.

    Click on the Download Credentials button to save the credentials (Access Key ID and Secret Access Key) to a file.

    Click close in the lower right corner.

    Create a Group

    This step will generate a new group and assign the required permissions to the group via a policy.

    From the left hand menu bar select Groups. The Group editor is displayed.

    Click the button Create New Group button.

    In the Group Name field type: Truesight.

    Click on the button Next Step in the lower right corner.

    Scroll down the list and check the box next to the item with a Policy Name ofCloudWatchReadOnlyAccess.

    Click on the button Next Step in the lower right corner.

    Click on the Create Group button which returns to the Groups editor.

    Assignthe User to theGroup

    Associates thetruesight user with theTruesight group, so that thetruesight user has the require permissions.

    Check box next to the line entry Truesight.

    Click on the Group Actions button which displays a drop down and select the Add Users to Group.

    Click the check box next to truesight.

    Click on the Add Users button in the lower right.

    Use Keysin PulseAWS Integration

    The Access Key ID and Secret Access Key are contained in the file downloaded from step 6 from Create a User. These keyscan now be used to configure theBMC TrueSight Pulse integration to AWS. For more information on configuring the integration, see .

    View Article
  • Overview

    The Truesight meter collects a set of core metrics that are, for the most part, common across a variety of OS flavors. These include metrics such as CPU, memory, disk and network utilization. Only a few, such as Processor Queue Length are MS Windows specific. Prior to the meter's counter collection feature, access to any of the thousands of other metrics were either via BMC provided plugins or customer written software. Though the plugins provide a tenable solution, they are still very much application specific, such as IIS, or MS SQL, and do not provide a general, non-application specific capability.

    The counter collection feature attempts to address a number of issues with the prior model and provide an extremely flexible approach in gaining access to any of the other performance counters. In addition to counter access, ease of use and deployment was another important consideration. The remainder of this documentation will provide all the necessary information to setup custom counter collection.

    Requirements

    The only requirement for using the performance counter collection feature is that the Truesight meter version must be 4.7.0 or greater. The officially supported platforms are Windows server 2008, 2012, or 2016.

    Quick Start

    For those with simple counter collection requirements, this section will provide the necessary information to quickly setup custom counter metrics. In this section, we will determine the counter(s) to be collected, modify the meter's counter configuration file, and add the new metric to the Pulse dashboard.

    Meter Counter Configuration File

    The meter parses a static counter configuration file in order to determine which, if any, counters are to be collected, and the metric names to which the counters are matched. The counter file is named - win_pdh.ini - and resides in the same location as the meter executable. The meter will monitor this file for changes, and update its counter specifications automatically. This means that when the file contents are modified, the meter will detect the changes and act appropriately without the need for restarting the service.

    For example, assume a user wishes to monitor the counter - "System Calls/sec" This counter is contained in the "System" object so the counter path would be "\System\System Calls/sec".

    See Appendix A for information on determining which counters are available and the path.

    Once the counter path is determined, the user needs to specify the metric name mapping for the Pulse back end. It is recommended that a consistent prefix be used for Windows counters in order to avoid name collision with other metrics, and facilitate finding the metrics in the UI. In this particular case, we will use PDH_SYSTEM_CALLS_SEC as our metric name. With this information, the user can modify the win_pdh.ini file and add the following section:

    [PDH_SYSTEM_CALLS_SEC]

    counter=\System\System Calls/sec

    Shortly after these changes are saved, the meter will begin collecting and sending the new counter data to the back end.

    Dashboard modification

    The user simply needs to add the metric to the dashboard at this point. In the UI, the user can select "Edit Dashboard" widget and find the new metric via the PDH prefix. Drag and drop the metric onto the desired slot in the dashboard and save the changes. <a rel="noopener,nofollow" target="_blank" href="https://msdn.microsoft.com/en-us/library/windows/desktop/aa373046(v=vs.85).aspx+">https://msdn.microsoft.com/en-us/library/windows/desktop/aa373046(v=vs.85).aspx+</a> Once the dashboard is saved, the new metric will be visible in the graph. Any additional counters can be added in a similar fashion by editing the win_pdh.ini file and appending the definitions in the manner described above. If the user is running multiple meters on multiple hosts, this file can be pushed to the remote machines and the meter will begin reporting the metrics for those hosts.

    For information on additional configuration options in the win_pdh.ini file, refer to Appendix B.

    Performance Counter Plugin

    Plugins may generate a win_pdh.ini file in their local directory which allows plugins to leverage the meters collection ability. If the meter detects a win_pdh.ini file in the plugin directory, and the plugin is currently enabled, the meter will begin collecting any counters specified in the file. BMC provides a general use performance counter plugin whereby a user can enter the counters to be collected in the UI. The required fields are the same as outlined in the Quick Start section above.

    In following section, we will create the same counter metric as in the prior section. In this instance, we will be using the plugin rather than modifying the meters counter file. Note that the meter will continue to collect any metrics specified in its local counter file. It is assumed that the user is familiar with the plugin installation process.

    Create the counter metric via the plugin UI

    Select a meter which has the plugin installed. In the plugin configuration screen, select "Add a Windows Counter". The metric name will be PDH_SYSTEM_CALLS_SEC and the counter path is \System\System Calls/sec. Save the plugin configuration changes, and within a few seconds the new metric will be collected. Any number of performance counters may be collected via the plugin. The metric may need to be added to the Dashboard to become visible. See the Quick Start Guide for the appropriate steps.

    Advanced Counter Paths

    In the previous examples, the counter we pulled was a single instance and provided a single metric value. The following sections will address two additional topics; parent instances, and the wildcard character.

    Parent Instances in Counters

    Some services, such as MS SQL, can run multiple instances. In order to pull the correct counter data, the instance needs to be specified in the path. This section will demonstrate pulling these types of counters from a MS SQL instance.

    In this example, we will look at pulling the "Latches\Average Latch Wait Time (ms)" counter from MS SQL. Our parent instance name is 'MSSQL$SQLEXPRESS', giving the complete counter path of:

    'MSSQL$SQLEXPRESS:Latches\Average Latch Wait Time (ms)' In the case of multi-instance service deployment, the meter supports specifying a list of instance names and will generate the multiple counter paths for a single metric. This removes the need for the user to specify individual metric/counter definitions for each instance. This behavior is controlled by the "instances=" variable in the win_pdh.ini file. By way of example, let's assume we have three MSSQL instances - SQL_PROD, SQL_STAGING and SQL_DEV.

    Our metric specification could be set up thusly:

    [PDH_LATCH_WAIT_TIME]

    instances=SQL_PROD, SQL_STAGING, SQL_DEV

    counter=Latches\Average Latch Wait Time (ms)

    The meter will create and collect the counters:

    SQL_PROD:Latches\Average Latch Wait Time (ms)

    SQL_STAGING:Latches\Average Latch Wait Time (ms)

    SQL_DEV:Latches\Average Latch Wait Time (ms) Since we now have three potentially different values for our single metric - PDH_LATCH_WAIT_TIME - the meter will append the instance name to the source in order to differentiate the values. From this example, the user would see the following sources graphed (assuming a hostname of "win-server")

    win-server.SQL_PROD

    win-server.SQL_STAGING

    win-server.SQL_DEV

    This mimics the existing behavior of the BMC provided MSSQL plugin.

    Wildcards in Counters

    Many of the Windows performance counters resolve to an array of services or instances. For example, Windows provides a global counter for threads in the path \System\Threads. It always provides a counter on a per-process basis. The total value as a single metric is normally collected using the (total) specification. Eg: _\Process(_total)\Thread Count

    It is possible to retrieve the values for each process in a single counter. The following would return an array of values for each running process - \Process(*)\Thread Count

    The meter supports using a wildcard character and processing an array of responses. Since each counter element maps to the same metric name, the meter will differentiate the values by appending the instance name to the source. The following image illustrates specifying the collection of all processes thread counts via the wildcarded counter path.

    Given the volume of sources created, this is not a recommended scenario but serves to illustrate the functionality.

    Appendix A

    Exploring available performance counters

    Windows provides a tool which will dump all the currently available counters - TypePerf.exe One quick method to dump all the counters to a file would be using the following command in a PowerShell TypePerf.exe -q &gt; counters.txt For complete details on using TypePerf and the various options, view the MS technical article at : <a rel="noopener,nofollow" target="_blank" href="https://technet.microsoft.com/en-us/library/bb490960.aspx">{+}</a> <a rel="noopener,nofollow" target="_blank" href="https://technet.microsoft.com/en-us/library/bb490960.aspx+">https://technet.microsoft.com/en-us/library/bb490960.aspx+</a>

    Appendix B

    Meter Counter Template

    The meter uses a simple .ini type file to specify the counters for collection. Upon startup, if the file it not present, the meter will create a template file. The only required fields for counter definitions are the 'metric name' as the section header, and the counter path. Below is a description of each section element and purpose.

    Global Section

    version

    This is the version of the file format specification. It is currently unused.

    Counter Section

    [METRIC_NAME] *Required

    This is the section header for each counter to be collected. The section name is the name of the metric that will be pushed to the back end. It is recommend that the metric names for the performance counters be prefixed for easy location in the metrics UI. eg: PDH_THREAD_COUNT

    counter *Required

    The full path to the desired counter. See Appendix A for determining which counters are available and the path. The specified path should contain the leading '\' character. For example: \System\Threads. A path may also specify a wildcard character.eg: \Process(*)\Thread Count

    instance_name

    This field is an optional, comma delimited list of instance names. This is useful in the case of services such as MSSQL that allow multi-instance setups. If present, a counter will be created for each instance_name listed.

    eg: instance_name=a,b counter=\object\counter - the following counters would be generated:

    \a:object\counter

    \b:object\counter

    push

    This is a boolean variable set to "true" or "false". If "true", the meter will push the counter metric to the back end. If "false", the meter will retain the value for querying by plugins, but will not send the values to the back end directly. This is useful for plugins that may wish to generate alarms on values, or created aggregated metrics. The default value is "true"

    factor

    This is a multiplier value that will be applied to the counter value. The default value is 1.0

    interval_sec

    This is the counter collection time in seconds. Due to the method Windows uses to compute certain counters with history requirements (such as the "per second" counters), the lower limit for this value can be no faster than 2 seconds.

    include_tags

    A comma delimited list of meter tags. If present, the specified counter will only be collected by meters with tags matching one of the specified tags.

    exclude_tags

    A comma delimited list of meter tags. If present, the specified counter not be collected by meters with tags matching one of the specified tags. {}Note{*}: In the event that a meter matches both include and exclude tags, the exclude tag will take precedence. A warning message will be emitted by the meter in this case.

    Appendix C

    Debugging Counters

    get-counter

    get-counter is a standard Windows tool available in the PowerShell. It can be very useful for determining if the correct paths are being specified and which instances are available when using the wildcard specification.

    For more information on usage, "help get-counter" in a PowerShell will provide the available options.

    truesight-meter

    The meter itself has an option build in to allow testing of ini specification files. When invoked with the --verify-pdh option, the meter will parse the ini file, and make one pass of counter collection. This can be useful for validation files before deployment.

    eg: truesight-meter.exe --verify-pdh win_pdh.ini Meter status page

    The meter status page ( <a rel="noopener,nofollow" target="_blank" href="http://127.0.0.1:9193/info">{+}</a> <a rel="noopener,nofollow" target="_blank" href="http://127.0.0.1:9193/info+">http://127.0.0.1:9193/info+</a> ) contains a section related to performance counters. A status of 0 indicates successful collection, while any other value denotes an issue. The status code is mapped to a PDH error response. Status codes can be found at <a rel="noopener,nofollow" target="_blank" href="https://msdn.microsoft.com/en-us/library/windows/desktop/aa373046(v=vs.85).aspx">{+}</a> meter.conf debug flag

    The meter.conf file has a debug flag specifically for performance counters. To enable debug, modify the win_per_counters.debug section and set the value to 'true'. The meter will provide much more information on the counter collection loop.

    View Article
  • TrueSight Pulse works best on the latest versions of ChromeorFirefox running on WindowsormacOS.Pulse may operate on other browsers such as Safari orInternet Explorer, but completefunctionality is not guaranteed nor tested.

    We make everyattempt to provide the best support possible forolder versions of Chrome and Firefox, but depending on the issue, upgrading to the latest version of the browser may be required.

    Looking for browser options for TrueSight Intelligence? Please look here: <a rel="noopener,nofollow" target="_blank" href="https://docs.bmc.com/docs/display/bti10/Supported+platforms">TrueSight Intelligence Browser Support</a>

    View Article
  • Meter 4.7.0-852

    Meter 4.7.0-852 Released to production on 8/14/2017.

    Official Release Notes forVersion 4.7.0

    Native support for Windows performance counters

    The meter now provides a convenient collection method for any of the available Windows performance counters. A simple .ini specification file is all that is required toimmediately begin collecting any of the native or application specific data. A sample template file is created on meter startup, which provides the necessary informationto get started.

    Enhanced metrics logging

    To further assist in debugging issues with core and plugin metrics, the meter now supports a command line option which allows the logging of all posted metrics to a local file. Previous versions of the meter had a similar capability but it was mixed with a variety of other log data, making traversing the information difficult.

    The data will now go the specified log file, and only contain the information relevant to metrics in a readable/parse-able format. The option is invoked on the command line as such - "--metrics-logfile &lt;filename&gt;"

    Increased event size for title and message fields

    The meter supports ingesting events and pushing them to the back end. These can come from a variety of sources, such as plugins, customer scripts, custom plugins, etc. Previous versions of the meter restricted the title and message fields to 255 bytes each. This limit has been increased to 8k each.

    Event Proxy RPC responses

    The event RPC proxy now supports returning the status and JSON response from the back end API call. This allows clients using the interface to track thesuccess/failure or partial success status of each event that was proxied through the meter.

    View Article
  • This video will walk you through the installation and configuration of the BMC TrueSight plugin for MS SQL Server.

    View Article
  • As you continue to extend your monitoring with TrueSight Pulseyou will build up a large list of sources.

    While the dashboards will automatically limit the displayed sources based on the metrics, you may need to search for one or two specific sources, or group them together in ways that make sense to you. For that we have the sources list on the left of all your dashboards and a search syntax to make it easy to find them.

    <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201728561-Legend-Bar-How-To">Legend Bar.</a>

    The list populates automatically with all sources you have registered (from meters, plugins, or integrations). Some integrations also automatically add Saved Filters, for example AWS integration has created regional filters for all the AWS services in the above screenshot.

    When you first open the sources drop down the sources currently active in the legend bar will be selected. You can use this drop down to change which sources are displayed in the Legend Bar.

    Searching

    Byentering a stringin the search box TrueSight Pulsewill instantly search and limit the sources and filters displayed.

    The source search is powered by asimple query syntax which is described in detail <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/articles/115003520529-Source-Query-Language">here</a>. You can perform straight forward searches like "starting with" as well asverycomplex patterns.

    Filters - Pre-Defining re-usable Searches

    In Settings &gt; Filters select

    The Filter dialog provide a Query box that can dynamically search sources to create new filters.

    Typing 'clm' in the query box will automatically list all sources with that phrase in the name.The query syntax isdescribed in detail <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/articles/115003520529-Source-Query-Language">here</a>.

    Once saved your filter will appear in the filters list and be available to everyone that uses your account.

    Adding New Sources to existing Filter

    Filter and source management is simplified when adding new hosts because TrueSight Pulse will automatically add new sources thatmatch a Filter's Query configuration.

    For example, using the "CLM Servers" filter example above, any new sources with 'clm' in the name will automatically be associated to that filter.

    Editing/Deleting Filters

    Filters can be deleted or manually edited by opening the Settings menu, choosingFiltersin the left hand section, choosing your filter and clicking delete to remove the filter.

    Pinning a Filter

    When you save a filter you have the option to Pin it to a dashboard. This means that the filter will be automatically selected whenever you visit this dashboard. To pin or unpin a dashboard you can use the pin icon next to the sources box (note that this icon only appears when a saved filter is currently in use)

    Note that the Sources box only controls which sources are displayed in the legend. You can further control what is shown on the graphs by using the

    View Article
  • NOTE

    On October 11, 2016, BMC released <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/articles/212732505-Version-4-4-1">Meter Version 4.4.1</a> which changed the name of the meter from boundary-meter to truesight-meter. This article reflects the change. If you are using a meter version prior to 4.4.1, then you will need to reference boundary-meter instead of truesight-meter in the operations discussed in this article.

    Supported Installer Variables

    All BMC TrueSight Pulse meter installer packages and scripts can modify their default behavior by setting various environment variables. These settings work the same whether one installs the meter package usinga native package manager such as rpm, apt, yum, zypper, pkg_add, msiexec, or using the setup_meter.sh script. Supported installation variables are:

    INSTALLTOKEN: use to allow the installer to automatically provision itself with BMC TrueSight Pulse. The meter will additionally save a copy of the token in a private config file that can be used later for interacting with other Pulse services.

    METERPRODUCTDIR: (windows only) use when an alternative installation directory is required. This takes the place of the traditional msiexec INSTALLDIR.

    PROVISIONHOSTNAME: allows the user to provision the host with a different name than the default host name. Useful for distinguishing several machines with the same name.

    PROVISIONTAGS: allows the user to tag meters directly as part of the installation process, ex PROVISIONTAGS=webserver,internal,pulse

    PROVISIONDOMAIN: if not set, defaults to 'truesight.bmc.com', specify another value to provision in a private SaaS environment

    PROVISIONFEATURES: if not set, defaults to 'flow_metrics', specify a comma-separated list of the words 'server_metrics', 'flow_metrics' to specify particular features to enable with this meter.

    TLSSKIPVALIDATION: enable debugging SSL connectivity in a test environment

    COLLECTORPORT: override the default collector ports of 4740 and 443. You can either specify a single port, or a set of comma separated ports to try, e.g. COLLECTORPORT=4740,443

    DISABLENTP: disables the built-in NTP client. In meters 2.0.x and earlier, the NTP client is enabled by default. In meters 3.0.0 and later, the NTP client is disabled in favor of in-band time synchronization, so this option has no effect. (2.0.3 and later)

    ENABLESTUN: enables the built-in STUN client support. If this is enabled, the meter will use the STUN protocol to discover public IP addresses for each internal interface with a private address. (2.0.3 and later)

    HTTPS_PROXY: Specify a HTTPS-capable proxy to use when accessing the APIs to provision the meter. This supports the same syntax as the CURL utility, e.g. HTTPS_PROXY=proxy-server:8888 (3.0.0 and later)

    Examples with various package installation methods

    setup_meter.sh

    sudo PROVISIONHOSTNAME=host \

    PROVISIONTAGS=server,blue \

    HTTPS_PROXY=localproxy:8888 \

    ENABLESTUN=1 \

    ./setup_meter.sh -i api.0123456789-0123

    rpm

    sudo PROVISIONHOSTNAME=host \

    PROVISIONTAGS=server,blue \

    HTTPS_PROXY=localproxy:8888 \

    ENABLESTUN=1 \

    INSTALLTOKEN=api.0123456789-0123 \

    rpm -i truesight-meter-*.rpm

    dpkg

    sudo PROVISIONHOSTNAME=host \

    PROVISIONTAGS=server,blue \

    HTTPS_PROXY=localproxy:8888 \

    ENABLESTUN=1 \

    INSTALLTOKEN=api.0123456789-0123 \

    dpkg -i truesight-meter-*.dpkg

    Windows (Silent Install)

    msiexec /l*v truesight-meter.log /qn /i truesight-meter-current.msi INSTALLTOKEN=api.0123456789-0123 PROVISIONHOSTNAME=host PROVISIONTAGS=server,blue HTTPS_PROXY=localproxy:8888 ENABLESTUN=1

    View Article
  • For instructions on setting up an AWS IAM account for the integration, please refer to the KB article posted <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201851731-Creating-Credentials-for-AWS-Integration">here</a>.

    View Article
  • Baseline Alarms trigger when the data value for a selected metric, and optionally the selected source deviates from the baseline for the duration of the configured period. Baselines are computed using hourly and daily time periods based on the metric measure time interval.

    Configuring a Baseline Alarm

    Click on the Alarm icon in menu pane or select the Settings -&gt; Alarm menu items from the Settings menu to display the Alarm configuration dialog.

    Click on the green button in lower right of the dialog labeled Add Alarm and then an Alarm configuration dialog will be displayed.

    Identifythe alarm by entering text into the Name field.

    From the Alarm ondrop down menu select the Baseline menu item.

    From the API Metric drop down menu select the desired Metric to trigger upon if there is a deviation from the baseline.

    Select the desired source from the Source Filter drop down menu.

    From the Threshold drop down menu select the condition that should be violated for triggering an alarm.

    From the Period drop down menu select the desired period for which the deviation from the baseline should persist before triggering an alarm.

    From the Actions drop down menu select the desired action to fire if this alarm is triggered.

    In the Note field add any supplementary text to be associated with the alarm.

    View Article
  • Introduction

    The great thing about working on TrueSight Pulse is that we get to build tools that we want to use ourselves, everyday. Being developers for many years we've been exposed to plenty of alarming / alerting tools. In fact, alarming is usually the second thing we set up after our servers are created. We can't watch our server monitors constantly so getting told when things are suspect is vital.

    The usual suspects of alarming haven't really changed over the years. At the application layer the alarms will typically test for slow or missing responses from a web request. At the system level, there are basic resource threshold checks. One of the biggest issues that surrounds alarming techniques is the ability to produce valid alarms. The basic problem is that, as we all know, systems fluctuate throughout the day, mostly for known reasons which might cause alarms which are superfluous. You then must dig through the notifications that are generated in order to find the real problems. There are various ideas around 'flapping detection', application scoring, and other somewhat arcane techniques so we thought "why not use our existing analytic engine behind TrueSight Pulse to make a better alarming solution?"

    TrueSight Pulse Alarms are able to be triggered when a measurement value exceeds a threshold, or when communication ceases between a meter or a measurement is not longer being sent.

    Here is a video that covers alarms and actions as well:

    <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201130392-Tip-Alarms-and-Actions">TrueSight Pulse - Alarms and Actions</a>

    Setup

    Firstly, you can add alarms quickly and easily from the Alarms tab in the settings dialog.

    <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201856042-Filtering-Searching-Sources-How-To">Filtering &amp; Searching Sources - How To</a>

    On the Alarms tab we can see our existing alarms and click to add a new one:

    Next we see the alarm settings:

    We tried to make alarms as easy as possible to set up.

    First you give the alarm a name. This is a simple, short, title that you can create so you can quickly get an idea of what the issue is when you see the alarm.

    For a threshold alarm we select Threshold from the drop down menu. A threshold alarm indicates that we want the alarm to trigger.

    See <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/207144749">How To Configure Communication Alarms</a> for step by step instructions on configuring threshold alarms.

    See <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/115004096609">How to Configure Baseline Alarms</a> for step by step instructions on configuring baseline alarms.

    Next is the metric. This is can be any one of those listed in the drop down menu.

    These settings are typical with what you've seen elsewhere but now we get to a feature that is a little different; threshold.

    What sets apart TrueSight Pulse alarms is that we can not only alarm basic aggregates like min, max, count but we can also alarm for an average. The aggregates work in conjunction with the time period:

    The time period can range from 1 second up to 1 hour. For example, if I set a CPU threshold of, say, avg &gt; 80\% and a period of 1 minute then this translates to:

    "Tell me when my CPU average is above 80\% for at least 1 minute"

    In practice, this technique for detecting actually bad states has been most effective for us at BMC.

    After setting the threshold and period you can set an associated Action that runs when the alarm threshold is exceeded. See <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/202359171-Action-Send-Notification-by-Email">Action Send Notification by Email</a> for instructions for configuring an email Action. For complete discussion on Actions see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/207854165">TrueSight Pulse Actions</a>.

    The Note will be passed along at the time the alarm notification is sent.

    You can choose which servers you wish to alarm by selecting a filter from the drop down menu (See for additional details on creating and using filters). By default you can simply alarm for All Sources. This setting works in conjunction with the Notify for every change feature.

    To illustrate how these settings work let's take a simple of example of monitoring 3 servers, A, B, and C at a 1 minute period. Consider the following scenario:

    1:00pm - Alarm A triggered

    1:01pm - Alarms B and C triggered

    1:02pm - Alarms A and B resolved

    1:03pm - Alarm C resolved

    By default, without the 'notify for every change' option you would receive just two notifications:

    ALARM at 1:00pm because at least on of your server alarms triggered

    RESOLVED at 1:03pm when all of your server alarms were no longer triggered

    However, if you enable 'notify for every change' you would receive four notifications as follows:

    ALARM at 1:00pm because at least on of your server alarms triggered

    ALARM UPDATE at 1:01pm stating that B and C are now triggered, A continues

    ALARM UPDATE at 1:02pm stating that A and B are resolved, C continues

    RESOLVED at 1:03pm when all of your server alarms were no longer triggered

    Speaking of notifications, here's what a typical notification mail looks like:

    Notice that you are told exactly which alarms are triggered (or resolved as the case may be), why they are triggered, and a link to the dashboard at the point in time of the trigger.

    When you go to your dash you will now see some differences. The first thing you'll notice is that the graph representing the metric that has triggered the alarm now has a flashing red border:

    The next thing you'll notice is a red bell icon in the graph title bar. We can click this to see what has triggered:

    You can now click on the triggered alarm to go directly to the point in time of the trigger.

    That is the short and sweet approach to TrueSight Pulse alarms. We hope these alarms are as useful and pertinent to your business as it has been to ours.

    View Article
  • Follow the steps given below to integrate with Amazon Web Services:

    Click Settings &gt; Integrations

    Click Add New

    Click AWS

    Enter the required details. For more information on the values, see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201851731">Creating Credentials for AWS Integration</a>.

    Click Test Connection to test the connection with the AWS instance.

    Click Submit to save the integration.

    AWS Services

    The following AWS services are supported. For more information on the supported metrics for each service, see <a rel="noopener,nofollow" target="_blank" href="http://truesightpulse.bmc.com/integrations/aws-monitoring/">http://truesightpulse.bmc.com/integrations/aws-monitoring</a>.

    AWS APIGateway

    AWS ElastiCache

    AWS Redshift

    AWS AutoScaling

    AWS ElasticLoadBalancing

    AWS S3

    AWS Billing

    AWS EMR

    AWS SNS

    AWS CloudFront

    AWS Kinesis

    AWS SQS

    AWS dynamoDB

    AWS Lambda

    AWS Storage Gateway

    AWS EBS

    AWS ML

    AWS SWF

    AWS EC2

    AWS OpsWorks

    AWS WorkSpace

    AWS EC2 spot instance

    AWS RD

    Support for these services was added on June 30 2017

    AWS Regions

    The following AWS regions are supported.

    AP_NORTHEAST_1

    EU_WEST_1

    AP_NORTHEAST_2

    EU_WEST_2

    AP_SOUTH_1

    GovCloud

    AP_SOUTHEAST_1

    SA_EAST_1

    AP_SOUTHEAST_2

    US_EAST_1

    CA_CENTRAL_1

    US_EAST_2

    CN_NORTH_1

    US_WEST_1

    EU_CENTRAL_1

    US_WEST_2

    Support for these regions was added on June 30 2017

    View Article
  • NOTE

    On October 11, 2016, BMC released <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/articles/212732505-Version-4-4-1">Meter Version 4.4.1</a> which changed the name of the meter from boundary-meter to truesight-meter. This article reflects the change. If you are using a meter version prior to 4.4.1, then you will need to reference boundary-meter instead of truesight-meter in the operations discussed in this article.

    Uninstalling

    The meter can be uninstalled by running the appropriate package commands:

    CentOS, RedHat, ...

    sudo yum remove truesight-meter

    Ubuntu, Debian, ...

    sudo apt-get purge truesight-meter

    Note: TrueSight PulseMeter directory is /etc/truesight, which also contains configuration files and plugins. In some cases it is not removed, you can safely remove it manually after uninstalling the meter.

    View Article
  • Userssometimes experience issues uploading private plugins to the BMC TrueSight Pulse service. Below are some commonly used tips for troubleshooting this:

    Check your username/token in the upload: The basic curl command for uploading repositories in the documentation is:

    $ curl https://api.graphdat.com/v1/plugins/private/&lt;your plugin name&gt;/&lt;your github username&gt;/&lt;repo name&gt;

    -X PUT

    -u &lt;your email&gt;:&lt;your API key&gt;

    Get your API Token by click settings -&gt; Account and taking the API Token for your account. The username is the email address next to "owner" at the top of this screen.

    Confirm the address of your GitHub repository: The Curl upload path is:

    https://api.graphdat.com/v1/plugins/private/&lt;Your Plugin Name&gt;/&lt;your github username&gt;/&lt;GitHub repository name&gt;

    The plugin name can be anything you want and is set at this point.

    The easiest way to get the github section is to visit the github page for your repository and copy the end of the URL or the title of the page to ensure there are no errors.

    Check your JSON:A common cause of upload errors is invalid JSON in the plugin config file. You can pre validate your JSON by using an online service such as <a rel="noopener,nofollow" target="_blank" href="http://jsonlint.com/">JSONLint</a>.

    If you don't see a JSON response: If the upload works you should see a JSON command showing 200, success. Occasionally the upload may take a while and you will see a HTML response. This is most likely a timeout with the Boundary service which shouldn't happen, so please let us know if you see this. However usually a retry will succeed.

    Put your code on the master branch: When we load a new repo for private plugins, we pull the master branch, without it, we don't know which branch to use.

    $ git checkout -b master

    $ git push -u origin master

    Other errors: Generally if the upload path is correct you will receive a JSON formatted message with either success or an error. The error should give you some clues towards the problem, but if you do hit issues raise a ticket using the link on the right and we'll be pleased to help.

    View Article
  • This meter plugin collects metrics from the ActiveMQ node using the embedded <a rel="noopener,nofollow" target="_blank" href="https://jolokia.org/">Jolokia</a> instance that allows measurement collection via a REST API. There is a <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/115003777645-Plugins-Apache-ActiveMQ-Plugin-Walkthrough">video walkthrough of deployment here</a>.

    Prerequisites

    Supported OS: Linux, Windows, OS X

    TrueSight Pulse meter 4.5.0-778 or later

    ActiveMQ version 5.10.0 or later

    To install a new meter, go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version, see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected:

    ACTIVEMQ_BROKER_TOTALS_QUEUES

    ACTIVEMQ_BROKER_TOTALS_TOPICS

    ACTIVEMQ_BROKER_TOTALS_PRODUCERS

    ACTIVEMQ_BROKER_TOTALS_CONSUMERS

    ACTIVEMQ_BROKER_TOTALS_MESSAGES

    ACTIVEMQ_BROKER_STATS_ENQUEUE

    ACTIVEMQ_BROKER_STATS_DEQUEUE

    ACTIVEMQ_BROKER_STATS_INFLIGHT

    ACTIVEMQ_MESSAGE_STATS_DISPATCH

    ACTIVEMQ_MESSAGE_STATS_EXPIRED

    ACTIVEMQ_MESSAGE_STATS_QUEUE_SIZE

    ACTIVEMQ_MEM_USED

    ACTIVEMQ_STORE_USED

    Installing the plugin

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">BMC TrueSight Pulse console</a>.

    2) Go to Settings &gt; Plugins.

    3) Click 'Get Plugins'.

    4)Scroll to 'ActiveMQ' and click 'Install'.

    5) Pulse provides a list of meters to associate to the plugin. Select a meter. An "Add a plugin..." drop down box will display.

    Field Name

    Description

    pollInterval

    Frequency at which the metrics are gathered from ActiveMQ

    host

    The server from which ActiveMQ statistics should be gathered

    broker_name

    The name of the ActiveMQ broker that should be monitored

    port

    The port on which ActiveMQ metrics can be retrieved

    username

    The administrative user who can gather ActiveMQ metrics

    password

    The password for the administrative user

    sourceName

    The source name to be displayed for each metric

    6) Type the required details. Use the available tool-tips for help. Click 'OK'.

    7)The following dashboard will be created:

    ActiveMQ Summary

    References

    <a rel="noopener,nofollow" target="_blank" href="https://github.com/boundary/meter-plugin-activemq">ActiveMQ plugin on GitHub</a>

    View Article
  • Monitor, visualize and alert on your Apache Stormenvironment in one-second intervals with this TrueSight Pulse Apache StormAPI plugin. There is a <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/209734049-Apache-Storm-Plugin">video walkthrough of deployment here</a>.

    Prerequisites

    Supported OS: Linux

    Apache Storm0.9.3or later

    TrueSight Pulse meter 4.5.0-778 or later

    To install new meter go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected:

    STORM_BOLT_ACKED

    STORM_BOLT_CAPACITY

    STORM_BOLT_EMITTED

    STORM_BOLT_EXECUTELATENCY

    STORM_BOLT_EXECUTORS

    STORM_BOLT_FAILED

    STORM_BOLT_LASTERROR

    STORM_BOLT_PROCESSLATENCY

    STORM_BOLT_TASKS

    STORM_CLUSTER_EXECUTORS

    STORM_CLUSTER_SLOTS_TOTAL

    STORM_CLUSTER_SLOTS_USED

    STORM_CLUSTER_TASKS_TOTAL

    STORM_CLUSTER_TOPOLOGIES

    STORM_SPOUT_ACKED

    STORM_SPOUT_COMPLETELATENCY

    STORM_SPOUT_EMITTED

    STORM_SPOUT_EXECUTORS

    STORM_SPOUT_FAILED

    STORM_SPOUT_LASTERROR

    STORM_SPOUT_TASKS

    STORM_CLUSTER_SUPERVISORS

    STORM_TOPOLOGY_TASKS_TOTAL

    STORM_TOPOLOGY_WORKERS_TOTAL

    STORM_TOPOLOGY_EXECUTORS_TOTAL

    How To Install Apache StormPlugin

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">BMC TrueSight Pulse console</a>.

    2) Go to Settings &gt; Plugins

    <a rel="noopener,nofollow" target="_blank" href="http://storm.apache.org/">Apache StormDocumentation</a>

    3) Click on 'Get Plugins'.

    4)Scroll to 'storm' and click 'Install'.

    5) Next, Pulse will provide a list of meters to associate to the plugin. Please select a meter. Now an "Add a plugin..." drop down box will display. Please click and select 'storm':

    6)You will be prompted to "Add an Instance":

    7) You can select default settings or update per your configuration. The "Source" value is the name to display in the legend for the metrics data. It will default to the hostname of the server. Click "OK".

    8) Sample screen after clicking "OK":

    9) Click "Save". The following console output will appear:

    10) The following dashboards will be created:

    Storm General

    Storm Bolts

    Storm Spouts

    11)Sample Apache Storm Bolts dashboard output:

    References

    View Article
  • This video will walk you through the installation and configuration of the BMC TrueSight plugin for Apache ActiveMQ.

    View Article
  • This video will walk you through the installation and configuration of the BMC TrueSight plugin for Apache Storm.

    View Article
  • Monitor, visualize and alert on your Apache Tomcat web server in one-second intervals with this TrueSight Pulse Apache TomcatAPI plugin.

    You may also refer to this <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/115000947209">video</a> for a recorded walk through of the install and configuration process.

    Prerequisites

    Supported OS: Linux, Windows, OS X

    TrueSight Pulse meter 4.2 or later

    To install new meter go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected:

    TOMCAT_JVM_FREE_MEMORY

    TOMCAT_JVM_TOTAL_MEMORY

    TOMCAT_HTTP_CURRENT_THREAD_COUNT

    TOMCAT_HTTP_CURRENT_THREAD_BUSY

    TOMCAT_HTTP_MAX_PROCESSING_TIME

    TOMCAT_HTTP_REQUEST_COUNT

    TOMCAT_HTTP_ERROR_COUNT

    TOMCAT_HTTP_BYTES_SENT

    TOMCAT_HTTP_BYTES_RECEIVED

    TOMCAT_MEMPOOL_HEAP_EDEN_SPACE

    TOMCAT_MEMPOOL_HEAP_OLD/TENURED_GEN

    TOMCAT_MEMPOOL_HEAP_SURVIVOR_SPACE

    TOMCAT_MEMPOOL_NONHEAP_PERM_GEN

    TOMCAT_MEMPOOL_NONHEAP_METASPACE

    TOMCAT_MEMPOOL_NONHEAP_CODE_CACHE

    How To Install Apache TomcatPlugin

    Plugin Setup

    In order for the plugin to collect statistics from Tomcat you need to:

    A) Configure JMX endpoint for Tomcat installed.

    On Windows (if Tomcat is running as service):

    Enable Apache Service Manager (commons daemon service manager) for the installed service using the command: tomcat7w.exe

    This should start Apache Service Monitor program on your system tray. Click on its icon. Select on the 'Java' tab and append the following on the 'Java Options' text box, one option per line (note -assuming JMX endpoint as 8999 of your localhost):

    -Dcom.sun.management.jmxremote.port=8999

    -Dcom.sun.management.jmxremote.authenticate=false

    -Dcom.sun.management.jmxremote.ssl=false

    <a rel="noopener,nofollow" target="_blank" href="http://tomcat.apache.org/tomcat-7.0-doc/">Apache TomcatDocumentation</a>

    B) Set the CATALINA_OPTS environment variable

    On Windows:

    set CATALINA_OPTS="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=8999

    -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false

    -Djava.rmi.server.hostname=localhost"

    On Linux &amp; OS X:

    $ CATALINA_OPTS="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=8999

    -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false

    -Djava.rmi.server.hostname=localhost"

    $ export CATALINA_OPTS

    NB: To set the above mentioned environment variable, you can create setenv.bat or setenv.sh, depending on your OS, inside CATALINA_HOME/bin and restart the tomcat. If you are monitoring a remote tomcat instance, in that case, you need to set

    On Windows: -Djava.rmi.server.hostname=hostname

    On Linux &amp; OS X: -Djava.rmi.server.hostname=$HOSTNAME

    If you have set credentials for JMX Port, in that case you have to set

    -Dcom.sun.management.jmxremote.authenticate=true

    -Dcom.sun.management.jmxremote.password.file=$JAVA_HOME/jre/lib/management/jmxremote.password

    -Dcom.sun.management.jmxremote.access.file=$JAVA_HOME/jre/lib/management/jmxremote.access

    Once steps A and B have completed you can now install the plugin.

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">BMC TrueSight Pulse console</a>.

    2) Go to Settings &gt; Plugins

    3) Click on 'Get Plugins'.

    4)Scroll to 'tomcat' and click 'Install'.

    5) Next, Pulse will provide a list of meters to associate to the plugin. Please select a meter. Now an "Add a plugin..." drop down box will display. Please click and select 'tomcat':

    6)You will be prompted to "Add an Instance".

    7) You can select default settings or update per your configuration. The "Source" value is the name to display in the legend for the metrics data. It will default to the hostname of the server. Click "OK".

    8)The following dashboards will be created:

    Tomcat HTTP Service

    Tomcat Memory Pool

    9)Sample Tomcat HTTP Serviceoutput:

    References

    View Article
  • Below is the list of currently supported operating systems. If you don't see your OS or version of choice, please email us at <a rel="noopener,nofollow" target="_blank" href="mailto:[email protected]?subject=OS\%20Support\%20Request\%20201223531">[email protected]</a>

    Alpine - 3.2 and later- 64-bit (x86_64)

    Amazon Linux AMI - All Versions - 32-bit and 64-bit

    ArchLinux - Kernel Version 464-bit (x86_64)

    CentOS - 6.x-7.x - 32-bit (x86) and 64-bit (x86_64)

    CloudLinux - 5.x-7.x - 32-bit (x86) and 64-bit (x86_64)

    Debian - 7.x-8.x - 32-bit (x86, armel, armhf) and 64-bit (x86_64)

    Fedora Linux 14 - 32-bit (x86) and 64-bit (x86_64)

    FreeBSD - 10.x-11.x- 64-bit (amd64)

    Linux Mint - 13-17 - 32-bit (x86) and 64-bit (x86_64)

    Mac OS X - 10.8-10.10- 64-bit (x86_64)

    openSUSE - 13.2- 64-bit (x86_64)

    Oracle Linux - 5.x-7.x - 32-bit (x86) and 64-bit (x86_64)

    <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201954051">Red Hat Enterprise Linux</a> - 5.x-7.x - 32-bit (x86) and 64-bit (x86_64)

    Scientific Linux - 6.x-7.x - 32-bit (x86) and 64-bit (x86_64)

    Ubuntu - 12.04, 14.04, 16.04 - 32-bit (x86, armel, armhf) and 64-bit (x86_64)

    Windows Server - 2008 R2-2016- 32-bit (x86) and 64-bit (x64)

    This list was last updated on June 9, 2017 with the release of meter version 4.6.2.

    View Article
  • Version 4.6.2

    Meter 4.6.2-839 Released to production on 6/9/2017.

    Official Release Notes Version 4.6.2

    Features

    New Remote Procedure call which allows the proxying of Pulse events through the meter to the back end API. This provides a much greater degree of control for events for clients which need to access all of the available raw event fields. For further information on raw events, see

    <a rel="noopener,nofollow" target="_blank" href="https://documentation.truesight.bmc.com/events#RawEvent">https://documentation.truesight.bmc.com/events#RawEvent</a>

    Addition of support for new platforms:

    With this release, we have added support for:

    OpenSUSE 13.2

    End of support for Obsolete Platforms

    With this release, we have withdrawn support for:

    CentOS 5

    OpenSUSE 12.1 - 13.1

    View Article
  • Follow the steps given below to integrate with Microsoft Azure:

    Click Settings &gt; Integrations

    Click Add New

    Click Azure

    Enter the required details. For more information on the values, see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/213397725">Creating Credentials for Azure Integration</a>.

    Click Test Connection to test the connection with the Microsoft Azure instance.

    Click Submit to save the integration.

    The following Azure services are supported. For more information on the supported metrics for each service, see <a rel="noopener,nofollow" target="_blank" href="http://truesightpulse.bmc.com/integrations/azure-monitoring">http://truesightpulse.bmc.com/integrations/azure-monitoring</a>.

    Azure Windows VM

    Azure Linux VM

    Azure SQL Database

    View Article
  • Pulse’s source query language provides a mechanism for creating dynamic lists of sources which are in turn used in source filter definitions, dashboard legend searches, and source selections. Where within Pulse the queries can be used is discussed <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/articles/115002743329-Introducing-Dynamic-Filters">here</a>.

    Available search criteria are:

    source name patterns, and;

    the relative time since data was last seen from the sources.

    For example, to create a filter that includes all sources that contain the text “prod” which have been active in the last two hours you would cre-ate a filter with the query:

    prod &amp;&amp; last: 2h

    WildcardQueries

    By default, queries are implied substring searches. Examples follow.

    prod

    This query returns all sources that contain “prod” in the source name. Matched sources would include:

    service-24.prod.domain.com

    prod.domain.com

    prod

    source-prod

    *prod*

    This is an explicit version of the previous example. The wild-carding is explicitly defined but has the same effect of returning all sources that contain the string.

    prod*

    This query searches for “sources that start with” and would match:

    prod.domain.com

    prod

    *prod

    This query searches for “sources that end with” and would match:

    prod

    source-prod

    prod.*.com

    This query would have the following valid matches:

    service-24.prod.domain.com

    prod.domain.com

    Exact Match

    To find a specific source that must be an exact match, one must surround the string search with double quotes. For example:

    "service-24.prod.domain.com"

    This query will return a source which has a name "service-24.prod.domain.com".

    Relative Active Time

    To find sources that have reported within the last few hours you can use the following query:

    last: 24h

    This query will return all sources that have been active in the last 24 hours.

    Relative Active Time with comparisons

    Alternatively this same time modifier can be written like the following:

    last &gt; 24h

    The following query will return all sources that have not been active in the last 2 hours.

    last &lt; 2h

    Binary Comparison "AND" Queries

    This query will return only the matching sources that matched in our implicit wildcard query example earlier which have sent data within the last 2 hours:

    prod &amp;&amp; last: 2h

    Alternatively you can use the word “AND” which has the exact same effect:

    prod and last: 2h

    Binary Comparison "OR" Queries

    This query will return the matching sources from our implicit wildcard query example as well as any other sources that have been active within the last 2 hours:

    prod || last: 2h

    Alternatively, you can use the word “OR” which has the exact same effect:

    prod or last: 2h

    Chained Comparison Queries:

    This query is effectively processed like ((prod || staging) &amp;&amp; last: 24h) due to typical order of operations.

    prod || staging &amp;&amp; last: 24h

    View Article
  • Source filters are used in dashboards, alarms, and the situation room to focus on a subset of all available sources. Source filters could only be defined as a list of specifichard-codedsources.

    Released on April 19, 2017,dynamic source filtershave introduced new and far more flexible methods of both creating filters and specifying the members of the source list. Further, membership in a filter is now dynamic. That is to say that a source may come and go from a filter as the source’s properties fulfill the membership selection criteria of the filter.

    Presently, dynamic source filter selection criteria are limited to

    source name patterns, and;

    how recently data has been received for the source.

    In the near future, additional properties such as ec2 tags will be available in the selection criteria. These criteria are specified using a new simple query syntax which is described in detail <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/articles/115003520529-Source-Query-Language">here</a>.

    Finally, it’s worth pointing out that one can configure an alarm to monitor a list of sources defined by a source filter which is now dynamic so that when a new source is added to Pulse one no longer needs to manually add the source to one or more filter lists.

    To review a video of the feature please see the following <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/115002770225">link</a>.

    Search in Dashboard Legend

    The dashboard’s legend has been enhanced by the addition of a search box which provides the ability to enter a <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/articles/115003520529-Source-Query-Language">source query</a> that immediately filters the sources in the current view. Type your query into the search box and see the resulting list. When you are happy with the results, press Enter and the listed sources will be selected into the current legend. This replaces the need for the ‘delete’ button next to each source, and hence the delete button has been removed from the legend.

    <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/articles/115003520529-Source-Query-Language">source query</a>

    Source Filter Definitions

    The Settings -&gt; Filters-&gt; Add Filter panel has been completely overhauled. Prior to this update, the panel only provided the ability to add or modify the source names in a filter list:

    The significantly enhanced panel now provides for entry of a <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/articles/115003520529-Source-Query-Language">query (selection criteria)</a> and an optional description of the filter. It displays of the list’s membership as well. The panel is interactive in that as the query is being entered, the membership list is updated in real time.

    Note that when we enhanced source filters, we converted any existing source filters from the older simple host lists to new selection queries. Users may find that they want to re-define their existing queries to take advantage of the new capabilities.

    View Article
  • BMC TrueSight Pulse provides easy to use alarms, which will be triggered when the monitored metric goes above (or below) the defined threshold. Each alarm can be connected toone or more Actions, so users can be notified when an alarm status changes. When the account is created, we pre-provision several simple alarms to get you started and connect them to the e-mail Action. Customers who use differentcollaboration tools can easily createmore Actions and attach them to Alarms. This article describes how to integrate with popular <a rel="noopener,nofollow" target="_blank" href="https://www.opsgenie.com/">OpsGenie</a> service.

    Note there is also a <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/202671571">video tutorial</a> of this integration available.

    First we will add the TrueSightPulseintegration to your OpsGenie account. Log in to OpsGenie and click on "Integrations" in the left hand menu

    A list of all available OpsGenie integrations will appear, scroll down to the BMC TrueSight Pulsetile, hover over it and click "add"

    The next screen will give you details on setting up the integration and some config options below. First copy the Api key to your clipboard (you'll need this in BMC TrueSight Pulse)

    Now scroll down to configure where inbound alerts are directed to, I've sent them to the Ops_team and made myself a recipient. You can also suppress, disable or reset the integrations from here. When you are finished be sure to click "Save".

    Now head back over to your BMC TrueSight Pulseaccount and go to "Settings" -&gt; "Actions"

    Click "Add Action" in the bottom right of the popup

    The next screen shows a list of all available Actions, click "Add" next to the OpsGenie Action.

    Give your Action a name (remember you could have multiple actions for different teams/alerts) and paste your API key that we copied earlier, and click "Save"

    Now we need to attach this action to any Alarms we wish to be notified about. To do this go to "Alarms" on the left of the Settings screen and select an alarm you wish to be notified about. In the Actions section of that alarm add your new Action from the drop down menu.

    I have also selected "notify for every change", this means that if an Alarm resolves itself it will automatically be closed on the OpsGenie side. Once you are happy, click "Save".

    When the alarm next fires you will receive a new alert in OpsGenie!

    If you click on details you'll see the whole error message with source names and a link to further investigate in BMC TrueSight Pulse.

    View Article
  • A source,associated with a measurement value, describes an instance of athing being measured such as the overall CPU usage of a host, or number of gigabytes used on a file system.

    When using the AWS Integration, sources in the form of instance ids are unique across time and can accumulate if your particular workloads are elastic enough that instances are started and terminated on regular basis.

    To preventcruft sources from being displayed in the left-hand legend, sources can beremoved by either using the web interface or programmatically through a REST API.

    NOTE: Removing a source does not remove its associated measurements; it only removes its visibility within the account, such as the left-hand legend

    Removing Sources Using the Web UI

    Click on the settings icon (a gear) and select sources.

    Check the box labeledAllow removing / un-removing.

    For each source you wish to remove uncheck enabled and check removed.

    Click the save button to apply your changes.

    Removing Source Programmatically

    Removing many sources is tedious so a REST API call is provide to programmatically remove sources.

    Documentation on the API to remove sources by name is <a rel="noopener,nofollow" target="_blank" href="http://premium-documentation.boundary.com/v1/delete/sources/byName">here</a>.

    Listing Sources In An Account

    Sources in an account are listed by the following call:

    $ curl -X GET -u "&lt;e-mail&gt;:$&lt;api-token&gt;" \ 'https://api.truesight.bmc.com/v1/account/sources'

    Deleting A Source In An Account

    1 or more sources can be removed by the following command:

    $ curl -X DELETE -u "&lt;e-mail&gt;:$&lt;api-token&gt;" \

    'https://api.truesight.bmc.com/v1/sources/byName' \

    -H "Content-Type: application/json" \

    -d ' { "names": [ "source1", "source2" ] }'

    Deleting All Sources

    For this example you need to have the command line toolsdescribed <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/202729012-API-CLI-Documentation">here</a> and have the jq tool installed which is downloaded from <a rel="noopener,nofollow" target="_blank" href="https://stedolan.github.io/jq/">here</a>.

    $ source-list | jq '.result.sources | .[] | .name' | tr -d '"' &gt; sources.txt # Generate a list of sources

    $ for source in $(cat sources.txt); do echo "deleting source: $source" ; source-delete -s $source; sleep 1; done # Remove each of the sources listed in the file

    View Article
  • A plugin that collects metrics from SOLR using Rest-API from Solr Admin server.

    You may also refer to this <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/115003082865">video</a> for a recorded walk through of the install and configuration process.

    Prerequisites

    Supported OS: Linux

    TrueSight Pulse meter 4.5.0-778 or later

    Apache Solr 4.5 or later

    To install new meter go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected:

    SOLR_SYSTEM_COMMITED_VIRTUAL_MEMORY_SIZE

    SOLR_SYSTEM_FREE_PHYSICAL_MEMORY_SIZE

    SOLR_SYSTEM_PROCESS_CPU_TIME

    SOLR_SYSTEM_OPEN_FILE_DESCRIPTOR_COUNT

    SOLR_SYSTEM_MAX_FILE_DESCRIPTOR_COUNT

    SOLR_JVM_UPTIME

    SOLR_JVM_MEMORY_FREE

    SOLR_JVM_MEMORY_TOTAL

    SOLR_JVM_MEMORY_MAX

    SOLR_JVM_MEMORY_USED

    SOLR_THREAD_CURRENT

    SOLR_THREAD_PEAK

    SOLR_THREAD_DAEMON

    SOLR_CACHE_DOCUMENT_LOOKUPS

    SOLR_CACHE_DOCUMENT_HITS

    SOLR_CACHE_DOCUMENT_HITRATIO

    SOLR_CACHE_DOCUMENT_INSERTS

    SOLR_CACHE_DOCUMENT_SIZE

    SOLR_CACHE_DOCUMENT_EVICTIONS

    SOLR_CACHE_DOCUMENT_WARMUPTIME

    Installing the plugin

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">Pulse</a>.

    2) Go to Settings &gt; Plugins

    3) Click on 'Get Plugins'.

    4)Scroll to 'solr' and click 'Install'.

    5) Pulse provides a list of meters to associate to the plugin. Please select a meter. Now an "Add a plugin..." drop down box will display. Please click and select 'solr'.

    6) Click "Add a Instance" and enter the following details:

    Field

    Description

    Host

    SOLR hostname default:localhost

    Port

    SOLR Admin port number default: 8983

    Core Name

    The Solr core(s) that need to be monitored

    Source Name

    Source name which will be displayed as source identifier

    Poll Interval

    The frequency (in milliseconds) used to poll the SOLR for metrics.

    7)The following dashboards will be created:

    Solr-General

    Solr-Cache

    References

    <a rel="noopener,nofollow" target="_blank" href="https://github.com/boundary/meter-plugin-solr">Solr meter plugin on GitHub</a>

    View Article
  • This video will walk you through the installation and configuration of the BMC TrueSight plugin for Apache Solr.

    View Article
  • This video will walk you through the installation and configuration of the BMC TrueSight plugin for Apache Spark.

    View Article
  • Monitor, visualize and alert on your Apache Spark MetricsServlet sink in one-second intervals with this TrueSight Pulse Apache Spark API plugin.

    You may also refer to this <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/115003082385">video</a> for a recorded walk through of the install and configuration process.

    Prerequisites

    Supported OS: Linux

    Apache Spark 1.2.1 or later

    TrueSight Pulse meter 4.2 or later

    To install new meter go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected:

    SPARK_MASTER_WORKERS_COUNT

    SPARK_MASTER_APPLICATIONS_RUNNING_COUNT

    SPARK_MASTER_APPLICATIONS_WAITING_COUNT

    SPARK_MASTER_JVM_MEMORY_USED

    SPARK_MASTER_JVM_MEMORY_COMMITTED

    SPARK_MASTER_JVM_HEAP_MEMORY_USED

    SPARK_MASTER_JVM_HEAP_MEMORY_USAGE

    SPARK_MASTER_JVM_NONHEAP_MEMORY_COMMITTED

    SPARK_MASTER_JVM_NONHEAP_MEMORY_USED

    SPARK_MASTER_JVM_NONHEAP_MEMORY_USAGE

    SPARK_APP_JOBS_ACTIVE

    SPARK_APP_JOBS_ALL

    SPARK_APP_STAGES_FAILED

    SPARK_APP_STAGES_RUNNING

    SPARK_APP_STAGES_WAITING

    SPARK_APP_BLKMGR_DISK_SPACE_USED

    SPARK_APP_BLKMGR_MEMORY_USED

    SPARK_APP_BLKMGR_MEMORY_FREE

    SPARK_APP_JVM_MEMORY_COMMITTED

    SPARK_APP_JVM_MEMORY_USED

    SPARK_APP_JVM_HEAP_MEMORY_COMMITTED

    SPARK_APP_JVM_HEAP_MEMORY_USED

    SPARK_APP_JVM_HEAP_MEMORY_USAGE

    How To Install Apache SparkPlugin

    Plugin Setup

    MetricsServlet

    MetricsServlet is added by default as a sink in master, worker and client driver. See the /etc/conf/metrics.properties file on your Spark installation for more details.

    JMV Source

    You can also enable the jvm source for instance master, worker, driver and executor to get detailed metrics of the JVM uncommenting the following lines in your /etc/conf/metrics.properties

    The plugin gathers metrics from the Master and an optional running application. So you need to configure the host and port for the WebUI of the master and application process.

    WebUI Configuration

    By default, the WebUI for the master runs on port 18080 and, for applications the its on 4040 port. These are the default values for this parameters but you can change them based on your configuration.

    Installing the plugin

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">BMC TrueSight Pulse console</a>.

    2) Go to Settings &gt; Plugins

    3) Click on 'Get Plugins'.

    4)Scroll to 'spark' and click 'Install'.

    <a rel="noopener,nofollow" target="_blank" href="http://spark.apache.org/docs/latest/">Apache SparkDocumentation</a>

    5) Pulse provides a list of meters to associate to the plugin. Please select a meter. Now an "Add a plugin..." drop down box will display. Please click and select 'spark':

    6)You will be prompted to "Add an Instance".

    7) You can select default settings or update per your configuration. The "Source" value is the name to display in the legend for the metrics data. It will default to the hostname of the server. Click "OK".

    8)The following dashboards will be created:

    Spark Master

    Spark Application

    References

    View Article
  • Check this out!

    That is a realtime graph of one of our production clusters. You can click to see a legend, drag around to see historical data, zoom out to see larger sections of time (with the mouse wheel), etc... It is essentially everything you get within yourTruesight Pulsedashboard, except it is embedded in any web page you like.

    How to do it? Very easy.

    Sign up at <a rel="noopener,nofollow" target="_blank" href="http://www.bmc.com/truesightpulse">http://www.bmc.com/truesightpulse</a>. Fill in a couple of fields to get your trial account rolling. Install theBMC TrueSight Pulse Meteron any of the servers you want to track (once you sign up you will get instructions on the agent setup).

    With yourTruesight Pulsedash running, just click the embed button on the menu:

    <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201540811-Tip-Embedding-URL-s-and-Grouping-Servers">video</a>

    Here's the embed dialog. Notice we have all our metrics on the left. The one we want is CPU.

    We just need to drag+drop the CPU metric to the upper left of the grid...

    Once we've dropped in CPU, let's drag the corner so that it takes up the whole display

    For this graph we will turn off the header, legend, and slider

    To make it fit nicely onto our page we can set the background to transparent

    And finally, because our target web page has a white background we will set the light theme

    So look and feel are all fine, let's copy the HTML

    And here's the snippet that was copied to the clipboard:

    &lt;iframe src="https://premium.boundary.com/embed/e.5d76805c17?d-w=3&amp;d-h=2&amp;

    d-pad=5&amp;d-header=0&amp;d-slider=0&amp;d-legend=0&amp;d-light=1&amp;d-bg=none&amp;

    d-sg-cpu=0-0-3-2#null" allowtransparency="true"&gt;&lt;/iframe&gt;

    Note: This iframe will be of the default width/height. You can add width="your width" and height="your height" tags to the iframe and the graphs will resize accordingly.

    Just paste that into the web page of your choice and we are good to go! Note, there is no login or password here, bt the link contains "secret" part, called Embed token.

    If, any time in future, you would decide to revoke the rights to show your charts outside BMC TrueSight Pulse, please go to <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home#settings/account">Settings-&gt;Account</a> and click reset link for Embed token. All previously shared links will become invalid.

    Oh, there's one more thing....

    For those who have been reading so far, we have not one, but two undocumented parameters, which can be added to the URL to provide additional customization. Those are 'filter' and 'exc'. The first allows to pre-select certain servers, so they will be shown as colored lines, while all others will be shown as gray lines. The second parameter allows to hide all the gray lines. So, consider manually adding something like

    &amp;filter=web1/web2&amp;exc=1

    to the URL generated by the UI and decide if it is useful for you.

    Check this for more coolexamples - creating customized dashboards for specific group of servers.

    View Article
  • TrueSight PulseDashboards feature innovative Legend Bar in the left hand side of your dashboards.This dynamic legend bar shows which colour is assigned to each of servers shown in the current dashboard. But it also doubles as selection and focus control.

    When dashboard is selected, the legend bar is populated with the servers relevant to this dashboard. This is automatically determined by metrics used. In the beginning, all the toggles are in 'on' positions.

    You can hide a specific server by clicking its toggle in the legend, this will turn its' line grey on the graphs

    You can continue to select different servers by clicking the toggles.

    This way we can add or remove selections one by one. Selected servers will colored, while all other will be shown using gray color. If you would like to focus on selected ones only and remove grey lines, use 'context' toggle button on the bottom left.

    There are also 3 other buttons next to the contextbutton. These allow you to select all, select none, or inverse your selection

    The Invert Selection button selects the opposite of your current selection. For example if I deselect my clm-aus-000208server as below:

    and hit the "select inverse" button all servers except for clm-aus-000208 will be deselected as below:

    View Article
  • NOTE

    On October 11, 2016, BMC released <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/articles/212732505-Version-4-4-1">Meter Version 4.4.1</a> which changed the name of the meter from boundary-meter to truesight-meter. This article reflects the change. If you are using a meter version prior to 4.4.1, then you will need to reference boundary-meter instead of truesight-meter in the operations discussed in this article.

    Troubleshooting Installation

    During the installation you might get the following error:

    <a rel="noopener,nofollow" target="_blank" href="https://nmap.org/npcap/">Npcap</a>

    The cause for this error may vary.

    Invalid API Token

    First ensure that you have entered the right API Token (Install Token) in the Installation screen. You will find your token in TrueSight Pulse by navigating to the settings window and selecting "Help With Installation". You reach the settings window by selecting the gearwheel in the navigation bar on the left side of the screen. The window will look similar to this:

    Ensure by copy and pasting the API Token to the installation window that you are using the right api token. Be aware that the period (.) after the API Token is not part of the API Token.

    Internet Access

    Another reason for getting this message might be that you are not connected to the internet. To ensure that you have access to the internet opena browser and try to access http://www.bmc.com. If you are able to see the BMC Homepage your browser has access to the internet.

    Proxy

    Even though your browser has access to the internet you could be accessing the internet through a proxy. In this case the installation will also show the error mentioned above. You would need to start the installer with command line option

    HTTPS_PROXY=&lt;hostname&gt;:&lt;port&gt;

    to force it to use your proxy when trying to access the internet.

    For further information on how to invoke the installer from the command line please refer to <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201856852-BMC-TrueSight-Pulse-Meter-Meter-Installer-Variables">Knowledge Article 201856852</a>.

    Troubleshooting Meter

    You can stop, start or restart TrueSightmeter using the services applet from Windows Control Panel.

    Alternatively, you can open a command window as Administrator and use 'sc' command to query the status, stop, start and restart the service.

    The service name for command line commands is "truesight_meter". Sample commands are:

    sc query truesight_meter

    sc stop truesight_meter

    sc start truesight_meter

    TrueSightMeter versions prior to <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/115002476225-Version-4-6-1-April-6-2017">4.6.1</a> relied upon an open source library (either <a rel="noopener,nofollow" target="_blank" href="http://www.winpcap.org/">WinPcap</a> or depending on the meter version) which was automatically installed by the meter installer. It will be shown as a separate program in "Programs and Features" section of "Control Panel". If you have another application which also uses WinPcap, and installed or uninstalledit, it might have installed incompatible version of WinPcap or uninstalled it altogether. Current version of WinPcap used by Meter is v4.1.3.

    However, we strongly recommend upgrading the meter to version 4.6.1 which completely removes the need for winpcap or npcap to be installed.

    The meter outputs its log messages to the Windows Event Log, into the Application and Services category. You can savemultiple eventsinto file using 'Actions' Panel at the right side. If you intendto send the file to BMC TrueSightSupport, please save the file as a CSV.

    Check that local tie is set to be automatically synchronized to Internet Network Servers.

    View Article
  • BMC TrueSight Pulseprovides technology <a rel="noopener,nofollow" target="_blank" href="http://www.bmc.com/truesightpulse/integrations/">plugins</a> to extend the features of the core product and provide the coverage ofmultiple 3rd party products. Unlikethe <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/categories/200178671-Agent-Meter">BMC TrueSight Pulse Meter</a> (which is developed in C language, compiled tonative code and fully self-contained), theplugins usually are implemented using a dynamic language and require additional runtimesupport, e.g. node.js, PythonorJava. Additionally, some plugins are not supported on all <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201223531-Boundary-Meter-Supported-Platforms">platforms supported by Meter</a>.

    Please refer to the specific plugin's README file for exact pre-requisite requirements.

    If plugin requires Pythonsupport, it should be installed on the host before installing the plugin. The installation method depends on server OS. Check if you are already have the Python installed and what is itsversion.

    Checking installed version

    On Windows run the command "python" in command prompt or PowerShell.

    <a rel="noopener,nofollow" target="_blank" href="https://www.python.org/downloads/mac-osx/">Python web site</a>

    On Linux or UNIX run the same "python" command in a terminal.

    We needPython v2.6.6 or later

    Installation instructions

    Linux and Unix(Debian, Ubuntu, FreeBSD, ...)

    The latest versions of CentOS, Fedora, Redhat Enterprise (RHEL) and Ubuntu come with Python 2.7 out of the box.

    To see which version of Python you have installed, open a command prompt and run

    $ python --version

    If not installed, type the following command:

    $ sudo yum install python

    OR

    # yum install python

    Use the following commands to install Python under Debian and Ubuntu Linux:

    First, install some dependencies:

    sudo apt-get install build-essential

    sudo apt-get install libreadline-gplv2-dev libncursesw5-dev libssl-dev libsqlite3-dev tk-dev libgdbm-dev libc6-dev libbz2-dev

    Then download using the following command:

    cd ~/Downloads/

    wget https://www.python.org/ftp/python/2.7.11/Python-2.7.11.tgz

    or download directly from <a rel="noopener,nofollow" target="_blank" href="https://www.python.org/downloads/source/">https://www.python.org/downloads/source/</a>

    Extract and go to the dirctory:

    tar -xvf Python-2.7.11.tgz

    cd Python-2.7.11

    Now, install using the following commands:

    ./configure

    make

    sudo make install

    Windows

    Download latest native Python installer for Windows at <a rel="noopener,nofollow" target="_blank" href="https://www.python.org/downloads/windows/">Python web site</a>.

    Mac OS X

    Download latest native Python installer for OSXat .

    View Article
  • A plugin that displays the average TCP Round Trip Time for a host.

    Prerequisites

    Supported OS: Linux, OS X

    TrueSight Pulse meter 4.5.0-778 or later

    To install a new meter, go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version, see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected:

    TCP RTT

    Enabling the TCP timestamp on your computer

    In order to provide the TCP round trip time metric, the optional TCP timestamp settings must be enabled on the target computer. Depending on the Operating System, it may or may not be enabled by default. The table below shows the supported Operating Systems and the command used to enable the flag.

    Operating System

    Enable Command

    Default setting

    OS/X 10.8 to 10.10

    sudo sysctl net.inet.tcp.rfc1323=1

    Enabled

    OS/X 10.11

    Unknown - feature was removed

    Unknown

    Ubuntu

    echo 1 &gt; /proc/sys/net/ipv4/tcp_timestamps

    Enabled

    CentOS

    echo 1 &gt; /proc/sys/net/ipv4/tcp_timestamps

    Enabled

    FreeBSD

    sudo sysctl net.inet.tcp.rfc1323=1

    Enabled

    Ubuntu

    echo 1 &gt; /proc/sys/net/ipv4/tcp_timestamps

    Enabled

    ArchLinux

    echo 1 &gt; /proc/sys/net/ipv4/tcp_timestamps

    Enabled

    OpenSuse

    echo 1 &gt; /proc/sys/net/ipv4/tcp_timestamps

    Enabled

    Alpine

    echo 1 &gt; /proc/sys/net/ipv4/tcp_timestamps

    Enabled

    Installing the plugin

    1) Log into <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">Pulse</a>.

    2) Go to Settings &gt; Plugins.

    3) Click on 'Get Plugins'.

    4)Scroll to 'tcprtt' and click 'Install'.

    5) Pulse provides a list of meters to associate to the plugin. Select a meter.

    6) The "Add a plugin..." drop down box will display. Click and select 'tcprtt'.

    7) Type the required details. Use the available tool-tips for help. Click 'OK'.

    Field Name

    Description

    Source

    The source to display in the legend. The host name of the computer is displayed if you do not specify a value.

    Polling Interval

    The frequency at which the metrics are collected from the computer.

    The following dashboard will be created:

    TCP RTT

    References

    <a rel="noopener,nofollow" target="_blank" href="https://github.com/boundary/meter-plugin-tcprtt">TCP RTT plugin on GitHub</a>

    View Article
  • For more detailed information on Dynamic Filtering please see the following <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/115002743329">article</a>.

    View Article
  • The meter plugin Collects metrics from Microsoft SQL Server instance using a subset of the SQL Server Performance Counters from WMI. This plugin supports multiple SQL Server instances running on the same machine. Each instance is displayed as a separate source on your TrueSight Pulse dashboard.

    Prerequisites

    Supported OS: Windows

    TrueSight Pulse meter 4.2 or later

    SQL Server: 2008, 2012, 2014 or 2016

    To install new meter go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected:

    MSSQL_ACTIVE_TEMP_TABLES

    MSSQL_USER_CONNECTIONS

    MSSQL_LOGICAL_CONNECTIONS

    MSSQL_TRANSACTIONS

    MSSQL_PROCESSES_BLOCKED

    MSSQL_LOCK_TIMEOUTS

    MSSQL_LOCK_WAITS

    MSSQL_LOCK_WAIT_TIME_MS

    MSSQL_LOCK_AVERAGE_WAIT_TIME_MS

    MSSQL_LOCK_TIMEOUTS_GT0

    MSSQL_PERCENT_LOG_USED

    MSSQL_REPL_PENDING_XACTS

    MSSQL_COMPILATIONS

    MSSQL_PAGE_IO_LATCH_WAITS

    Installing the plugin

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">BMC TrueSight Pulse console</a>.

    2) Go to Settings &gt; Plugins

    3) Click 'Get Plugins'.

    4)Scroll to 'mssql' and click 'Install'.

    5) Pulse provides a list of meters to associate to the plugin. Select a meter. Now an "Add a plugin..." drop down box will display.

    Field Name

    Description

    Source

    The source to display in the legend for the data

    Poll Interval (ms)

    The interval (in milliseconds) to poll for metrics

    6) Type the required details, use the available tool-tips for help. Click "OK".

    7)The following dashboard will be created:

    MSSQL

    References

    <a rel="noopener,nofollow" target="_blank" href="https://github.com/boundary/boundary-plugin-mssql">MSSQL plugin on GitHub</a>

    View Article
  • BMC TrueSight Pulselets you invite teammates to youraccount, so they can see and discuss the solutions. Everyone has a point of view and an expertise,TrueSight Pulse lets them get involved.

    Inviting someone toTrueSight Pulse is very simple.

    Open up Settings to the Users tab.

    Please select the "TrueSight Account Manager" link.

    Once in "TrueSight Account Manager" select "My Account" &gt; "Account Products".

    For TrueSight Pulse select "Users". You should see the screen below for TrueSight Pulse Users.

    Enter the email address of the user and select "Invite".

    The user will receive an invitation in their email.

    Once the invite is accepted the user will be able to view dashboards.

    If you want to give them permissions to make changes to the account, the admin option in "TrueSight Account Manager" &gt; "Account Users" &gt; "Roles" for user.

    In this case the user '[email protected]', who has just joined this account, already "owns" separateBMC TrueSight Pulse account (for example for testing purposes), he will be able switch between those accounts using Settings-&gt; Dashboards tab.

    View Article
  • Version 4.6.1

    Meter 4.6.1-831 Released to production on 4/6/2017.

    Official Release Notes Version 4.6.1

    Windows auto-upgrade

    The windows version of the meter now supports an auto-upgrade check. This can be enabled in the installer UI by checking the "Enable Meter Auto-Upgrade" button. When enabled, the meter will check for new packages on Sunday night at midnight. The user can change the check times by changing the values in the auto_upgrade/period section of the meter.conf file.

    FreeBSD 11

    FreeBSD released a stable version of 11.0. In support of this, we are now providing a version of the meter package built to install and run on FreeBSD 11.0

    Ubuntu hash signing security

    Ubuntu has increased the security level for package signing with the release of Ubuntu 16. Previously, the meter package was signed using a SHA-1 hash. This has been updated to SHA-256 for improved security and mitigates the warning message -- Signature by key {key} uses weak digest algorithm (SHA1) --that users were getting when using apt-get on Ubuntu 16.

    Meter no longer requires WinPcap or Npcap

    Beginning with this release, the windows version of the meter is no longer dependent upon WinPcap nor npcap. Therefore, they have been removed from the installer. Prior to this release, when installing the meter on Windows, the installer would also install WinPcap (or Npcap) if they were not already installed. This no longer occurs.

    After installing this release of the meter, customers may remove winpcap and/or npcap from their systems subject to any other software that might be using the drivers.

    End of support for Obsolete Platforms

    With this release, we have withdrawn support for FreeBSD 9.

    View Article
  • The monitored metrics for end-user experience (EUE) provide you with a way to measure the performance of your web-based application. The metrics represent the duration of page navigation timing events, which can help you pinpoint areas of concern or interest.

    Where can I see these metrics?

    To see EUE metrics in TrueSight Pulse, you must add the <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/212278645-Setting-up-end-user-monitoring-JavaScript-snippet-">JavaScript snippet</a> to your application. You can see the values of the collected metrics in the <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/211899109-Analyzing-end-user-monitoring-data-in-dashboards">EUE dashboards</a>.

    The following diagram displays the monitored metrics for page navigation timing events, in the order they occur. Each metric is described in the table below.

    End-user experience metrics for page navigation

    Click to enlarge image.

    <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/article_attachments/208279629/page-load_time.png"></a>

    End-user experience metrics for page navigation times

    All times are in milliseconds or seconds.

    Item in diagram

    Name

    Description

    1.

    Page Load

    End-to-end page response time, the entire time it takes to load the page, from initial request to the browser finishes processing the page

    2.

    DNS

    Time for the browser to complete the required domain lookup while retrieving a resource

    3.

    TCP

    Time for the browser to establish a connection with the server, including other time intervals such as SSL handshakes and SOCKS authentication

    4.

    SSL

    Time for the browser to perform the SSL handshake to secure the connection

    5.

    Back-End

    Time spent on server and network tiers

    6.

    Time to First Byte (TTFB)

    Time that the browser waits to receive the first piece of information

    7.

    Page Download

    Time for the browser to download response from server

    8.

    Front-End

    Time for the browser to process the critical rendering path of the request, including parsing, rendering, downloading sources, and executing JavaScript functions

    9.

    DOM Processing to Interactive

    Time that the browser spends loading the webpage until the user can start interacting with it

    10.

    DOM Interactive to Complete

    Time for the browser to load images and videos, and to execute JavaScript code that listens for the DOMContentLoaded event

    11.

    Onload

    Time for the browser to execute JavaScript code that waits for the window.load event

    12.

    Ajax

    Response time of Ajax calls

    End-user experience metrics for page views and errors

    All units are a numeric count.

    Name

    Description

    Page Views

    Indication of user volume, the number of times that users access pages of the application

    JavaScript Errors

    Number of times a JavaScript error occurred. The errors occur in the client browser during runtime.

    Ajax Errors

    Number of Ajax requests that return HTTP error codes

    View Article
  • This plugin monitors MySQL Instances directly for performance statistics. For a full list of metrics collected and to see the pre-requisites for this plugin please see the plugin details in the Product or visit the <a rel="noopener,nofollow" target="_blank" href="https://github.com/boundary/meter-plugin-mysql/blob/master/README.md">readme notes on Github</a>. A video walkthrough of plugin deployment is <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201536772-Plugins-MySQL-Deployment-Walkthrough">available here</a>

    View Article
  • A plugin that collects metrics from Elastic Search clusters and their nodes

    Prerequisites

    Supported OS: Linux, Windows, OS X

    TrueSight Pulse meter 4.2 or later

    To install new meter go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected:

    APACHE_BUSY_RATIO

    APACHE_BUSY_WORKERS

    APACHE_BYTES

    APACHE_BYTES_PER_REQUEST

    APACHE_CPU

    APACHE_IDLE_WORKERS

    APACHE_REQUESTS

    Installing the plugin

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">Pulse</a>.

    2) Go to Settings &gt; Plugins

    3) Click on 'Get Plugins'.

    4)Scroll to 'apache' and click 'Install'.

    5) Pulse provides a list of meters to associate to the plugin. Select a meter.

    6) An "Add a plugin..." drop down box will display. Click and select 'apache'.

    The following dashboard will be created:

    Apache Server

    References

    <a rel="noopener,nofollow" target="_blank" href="https://github.com/boundary/boundary-plugin-apache-http-server">Apache HTTP Server plugin on GitHub</a>

    View Article
  • This meter plugin collects metrics from Docker.

    Prerequisites

    Supported OS: Linux

    TrueSight Pulse meter 4.2 or later

    Docker version 1.7.1 or later

    To install a new meter go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version, see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected:

    DOCKER_MEMORY_USAGE_BYTES

    DOCKER_MEMORY_LIMIT_BYTES

    DOCKER_MEMORY_USAGE_PERCENT

    DOCKER_TOTAL_CPU_USAGE

    DOCKER_NETWORK_RX_BYTES

    DOCKER_NETWORK_TX_BYTES

    DOCKER_NETWORK_RX_PACKETS

    DOCKER_NETWORK_TX_PACKETS

    DOCKER_NETWORK_RX_ERRORS

    DOCKER_NETWORK_TX_ERRORS

    DOCKER_BLOCK_IO_READ_BYTES

    DOCKER_BLOCK_IO_WRITE_BYTES

    Installing the plugin

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">BMC TrueSight Pulse console</a>.

    2) Go to Settings &gt; Plugins.

    3) Click 'Get Plugins'.

    4)Scroll to 'docker' and click 'Install'.

    5) Pulse will provide a list of meters to associate to the plugin. Select a meter. An "Add a plugin..." drop down box will display.

    The following dashboard will be created:

    Docker Summary

    References

    <a rel="noopener,nofollow" target="_blank" href="https://github.com/boundary/meter-plugin-docker">Docker plugin on GitHub</a>

    View Article
  • This meter plugin collects metrics from Cassandra.

    Prerequisites

    Supported OS: Linux, Windows, OS X

    TrueSight Pulse meter 4.2 or later

    Cassandra version 2.1 or later

    To install a new meter go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version, see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected:

    CASSANDRA_COMPACTION_PENDING_TASKS

    CASSANDRA_COMPACTION_COMPLETED_TASKS

    CASSANDRA_COMPACTION_TOTAL_COMPLETED_RATE

    CASSANDRA_COMPACTION_BYTES_COMPACTED

    CASSANDRA_CACHE_KEYCACHE_HITRATE

    CASSANDRA_CACHE_KEYCACHE_REQUESTS_RATE

    CASSANDRA_CACHE_KEYCACHE_ENTRIES

    CASSANDRA_CACHE_KEYCACHE_SIZE

    CASSANDRA_CACHE_KEYCACHE_CAPACITY

    CASSANDRA_CACHE_ROWCACHE_HITRATE

    CASSANDRA_CACHE_ROWCACHE_REQUESTS_RATE

    CASSANDRA_CACHE_ROWCACHE_ENTRIES

    CASSANDRA_CACHE_ROWCACHE_SIZE

    CASSANDRA_CACHE_ROWCACHE_CAPACITY

    CASSANDRA_CACHE_COUNTERCACHE_HITRATE

    CASSANDRA_CACHE_COUNTERCACHE_REQUESTS_RATE

    CASSANDRA_CACHE_COUNTERCACHE_ENTRIES

    CASSANDRA_CACHE_COUNTERCACHE_SIZE

    CASSANDRA_CACHE_COUNTERCHE_CAPACITY

    CASSANDRA_HEAP_MEMORY_USED

    CASSANDRA_WRITE_LATENCY_MEAN

    CASSANDRA_WRITE_FAILURES_RATE

    CASSANDRA_WRITE_TIMEOUTS_RATE

    CASSANDRA_READ_LATENCY_MEAN

    CASSANDRA_READ_FAILURES_RATE

    CASSANDRA_READ_TIMEOUTS_RATE

    CASSANDRA_CLIENT_CONNECTED_NATIVE_CLIENTS

    CASSANDRA_CLIENT_CONNECTED_THRIFT_CLIENTS

    CASSANDRA_STORAGE_LOAD_BYTES

    CASSANDRA_STORAGE_COMMITLOG_SIZE

    CASSANDRA_WRITE_LATENCY_95P

    CASSANDRA_WRITE_1MIN_RATE

    CASSANDRA_READ_LATENCY_95P

    CASSANDRA_READ_1MIN_RATE

    CASSANDRA_RANGE_SLICE_LATENCY_MEAN

    CASSANDRA_RANGE_SLICE_LATENCY_95P

    CASSANDRA_RANGE_SLICE_1MIN_RATE

    CASSANDRA_RANGE_SLICE_FAILURES_RATE

    CASSANDRA_RANGE_SLICE_TIMEOUTS_RATE

    CASSANDRA_CAS_READ_LATENCY_MEAN

    CASSANDRA_CAS_READ_LATENCY_95P

    CASSANDRA_CAS_READ_1MIN_RATE

    CASSANDRA_CAS_READ_FAILURES_RATE

    CASSANDRA_CAS_READ_TIMEOUTS_RATE

    CASSANDRA_CAS_WRITE_LATENCY_MEAN

    CASSANDRA_CAS_WRITE_LATENCY_95P

    CASSANDRA_CAS_WRITE_1MIN_RATE

    CASSANDRA_CAS_WRITE_FAILURES_RATE

    CASSANDRA_CAS_WRITE_TIMEOUTS_RATE

    CASSANDRA_DROPPED_MUTATION_RATE

    CASSANDRA_DROPPED_READ_RATE

    CASSANDRA_DROPPED_COUNTER_MUTATION_RATE

    CASSANDRA_DROPPED_HINT_RATE

    CASSANDRA_PENDING_MUTATIONS

    CASSANDRA_PENDING_COUNTER_MUTATIONS

    CASSANDRA_PENDING_READS

    Installing the plugin

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">BMC TrueSight Pulse console</a>.

    2) Go to Settings &gt; Plugins.

    3) Click 'Get Plugins'.

    4)Scroll to 'cassandra' and click 'Install'.

    5) Pulse will provide a list of meters to associate to the plugin. Select a meter. An "Add a plugin..." drop down box will display.

    6) Click 'Add a Instance', and type the required details, use the available tool-tips for help. Click 'OK'.

    Field Name

    Description

    Host

    Host of the Cassandra JMX endpoint

    Port

    Port of the Cassandra JMX endpoint. Defaults to 7199

    User

    Username to access the Cassandra JMX endpoint

    Password

    Password to access the Cassandra JMX endpoint

    Poll Interval

    How often should the plugin poll for metrics.

    Source

    The Source to display in the legend for the metrics data. It will default to the hostname of the server.

    7)The following dashboard will be created:

    Cassandra General

    Cassandra Caches

    Cassandra Request latencies by type

    Cassandra Pending / Dropped Messages

    References

    <a rel="noopener,nofollow" target="_blank" href="https://github.com/boundary/meter-plugin-cassandra">Cassandra plugin on GitHub</a>

    View Article
  • This meter plugin collects metrics from the Kafka.

    Prerequisites

    Supported OS: Linux, Windows, OS X

    TrueSight Pulse meter 4.2 or later

    Kafka version 0.8.2 or later

    To install new meter go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected:

    KAFKA_JVM_HEAPMEMORY_USED

    KAFKA_TOPIC_MESSAGE_IN_RATE

    KAFKA_TOPIC_BYTE_IN_RATE

    KAFKA_TOPIC_BYTE_OUT_RATE

    KAFKA_PRODUCE_REQUEST_RATE

    KAFKA_CONSUME_REQUEST_RATE

    KAFKA_FOLLOW_REQUEST_RATE

    KAFKA_PRODUCE_REQUEST_FAILS

    KAFKA_FETCH_REQUEST_FAILS

    KAFKA_ISR_EXPAND_RATE

    KAFKA_ISR_SHRINK_RATE

    KAFKA_PRODUCE_REQUEST_TOTAL_TIME

    KAFKA_CONSUME_REQUEST_TOTAL_TIME

    KAFKA_FOLLOW_REQUEST_TOTAL_TIME

    KAFKA_PRODUCE_REQUEST_RESPONSE_TIME

    KAFKA_CONSUME_REQUEST_RESPONSE_TIME

    KAFKA_FOLLOW_REQUEST_RESPONSE_TIME

    KAFKA_NETWORK_PROCESSOR_IDLE_TIME

    KAFKA_REQUEST_HANDLER_THREADS_IDLE_TIME

    KAFKA_UNDER_REPLICATED_PARTITIONS

    KAFKA_LEADER_ELECTION_RATE

    KAFKA_UNCLEAN_LEADER_ELECTION_RATE

    KAFKA_MAX_LAG_MESSAGES_FOLLOWER_AND_REPLICAS

    KAFKA_PRODUCER_PURGATORY_REQUESTS_WAITING

    KAFKA_PRODUCER_PURGATORY_REQUESTS_DELAYED

    KAFKA_FETCH_PURGATORY_REQUESTS_WAITING

    KAFKA_FETCH_PURGATORY_REQUESTS_DELAYED

    KAFKA_LEADER_COUNT

    KAFKA_PARTITIONS_COUNT

    KAFKA_OFFLINE_PARTITIONS_COUNT

    KAFKA_ACTIVE_CONTROLLER_COUNT

    Installing the plugin

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">BMC TrueSight Pulse console</a>.

    2) Go to Settings &gt; Plugins

    3) Click on 'Get Plugins'.

    4)Scroll to 'kafka' and click 'Install'.

    5) Next, Pulse will provide a list of meters to associate to the plugin. Select a meter. An "Add a plugin..." drop down box will display.

    The following dashboard will be created:

    Kafka General

    References

    <a rel="noopener,nofollow" target="_blank" href="https://github.com/boundary/meter-plugin-kafka">Kafka plugin on GitHub</a>

    View Article
  • A plugin that collects metrics from Elastic Search clusters and their nodes

    Prerequisites

    Supported OS: Linux, Windows, OS X

    TrueSight Pulse meter 4.2.0-611 or later

    To install new meter go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected:

    ELASTIC_SEARCH_STATUS

    ELASTIC_SEARCH_NODE_COUNT

    ELASTIC_SEARCH_INDEX_COUNT

    ELASTIC_SEARCH_DOCUMENT_COUNT

    ELASTIC_SEARCH_STORE_SIZE

    ELASTIC_SEARCH_SEGMENT_COUNT

    ELASTIC_SEARCH_TOTAL_SHARDS

    ELASTIC_SEARCH_PRIMARY_SHARDS

    ELASTIC_SEARCH_FIELDDATA_MEMORY_SIZE

    ELASTIC_SEARCH_FIELDDATA_EVICTIONS

    ELASTIC_SEARCH_FILTER_CACHE_MEMORY_SIZE

    ELASTIC_SEARCH_FILTER_CACHE_EVICTIONS

    ELASTIC_SEARCH_QUERY_CACHE_MEMORY_SIZE

    ELASTIC_SEARCH_QUERY_CACHE_EVICTIONS

    ELASTIC_SEARCH_ID_CACHE_MEMORY_SIZE

    ELASTIC_SEARCH_COMPLETION_SIZE

    ELASTIC_SEARCH_NO_OF_NODES

    ELASTIC_SEARCH_NO_OF_DATA_NODES

    ELASTIC_SEARCH_ACTIVE_PRIMARY_SHARDS

    ELASTIC_SEARCH_ACTIVE_SHARDS

    ELASTIC_SEARCH_RELOCATING_SHARDS

    ELASTIC_SEARCH_INITIALISING_SHARDS

    ELASTIC_SEARCH_UNASSIGNED_SHARDS

    ELASTIC_SEARCH_JVM_UPTIME_IN_MILLIS

    ELASTIC_SEARCH_JVM_MEM_HEAP_USED_PERCENT

    ELASTIC_SEARCH_PROCESS_OPEN_FILE_DESCRIPTORS

    ELASTIC_SEARCH_PROCESS_MAX_FILE_DESCRIPTORS

    ELASTIC_SEARCH_FS_DATA_AVAILABLE_IN_BYTES

    ELASTIC_SEARCH_BREAKERS_FIELDDATA_TRIPPED

    Installing the plugin

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">Pulse</a>.

    2) Go to Settings &gt; Plugins

    3) Click on 'Get Plugins'.

    4)Scroll to 'elasticsearch' and click 'Install'.

    5) Pulse provides a list of meters to associate to the plugin. Select a meter.

    6) An "Add a plugin..." drop down box will display. Click and select 'elasticsearch'.

    7) Click "Add a Instance" and enter the following details:

    Field

    Description

    Name

    The name of the Elastic Search instance.

    Host

    The Elastic Search hostname or IP address.

    Port

    The Elastic Search port. Default value is 9200.

    Poll Interval (ms)

    The frequency (in milliseconds) used to poll for metrics.

    Source

    The Source to display in the legend for the elastic search data.It will default to the hostname of the server.

    8)The following dashboards will be created:

    ES ClusterStats

    ES ClusterStats v2

    ES ClusterHealth

    ES NodesStats

    References

    <a rel="noopener,nofollow" target="_blank" href="https://github.com/boundary/boundary-plugin-elasticsearch">Elasticsearch plugin on GitHub</a>

    View Article
  • Monitor, visualize and alert on your OpenStackenvironment in one-second intervals with this TrueSight Pulse OpenStackAPI plugin.This plugin grabs metrics from the OpenStack node where it is started and parses the data to be able to integrate into Pulse. To be able to start, ceilometer should be well configured on the machine and credentials needs to be created. Additional metrics can be added from the ceilometer by editing the plugin.py and adding or replacing different mapping tuple objects.

    You may also refer to this <a rel="noopener,nofollow" target="_blank" href="https://youtu.be/mokmyhJbBaA">video</a> for a recorded walk through of the install and configuration process.

    Prerequisites

    Supported OS: Linux

    OpenStack version Mitaka

    TrueSight Pulse meter 4.2 or later

    Ceilometer 2.3.0 or later

    To install new meter go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected:

    OS_CPUUTIL_AVG

    OS_CPUUTIL_SUM

    OS_CPUUTIL_MIN

    OS_CPUUTIL_MAX

    OS_CPU_AVG

    OS_CPU_SUM

    OS_INSTANCE_EVENT_SUM

    OS_INSTANCE_EVENT_MAX

    OS_MEMORY_SUM

    OS_MEMORY_AVG

    OS_MEMORY_USAGE_SUM

    OS_MEMORY_USAGE_AVG

    OS_VOLUME_EVENT_SUM

    OS_VOLUME_EVENT_AVG

    OS_IMAGE_SUM

    OS_IMAGE_AVG

    OS_IMAGE_SIZE_SUM

    OS_IMAGE_SIZE_AVG

    OS_DISK_READ_RATE_SUM

    OS_DISK_READ_RATE_AVG

    OS_DISK_WRITE_RATE_SUM

    OS_DISK_WRITE_RATE_AVG

    OS_NETWORK_IN_BYTES_SUM

    OS_NETWORK_IN_BYTES_AVG

    OS_NETWORK_OUT_BYTES_SUM

    OS_NETWORK_OUT_BYTES_AVG

    OS_MEMORY_RESIDENT_SUM

    OS_MEMORY_RESIDENT_AVG

    How To Install OpenStackPlugin

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">BMC TrueSight Pulse console</a>.

    2) Go to Settings &gt; Plugins

    <a rel="noopener,nofollow" target="_blank" href="http://www.openstack.org/software/start/">OpenStack</a>

    3) Click on 'Get Plugins'.

    4)Scroll to 'openstack' and click 'Install'.

    5) Next, Pulse will provide a list of meters to associate to the plugin. Please select a meter. Now an "Add a plugin..." drop down box will display. Please click and select 'openstack':

    6)You will be prompted with prerequisites review for OpenStack configuration. Click "Next".

    7) Fill out the OpenStackconfiguration information.

    8) Click "Save". The following console output will appear:

    9) The following dashboards will be created:

    Openstack Advanced

    Openstack Basic

    10)Sample newOpenStack Basicdashboard:

    References

    View Article
  • <a rel="noopener,nofollow" target="_blank" href="https://github.com/vmware/pyvmomi/tree/master/docs">VMware on GithubDocumentation</a>

    Monitor, visualize and alert on your VMware virtual machines using the vSphere SDK with this TrueSight Pulse VMware API plugin.

    Prerequisites

    Supported OS: Linux, Windows, OS X

    VMware vSphere 4.1 or later

    TrueSight Pulse meter 4.2.4 or later

    To install new meter go to 'Settings-&gt; Installation' or see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/sections/200634331-Installation">instructions</a>.

    To upgrade the meter to the latest version see <a rel="noopener,nofollow" target="_blank" href="https://help.truesight.bmc.com/hc/en-us/articles/201573102-Upgrading-the-Boundary-Meter">instructions</a>.

    Metrics Collected:

    VMware_SYSTEM_CPU_USAGE_AVERAGE

    VMware_SYSTEM_CPU_USAGE_MAXIMUM

    VMware_SYSTEM_MEMORY_ACTIVE_MAXIMUM

    VMware_SYSTEM_MEMORY_CONSUMED_AVERAGE

    VMware_SYSTEM_DISK_READ_AVERAGE

    VMware_SYSTEM_DISK_WRITE_AVERAGE

    VMware_SYSTEM_NETWORK_BYTES_TX_AVERAGE

    VMware_SYSTEM_NETWORK_BYTES_RX_AVERAGE

    VMware_SYSTEM_NETWORK_PACKETS_TX_SUM

    VMware_SYSTEM_NETWORK_PACKETS_RX_SUM

    How To Install the VMware Plugin

    Plugin Setup

    Python 2.7

    <a rel="noopener,nofollow" target="_blank" href="https://wiki.python.org/moin/BeginnersGuide/Download">Python</a> is required. We support versions2.7.5 to 2.7.11 (2.7.12 will not work). For more information please see the plugin <a rel="noopener,nofollow" target="_blank" href="https://raw.githubusercontent.com/boundary/meter-plugin-vmware/master/README.md">README.md</a>.

    For Windows

    Add Python and Python scripts to PATH environment variable

    1. Select Start, select Control Panel. double click System, and select the Advanced tab.

    2. Click Environment Variables.

    3. In the Edit System Variable (or New System Variable) window, specify the value (installed Python directory and "scripts" directory) of the PATH environment variable.

    Example: C:\Python27\Scripts;C:\Python27\

    4. Reopen Command prompt window, and check Python version.

    c:\python --version

    Installing the plugin

    1) Log into the <a rel="noopener,nofollow" target="_blank" href="https://pulse.truesight.bmc.com/home">BMC TrueSight Pulse console</a>.

    2) Go to Settings &gt; Plugins

    3) Click on 'Get Plugins'.

    4)Scroll to 'vmware' and click 'Install'.

    5) Next, Pulse will provide a list of meters to associate to the plugin. Please select a meter. Now an "Add a plugin..." drop down box will display. Please click and select 'vmware':

    6)You will be prompted to "Add a vCenter".

    7) You can select default settings or update per your configuration. The "host" value is the name to display in the legend for the metrics data. It shoulddefault to the hostname of the server. Click "OK". Below is a sample configuration.

    8)The following dashboard will be created:

    Virtual Machines Summary

    References

    View Article

Curious about BMC Software?

Anonymously Ask BMC Software Any Question

Ask Anonymous Question

×
Rate your company