Secure support of customization scripts using pipelining
In one embodiment, a device performs a detection stage of an automated instrumentation pipeline during which the device detects an application server type by examining a command line of a process of an application. The device performs, based on the application server type, an extraction stage of the automated instrumentation pipeline during which the device extracts application server attributes. The device performs, based on the application server attributes, a naming stage of the automated instrumentation pipeline during which the device forms a naming hierarchy for processes of the application. The detection stage, the extraction stage, and the naming stage of the automated instrumentation pipeline do not have access to a controlled space of the application. The device inserts, based in part on the naming hierarchy, arguments into command lines of processes of the application that cause the processes of the application to be instrumented at runtime.
1. A method comprising:
performing, by a device, a detection stage of an automated instrumentation pipeline during which the device detects an application server type by examining a command line of a process of an application;
performing, by the device and based on the application server type, an extraction stage of the automated instrumentation pipeline during which the device extracts application server attributes;
performing, by the device and based on the application server attributes, a naming stage of the automated instrumentation pipeline during which the device forms a naming hierarchy for processes of the application,
wherein the detection stage, the extraction stage, and the naming stage of the automated instrumentation pipeline do not have access to a controlled space of the application; and
inserting, by the device and based in part on the naming hierarchy, arguments into command lines of processes of the application that cause the processes of the application to be instrumented at runtime.
2. The method as in claim 1 , wherein the controlled space of the application comprises at least one of: a file system or a network connection associated with the application.
3. The method as in claim 1 , wherein the application server type comprises at least one of: Tomcat, JBoss, Glassfish, WebLogic, or WebSphere.
4. The method as in claim 1 , further comprising:
injecting a preload library into each process of the application, to capture command line arguments of that process.
5. The method as in claim 1 , wherein processes of the application that perform a same function are grouped by the naming hierarchy as a single tier.
6. The method as in claim 1 , wherein the device performs the naming stage of the automated instrumentation pipeline according to one or more defined naming rules.
7. The method as in claim 1 , further comprising:
disabling instrumentation for a portion of the application, using the naming hierarchy.
8. The method as in claim 1 , wherein the detection stage, the extraction stage, and the naming stage are performed in a sandbox environment.
9. The method as in claim 1 , further comprising:
constructing an attribute map for a particular process of the application indicative of a process identifier, its command line arguments, environment variables, and a current working directory, wherein the device performs the detection stage on the particular process based in part on the attribute map.
10. The method as in claim 1 , wherein the application is a Java application.
11. An apparatus, comprising:
one or more network interfaces;
a processor coupled to the one or more network interfaces and configured to execute one or more processes; and
a memory configured to store a process that is executable by the processor, the process when executed configured to:
perform a detection stage of an automated instrumentation pipeline during which the apparatus detects an application server type by examining a command line of a process of an application;
perform, based on the application server type, an extraction stage of the automated instrumentation pipeline during which the apparatus extracts application server attributes;
perform, based on the application server attributes, a naming stage of the automated instrumentation pipeline during which the apparatus forms a naming hierarchy for processes of the application,
wherein the detection stage, the extraction stage, and the naming stage of the automated instrumentation pipeline do not have access to a controlled space of the application; and
insert, based in part on the naming hierarchy, arguments into command lines of processes of the application that cause the processes of the application to be instrumented at runtime.
12. The apparatus as in claim 11 , wherein the controlled space of the application comprises at least one of: a file system or a network connection associated with the application.
13. The apparatus as in claim 11 , wherein the application server type comprises at least one of: Tomcat, JBoss, Glassfish, WebLogic, or WebSphere.
14. The apparatus as in claim 11 , wherein the process when executed is further configured to:
inject a preload library into each process of the application, to capture command line arguments of that process.
15. The apparatus as in claim 11 , wherein processes of the application that perform a same function are grouped by the naming hierarchy as a single tier.
16. The apparatus as in claim 11 , wherein the apparatus performs the naming stage of the automated instrumentation pipeline according to one or more defined naming rules.
17. The apparatus as in claim 11 , wherein the process when executed is further configured to:
disable instrumentation for a portion of the application, using the naming hierarchy.
18. The apparatus as in claim 11 , wherein the detection stage, the extraction stage, and the naming stage are performed in a sandbox environment.
19. The apparatus as in claim 11 , wherein the process when executed is further configured to:
construct an attribute map for a particular process of the application indicative of a process identifier, its command line arguments, environment variables, and a current working directory, wherein the apparatus performs the detection stage on the particular process based in part on the attribute map.
20. A tangible, non-transitory, computer-readable medium storing program instructions that cause a device to execute a process comprising:
performing, by the device, a detection stage of an automated instrumentation pipeline during which the device detects an application server type by examining a command line of a process of an application;
performing, by the device and based on the application server type, an extraction stage of the automated instrumentation pipeline during which the device extracts application server attributes;
performing, by the device and based on the application server attributes, a naming stage of the automated instrumentation pipeline during which the device forms a naming hierarchy for processes of the application,
wherein the detection stage, the extraction stage, and the naming stage of the automated instrumentation pipeline do not have access to a controlled space of the application; and
inserting, by the device and based in part on the naming hierarchy, arguments into command lines of processes of the application that cause the processes of the application to be instrumented at runtime.