Naming of nodes in net framework
A system for naming a process being monitored that handles a requesting a framework such as a .NET framework. The process may be implemented by a .NET application framework within an IIS web server. The naming system allows for user readable names which are more than just numbers or indexes. The naming system is configured from a single location rather than from multiple locations, making it much easier to configure, change and update.
1. A method for monitoring a business transaction, comprising:
detecting, at a profiler, a call by an application on a first remote server to a node on a second remote server;
reporting, at the profiler, to a coordinator of the detection of the call;
determining, at the coordinator of the first remote server, whether the call should be monitored, wherein the determination is based on whether a request name of the call matches INTERNET INFORMATION SERIVCES (IIS) process or process name or Windows service name;
in response to the determination that the call should be monitored, instantiating an agent; and
automatically generating, at the coordinator, a name for the node which is determined to be monitored and based on information from the agent, the name including the name of a machine on which the node resides and the name of a logical group of nodes that includes the node being called.
2. The method of claim 1 , wherein the application runs in a .NET framework.
3. The method of claim 1 , further comprising comparing a name of the called node to a list of nodes to monitor.
4. The method of claim 3 , wherein the list of nodes includes a list of the INTERNET INFORMATION SERVICES (IIS) processes, the process names, and the Windows service names from a single list at a remote location.
5. The method of claim 1 , further comprising determining a site name associated for the node, the name of the node including the site name.
6. The method of claim 1 , further comprising:
determining multiple work processes working at same site; and
adding a process identifier to the node name.
7. The method of claim 1 , further comprising:
determining multiple work processes working at same site; and
adding a work process index to the node name.
8. The method of claim 1 , further comprising:
determining multiple work processes working at same site; and
merging the work processes into a logical node.
9. The method of claim 1 , further comprising:
determining multiple programs started at the same application; and
adding an application domain identifier.
10. A non-transitory computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform a method for monitoring a business transaction, the method comprising:
detecting, at a profiler, a call by an application on a first remote server to a node on a second remote server;
reporting, at the profiler, to a coordinator of the detection of the call;
determining, at the coordinator of the first remote server, whether the call should be monitored, wherein the determination is based on whether a request name of the call matches INTERNET INFORMATION SERIVCES (IIS) process or process name or Windows service name;
in response to the determination that the call should be monitored, instantiating an agent; and
automatically generating, at the coordinator, a name for the node which is determined to be monitored and based on information from the agent, the name including the name of a machine on which the node resides and the name of a logical group of nodes that includes the node being called.
11. The non-transitory computer readable storage medium of claim 10 , wherein the application runs in a .NET framework.
12. The non-transitory computer readable storage medium of claim 10 , further comprising comparing a name of the called node to a list of nodes to monitor.
13. The non-transitory computer readable storage medium of claim 12 , wherein the list of nodes includes a list of the INTERNET INFORMATION SERVICES (IIS) processes, the process names, and the Windows service names from a single list at a remote location.
14. The non-transitory computer readable storage medium of claim 10 , further comprising determining a site name associated for the node, the name of the node including the site name.
15. The non-transitory computer readable storage medium of claim 10 , further comprising:
determining multiple work processes working at same site; and
adding a process identifier to the node name.
16. The non-transitory computer readable storage medium of claim 10 , further comprising:
determining multiple work processes working at same site; and
adding a work process index to the node name.
17. The non-transitory computer readable storage medium of claim 10 , further comprising:
determining multiple work processes working at same site; and
merging the work processes into a logical node.
18. The non-transitory computer readable storage medium of claim 10 , further comprising:
determining multiple programs started at the same application; and
adding an application domain identifier.
19. A system for monitoring a business transaction, comprising:
a processor;
a memory; and
one or more modules stored in memory and executable by a processor to:
detect, at a profiler, a call by an application on a first remote server to a node on a second remote server;
reporting, at the profiler, to a coordinator of the detection of the call;
determining, at the coordinator of the first remote server, whether the call should be monitored, wherein the determination is based on whether a request name of the call matches INTERNET INFORMATION SERIVCES (IIS) process or process name or Windows service name;
in response to the determination that the call should be monitored, instantiating an agent; and
automatically generate, at the coordinator, a name for the node which is determined to be monitored and based on information from the agent, the name including the name of a machine on which the node resides and the name of a logical group of nodes that includes the node being called.
20. The system of claim 19 , wherein the application runs in a .NET framework.
21. The system of claim 19 , the one or more modules further executable to compare a name of the called node to a list of nodes to monitor.
22. The system of claim 21 , wherein the list of nodes includes a list of the INTERNET INFORMATION SERVICES (IIS) processes, the process names, and the Windows service names from a single list at a remote location.
23. The system of claim 19 , the one or more modules further executable to determine a site name associated for the node, the name of the node including the site name.
24. The system of claim 19 , the one or more modules further executable to:
determining multiple work processes working at same site; and
adding a process identifier to the node name.
25. The system of claim 19 , the one or more modules further executable to:
determining multiple work processes working at same site; and
adding a work process index to the node name.
26. The system of claim 19 , the one or more modules further executable to:
determining multiple work processes working at same site; and
merging the work processes into a logical node.
27. The system of claim 19 , the one or more modules further executable to:
determining multiple programs started at the same application; and
adding an application domain identifier.