Automatic application discovery is driven by the way end users access and request services from your business applications. End users access the web application through a URL, and App Visibility provides a way to name applications by identifying common URL construction and patterns.
You, as an application specialist, can configure application discovery so that you can group requests with a common purpose under one application name, and separate requests with different purposes accordingly.
For example, suppose users access your application through one of the following URLs:
Depending on your requirements, you can group all of these requests under one application name, My Company, or separate them under different application names: My Company news, My Company blog, and My Company photos.
You can also identify and discard requests that are not relevant to your application monitoring environment, for example, requests that originate from the application servers and not from end users.
This topic describes the following topics:
The name of an automatically discovered application is determined by the application URL. You can configure the application discovery based on pattern matching in the domain, path, or both. The parts of the URL are displayed in the following diagram.
Parts of a URL
The domain part of the URL includes the host name (www), subdomain (if applicable), domain (example), and the top-level domain (com).
The path part of the URL is the full path to the resource. For example, the path can include the directory (weather) and file (today.jsp) names.
For configuring App Visibility application discovery, the protocol or query parts of the URL are not used.
You can tune the application discovery, grouping some applications together, separating some, and discarding those that are not useful for your evaluation. Define patterns in the application URL to configure the application discovery.
For more examples, see Examples of application discovery rules, below.
Select Map to name, and enter a name or name pattern, or select Discard to remove the application.
If you used a wildcard (*) in the Domain or Path fields, you can enter the wildcard as part of the application name. In the application name, the wildcard represents the same string that it represents in the domain or path.
For more examples, see Examples of application discovery rules, below.
Note
Ensure that the resulting application name is no longer than 255 characters. Application names greater than 255 characters are not displayed in the Operations Management console.
Click the Enter icon to confirm the addition of the rule.
Warning
After you enter or edit a rule, it is not saved in the system until you click the Save button.
The following examples show how to define rules to show descriptive application names:
Domain: *.mycompany.com
Map to name: My Company *
Domain: *.mycompany.com
Map to name: My Company
Path: /app/*
Only if domain is: corporate-intranet.com
Map to name: *
Path: /support-console
Discard
Rule | Description | Example | ||
---|---|---|---|---|
Order | Match | Action | ||
1 | Domain: www.*.com | Map to name: * | If a domain starts with www. and ends with .com, use the subdomain and domain part of the URL as the application name. | For http://www.mycompany.com/today, the application name is mycompany. |
2 | Domain: *.com | Map to name: * | If a URL domain ends with .com, use everything before this top-level domain part of the URL as the application name. | For https://blog.mycompany.com/today, the application name is blog.mycompany. |
3 | Domain: localhost | Discard | Discard requests that originate from the application servers. | The http://localhost/test request is not part of the system. |
4 | Domain: 127.0.0.1 | Discard | Discard requests that originate from the application servers. | The http://127.0.0.1/test request is not part of the system. |
5 | Domain: [::1] | Discard | Discard requests that originate from the application servers. | The http://[::1]/test request is not part of the system. |
6 | Domain: * | Map to name: * | Use the domain part of the URL as the application name. | For http://mycompany.org/today, the application name is mycompany.org. |
Perform one or more of the following procedures:
Setting up applications for monitoring
Setting up and managing synthetic transaction monitoring
2 Comments
Scott Eshleman
Sara Kamen