Skip navigation
All Places > CA APM > Blog
1 2 3 Previous Next

CA APM

291 posts

Checklist

Upgrade CA APM

We provide Upgrade Checklists to help you plan and implement your product upgrade. The checklists include information about selecting an upgrade method, prerequisites, necessary planning, and outline critical items that you must consider, such as sizing and hardware. The checklists also guide you through the documentation, directing you to the correct pages for each procedure.

What to Read

Go to the Upgrading section of the CA APM 10.7 documentation to review the checklists.

Enterprise Manager Cluster Upgrade

Manually Upgrade CA APM

APM Software Administration Lifecycle FAQ FINAL.pdf 

 

Dear Community:

  This work is a longstanding  labor of love. Those that interact with me frequently know that I often see APM software administration as part of an ongoing ad dynamic lifecycle. While I documented what this meant for CEM, I have not done this for APM as a whole.

 

If this is helpful to you, please like this post. I welcome suggestions on improvements. Part 2 already has a first draft. 

 

Thanks 

Hal German

Thank you heiwi02 and the Education Team for doing this. I REALLY like this useful video. 

 

https://youtu.be/Hhfjvf15J5I

What's New in APM 10.7 for Team Center Video

youtu.be

This video contains new features for Team Center in APM 10.7

It is sometimes very time consuming to go down to the Data-Center and pull out a device for getting the serial number of the device, or even the service tag. It is however quite easy to extract that information from a running system (In case the Manufacturer has inserted that information into the BIOS. 

 

This blog entry will show you how to extract that information on the Linux side.

Under Windows, almost every hardware manufacturer will provide its own tool for extracting the information (Dell, HP) will need to download the Bios Diagnosis tool etc. to extract that information. So - go to the manufacturer site, and check for the tool.

 

On a Linux system, the magic tool to use is dmidecode (on all older distributions). There are geeks out there telling that using lshw is better - but keep in mind that lshw will provide details on the hardware type, and amount and where it is placed on the system, but not on the serial numbers.

 

The advantage of dmidecode is that one can provide a string to extract only the serial number, one can provide the wanted information to extract: 

 

For example when using dmidecode with a missing argument, one will see the list of specific data one can extract.

Provide the argument, and if it exists, it will be dumped to the shell. This comes in very handy when using a shell-script to automate the data extraction.

root@titan:~# dmidecode -s
dmidecode: option requires an argument -- 's'
String keyword expected
Valid string keywords are:
bios-vendor
bios-version
bios-release-date
system-manufacturer
system-product-name
system-version
system-serial-number
system-uuid
baseboard-manufacturer
baseboard-product-name
baseboard-version
baseboard-serial-number
baseboard-asset-tag
chassis-manufacturer
chassis-type
chassis-version
chassis-serial-number
chassis-asset-tag
processor-family
processor-manufacturer
processor-version
processor-frequency
root@titan:~# dmidecode -s system-product-name
Latitude E7440
root@titan:~# dmidecode -s system-serial-number
5QY****

root@titan:~# dmidecode -s baseboard-asset-tag
D20001***

root@titan:~# dmidecode -s chassis-manufacturer
Dell Inc.

 

 

Some devices on the lose do not have these information implanted. In that case, the admin will have to use the old long way to gather that information (manually). On systems where the Manufacturer has not entered the data, one can see either:

Missing data

[merjr01@apm nextcloud_prod]$ sudo dmidecode -s system-serial-number

1234567890

Note that sometimes, on String-data, one tends to find: To be filled by O.E.M. or N/A

 

dmidecode has also the possibility to list all information based on hardware type. When looking for specific hardware (for example to increase the amount of Memory for a device), one can start dmidecode -t memory to extract all details on the installed memory.
In the below example, one can see that the maximum capacity of 16GB of Ram is already installed. The below slot information show each an amount of 8GB Ram. One can also see the Manufacturer of the RAM, and more important the part number if one needs to be replaced!

 

Search for memory
jmertin@titan:~$ sudo dmidecode -t memory
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0046, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 16 GB
Error Information Handle: Not Provided
Number Of Devices: 2

Handle 0x0047, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x0046
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: SODIMM
Set: None
Locator: DIMM A
Bank Locator: Not Specified
Type: DDR3
Type Detail: Synchronous
Speed: 1600 MT/s
Manufacturer: Samsung
Serial Number: 83C0****
Asset Tag: 02143900
Part Number: M471B1G73DB0-YK0
Rank: 2
Configured Clock Speed: 1600 MT/s

Handle 0x0049, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x0046
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: SODIMM
Set: None
Locator: DIMM B
Bank Locator: Not Specified
Type: DDR3
Type Detail: Synchronous
Speed: 1600 MT/s
Manufacturer: Samsung
Serial Number: CCF6****
Asset Tag: 03151900
Part Number: M471B1G73QH0-YK0
Rank: 2
Configured Clock Speed: 1600 MT/s

 

On a rare occasion, one can also find serial numbers for specific addon-cards due to the loaded driver (binary blob).

Many intel based  WiFi Mini-PCI cards for example do that. Using lspci as seen below.

Device serial
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260
Flags: bus master, fast devsel, latency 0, IRQ 47
Memory at f7d00000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 80-19-34-ff-ff-a1-cb-33
Capabilities: [14c] Latency Tolerance Reporting
Capabilities: [154] Vendor Specific Information: ID=cafe Rev=1 Len=014 <?>
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

 

For add-on hardware which registers itself as another PCIx or USB compatible device, extracting the information will be more complex. Usually that will only work using the manufacturer provided software or drivers which can query the hardware for these details. The OS itself will only see the published API which usually does not provider any such details.

Using the storage manager for Adaptec controllers for example, one can see the following details including the Serial number.

Storage Manager details

 

=== Configuration controller 1 ! =============================================
Controllers found: 2
----------------------------------------------------------------------
Controller information
----------------------------------------------------------------------
Controller Status : Optimal
Channel description : SAS/SATA
Controller Model : Adaptec 5405
Controller Serial Number : 2D3512****
Physical Slot : 1
Temperature : 77 C/ 170 F (Normal)
Installed memory : 256 MB
Copyback : Disabled
Background consistency check : Disabled
Automatic Failover : Enabled
Global task priority : High
Performance Mode : Default/Dynamic
Defunct disk drive count : 0
Logical devices/Failed/Degraded : 1/0/0

We’re proud to announce the availability of CA App Synthetic Monitor 10.1. In this release we have made several enhancements to improve the management and security of the solution as well as updates to further improve visibility into potential performance problems.

The updates in this release include:

 

Updated User Permissions Management

With this release, we are offering more granular and transparent user permissions management. This feature will reduce the need for have accounts with the ‘login as’ permission. Sub-accounts (users) can now manage monitors, contacts or maintenance windows through their account based on the assigned roles or individual permissions.

Additional details regarding permissions management can be found in the documentation.

 

Single Sign-On and Two-Factor Authentication

To increase product security, we now support single sign-on and two-factor authentication for log-in.

 

Single Sign-On 

Individual accounts can be configured to leverage single sign-on using your corporate standard. To enable log-in through your corporate identity provider, contact CA Support. 

 

Two-Factor Authentication

For accounts who chose not to leverage single sign-on, two-factor authentication can be enabled through user preferences > security settings. In addition, a RFC6238 compliant mobile application, such as Google Authenticator or FreeOTP, will be required to complete log-in.

 

New Maintenance Window Management

We have also made several updates to improve the use and management of maintenance windows. Contacts and maintenance windows can now be organized into folders. We have also added a new text field to allow users to include additional details regarding the purpose of the maintenance window.

 

Improved Full Page Monitor Options

Full-page monitors now include an ‘alert on embedded elements errors’ option which can be found in the monitor details. With this feature, you will now be alerted if any of the page sub-elements (JavaScript files, CSS files, images) fail to load properly. This will help you to further improve page performance and load times.

 

JMeter 4.0 Support

JMeter 4.0 is now supported on our monitoring stations. To run JMeter 4.0 scripts on your On-premise station, upgrade to the latest OPMS version. JMeter 3.3 scripts are now executed using 4.0 engine. We are staying backward compatible with all uploaded JMeter scripts.

 

Zero Downtime During Updates

We have updated our On-premise tunnel component to allow for zero downtime during updates and upgrades of CA App Synthetic Monitor core servers.

 

 

 

If you have any questions regarding the latest changes, please let us know in the comments or reach out to CA Support.

Blueprint

Size It Right

Like architectural blueprints provide design information for construction, CA engineering blueprints help you plan and implement your product deployment, and size it right. CA blueprints include information about the distribution of components in a deployment. A sizing process guides you towards identifying the right blueprint. The process can include assumptions, requirements, payload calculation, and hardware resources.

 

CA blueprints are available for the following Agile Operations products:

 

Agile Operations Analytics Base Platform

The Starter deployment options support: 

  • Non-High Availability: Use this option where partial High Availability is provided for Jarvis components. 
  • High Availability: Use this option where High Availability is provided for all components.

The Scalable deployment option supports:

  • Custom Deployment. Custom Deployment lets you choose the number of nodes depending on your requirement and determine the component distribution on these nodes.

More Information:

Starter deployment

Scalable deployment

 

CA APM/Agile Operations Analytics Base Platform

The Starter deployment option supports:

  • Loads where the total number of transaction traces across Enterprise Manager clusters is less than or equal to 10 K. The Elasticsearch Master Data node stores incoming real-time and historical data.

The Scalable deployment option supports:

  • Loads where the total number of transaction traces across Enterprise Manager clusters can increase. The Elasticsearch HOT nodes store incoming real-time data and the Elasticsearch WARM nodes store historical data.

More Information:

CA APM/Agile Operations Analytics Base Platform Deployment Blueprints

 

CA Digital Experience Collector Deployment for CA APM

Deployment options are available for:

  • APM on-premise Enterprise Manager
  • APM on-premise Enterprise Manager with App Experience Analytics SaaS

A deployment blueprint provides information about the number of instances of Digital Experience Collector, Kafka, and Logstash. This calculation is based on the payload and number of requests that you gather.

More Information:

CA Digital Experience Collector Deployment Blueprint for CA APM

Introduction

This is another in a series on the Product Compatibility Matrix (PCM) database accessible at https://pcm.ca.com

 

On the PCM Help Screen is listed the mission for this project:

https://pcm.ca.com/help.php

"Our goal is to build a tool that provides the capability to quickly
search for product compatibility information across all CA products and
which is easily accessed, easy to use, secure, and up to date with
accurate and reliable release information"

 

Let's discuss how this is fulfilled in the product

 

A Quick Search Product Compatibility Tool that is Easily Accessible

PCM accesses product compatibility information quickly from your browser, tablet, mobile phone, or dishwasher while on the CA internal network or Internet. I find myself going to "old reliable" 5-10 times a day answering your questions in cases and this community. 

 

Across all CA products

CA Performance Management was quietly added recently. Currently supported products include:

 

And more can be added if there is interest!

 

Easy to use, secure, and up to date with accurate and reliable release information.

 

PCM's usability has involved over time with your feedback. This includes tool tips with context-sensitive information, filters to quickly specify information shown, search boxes for simple and complex queries, the release comparison feature, plus much more! 

 

Accounts are needed to access and change internal information. 

 

The PCM Team works with Product Management, Development, and Tech Info to get accurate and current information. An audit record exists of those that changes any information in PCM. And any incorrect information found is corrected immediately.

 

I hope that you are enjoying this series. Please add a like or comment if you do. Future suggestions for topics are welcomed 

Colorful Pencils

 

 

 

 

 

 

 

 

 

 

CA APM collects and visualizes a wide range of data from your application environment. You can now tap into that data and create your own customized dashboards with the Grafana integration for CA APM. Grafana is an open-source tool that lets you send RegEx queries to the APMSQL database over a JDBC connection. Grafana then collects the query results in a stream of JSON files, which are compiled into dashboards.

 

Let's Give it a Try: Track Response Times of Frontend Components

Suppose you want to track the response times of your frontend components and compare them side-by-side in one comprehensive chart. To do this, execute the following query in Grafana for your enabled frontend component, in this case, the /purchase component. You can also expand the query to include any other desired frontend components:

apmsql '.*thieves.*' '^Frontends.*thieves.*/purchase(?!.*?Called Backends).*Time.*' agg_value

Result:

What to Do and What to Read

Go to Using Grafana with CA APMSQL for further information about the Grafana setup process. The Grafana Getting Started Guide contains a tutorial on building your first dashboard.

Introduction

I mentioned last week about Release Comparison accessible at PCM for CA Software - Agile Operations Product Compatibility Search . It can be accessed off the main menu, 

 

 

New Functionality

Starting today, the PCM Release Comparison  feature shows components and you can filter by components. Data will be added soon for other products  accessible via PCM. Let us know what you think about this feature. 

 

Introduction:

   This is part of a new series on the Product Compatibility Matrix -- an  database to access at any time product compatibility information for a APM,SSO, IM and other products.

 

Also see PCM Features: The Overview Tab 

 

http://pcm.ca.com is the starting point to access this 

 

Release Comparison 

Starting today, you can access the Release Comparison feature  If you log in from the Internet, it will look like 

 

Click on release comparison and a ilst like below appears. Use the pull-down menu to change to another Product

 

 

 

or select CSV Export to save the results. Other features will be added to Release Comparison in time. 

 

Introduction:

 The Product Compatibility Matrix (PCM) is a system that contains a wealth of compatibility content about  APM, ADA, ASM,AXA, DOI, SAAS, and SSO. It has various features that few users know about. 

 

To access, simply go to https://pcm.ca.com/ 

 

Note that those users on the CA network will see additional features.

 

One of my favorite places to go is the Overview Tab. It shows all the components supported for a particular release.

 

Using the Overview Tab

 

Once you have clicked on the above URL, you should see something like this 

 

 

Click on the Overview UI and select your solution

 

The supported components for that release appears. You may scroll down or click on CSV Export to save a copy of the contents. And that's it. Please give it a try and let us know how you like it! 

Olina

Read All About It: WalkMe

Posted by Olina Employee Sep 4, 2018

Have you noticed the Guide me option in your Digital Experience Insights user interface? Guide me is part of our recent implementation of WalkMe, which guides you through common tasks in the product. WalkMe gives you step-by-step assistance and information as you navigate the user interface.

What To Do and What To Read

Let's get started.

  1. In the Digital Experience Insights product user interface, click Guide me.
    Guide me drop-down list
  2. Select and click a Walk-through.
    Walk-through menu
  3. Read the Walk-through information and follow the steps.
    WalkMe step

Please let us know if you have any feedback or suggestions for WalkMe!

       Introduction

        There has never been a better time to revisit this topic. The original posts may be found at:

Four Keys to Successful APM Searches: Part One 

Four Keys to Successful APM Searches: Part Two 

 

One of the issues that some Engineers, Partners, and Customers experience is not knowing how to do effective searches. They enter one term after another without success. These articles discuss techniques to yield better results.

 

What is the goal of a helpful technical knowledge search? 

The desired result is to find a source that is

- trusted

- relevant 

- current 

- appropriate for my situation. (Such as the same operating system, product release etc.)

- contains clear and helpful next steps

 

Question 1: What is my search strategy? (First Pass.)

 Knowing the results you want to achieve and working backwards can help. For example:

 

- What are my search constraints (certain time periods, vendors, releases, etc?)

- Is this a general or specific question?

- What are the search repositories best suited for my search? (CA-specific, third-party vendors, general search databases?)

- How many returned articles am I willing to go through?

 

Question 2: What type of search technical query do I have?

 

 Just like in a Community, many types of questions are asked, so it is with searches.

 

 You could require:

- An answer to a general or specific question . (Information Requests). The range of topics could be vast 

    * Error Messages, Starting/Stopping a Component, Log locations, Metric Values and what they mean, and many more

 - Details on one or more tasks. (Such as preparing for or performing an upgrade, system optimization/maintenance.) 

- A broader answer such as backup software and strategies, administration responsibilities, best practices,  and customization approaches.

 

Knowing the type of query will determine:

 

-Which sources to search

-How long to search

-Results likely to be returned

 

Question 3: What is my search strategy? (Deeper Dive.)

 

So what approaches are best for searches? Here are some to consider:

 

General>Specific or Specific>General

 

Each approach has its uses. If completely new to a topic, a general search is a good place to start to get ideas of possible keywords to search for. In some cases, that may be all that is needed. A specific search is good when you already know something on your topic -- Why won't the server component start after an upgrade from release 200.x? Sometimes "backing up" and doing an analogous search may help. (Does this happen with earlier releases and different components? Does it happen during operating or stopping? Is it load related? What is the impact of third-party components on this issue?)

 

 

Constraints

Playing around with the constraints listed above may give you greater insight on what is the optimal search. This can include:

- Data sources used

- Timeframes

- Images, Texts, or Videos returned

- Vendor for operating system , database, etc.

- Release

- Log names

- Error Messages

 

 

Search terms, search terms, search terms.
A major reason for not finding information is simply the search terms being used. Some guidelines for successful searches:

- For Java, searching on the error and the troublesome class/method may help 

- Operation being performed  and the components and screens impacted

- Include the component name/version, third-party software version, and APM version. Again try this with one of these factors and then expand to all of them.

- List what is and is not happening. (Such as no reports)

 

Next time, I will continue on this topic. Until then, happy searching! And please add below your own suggestions! 

Assessing Enterprise Manager (EM) health can be done with the help of Supportability Metrics. However, understanding which metrics to use can be difficult. To facilitate this process, the CA APM documentation team has compiled a list of the top five Supportability Metrics that impact EM performance the most.

What to Do and What to Read

Go to the Top 5 Supportability Metrics page and view the metrics summary. Quickly identify the metric path and view the metric descriptions. See which APM product, component, and version is affected and determine the performance impact. Identify the health range and troubleshooting steps. For configuration recommendations, find links to the relevant documentation.

The CA APM documentation team continues to improve your APM doc by providing a Release Comparison of all major releases. The Release Comparison gives you a comprehensive guide to the major new features in any given release. Now, you can quickly and easily review the advantages of upgrading to a new version.

What To Do and What To Read

Go to the Release Notes of any version to view the Release Comparison in an easy-to-read table. Quickly identify new features and obtain the links to the relevant documentation. 

See the latest version of the Release Comparison to compare all versions, and watch a video of the newest features: Release Comparison.

Release Comparison

Filter Blog

By date: By tag: