1. A method of tracking a plurality of software calls in an enterprise environment, the method comprising:
tracking, during a runtime operation of the enterprise environment, layers through which each of the plurality of software calls passes, the tracking including
logging each of a plurality of physical components involved in each of the plurality of software calls;
annotating each of the plurality of physical components with metadata associated with each of the physical components;
logging each of a plurality of logical components involved in each of the plurality of software calls;
annotating each of the plurality of logical components with metadata associated with each of the logical components; and
logging a reliance of each of the plurality of the physical components and the logical components on others of the plurality of the physical components and the logical components; and
generating, using one or more processors, a dependency map indicating the layers tracked in each of the plurality of software calls.
2. The method of claim 1, wherein the dependency map further includes indicating the reliance of each of the plurality of the physical components and the logical components on others of the plurality of the physical components and the logical components underlying each of the plurality of software calls.
3. The method of claim 1, wherein the dependency map further indicates each of the plurality of physical components and the logical components tracked in the plurality of software calls.
4. The method of claim 1, further comprising:
logging each of a plurality of geographical regions for each of the plurality of physical components involved in each of the plurality of software calls; and
annotating each of the plurality of geographical regions with metadata associated with each of the plurality of geographical regions.
5. The method of claim 4, wherein the dependency map further indicates each of the plurality of geographical regions tracked in each of the plurality of software calls.
6. The method of claim 1, wherein the annotating of each of the plurality of physical components with metadata includes:
recording a version of code under which each of the plurality of physical components is running; and
recording each of one or more applications running on each of the plurality of physical components.
7. The method of claim 1, wherein the annotating further includes:
determining and recording a path accessed by each of the plurality of software calls to a subsequent one of the plurality of the physical components and the logical components from a prior component; and
recording a time to access each path.
8. The method of claim 1, further comprising:
making a determination of any errors encountered during the tracking; and
based on the determination that errors were encountered, logging each of the errors.
9. The method of claim 1, wherein each of the plurality of software calls can be tracked beginning at any point within the enterprise environment.
10. The method of claim 1, further comprising:
assigning a unique identifier to at least ones of the plurality of software calls; and
performing statistical analysis on the at least ones of the plurality of software calls.
11. The method of claim 1, further comprising:
preparing an aggregated call-trace output from the tracking; and
preparing generalized statistics regarding the enterprise environment.
12. A system to track a plurality of software calls in an enterprise environment, the system comprising:
a cluster of harvesters, having one or more processors to track, during a runtime operation of the enterprise environment, layers through which each of the plurality of software calls passes, the tracking to include
logging each of a plurality of physical components involved in each of the plurality of software calls;
annotating each of the plurality of physical components with metadata associated with each of the physical components;
logging each of a plurality of logical components involved in each of the plurality of software calls;
annotating each of the plurality of logical components with metadata associated with each of the logical components; and
logging a reliance of each of the plurality of the physical components and the logical components on others of the plurality of the physical components and the logical components; and
one or more reporters in electronic communication with the cluster of harvesters to generate a dependency map indicating the layers tracked in each of the plurality of software calls.
13. The system of claim 12, further comprising a data analysis service module to perform statistical analysis on at least one of the plurality of software calls, the statistical analysis being based on the tracked layers within the enterprise environment.
14. The system of claim 12, wherein the one or more reporters is further to include in the dependency map the reliance of each of the plurality of the physical components and the logical components on others of the plurality of the physical components and the logical components underlying each of the plurality of software calls.
15. The system of claim 12, wherein the one or more reporters is further to include in the dependency map each of the plurality of physical components and the logical components tracked in the plurality of software calls.
16. The system of claim 12, wherein the cluster of harvesters is further to:
determine and record a path accessed by each of the plurality of software calls to a subsequent one of the plurality of the physical components and the logical components from a prior component; and
record a time to access each path.
17. A method of tracking a plurality of software calls in an enterprise environment, the method comprising:
tracking, during a runtime operation of the enterprise environment, layers through which each of the plurality of software calls passes, the tracking including
logging each of a plurality of physical components involved in each of the plurality of software calls;
logging each of a plurality of logical components involved in each of the plurality of software calls; and
logging a reliance of each of the plurality of the physical components and the logical components on others of the plurality of the physical components and the logical components; and
generating, using one or more processors, a dependency map indicating the layers tracked in each of the plurality of software calls.
18. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform an operation, the operation comprising:
tracking, during a runtime operation of the enterprise environment, layers through which each of the plurality of software calls passes, the tracking including
logging each of a plurality of physical components involved in each of the plurality of software calls;
annotating each of the plurality of physical components with metadata associated with each of the physical components;
logging each of a plurality of logical components involved in each of the plurality of software calls;
annotating each of the plurality of logical components with metadata associated with each of the logical components; and
logging a reliance of each of the plurality of the physical components and the logical components on other of the plurality of the physical components and the logical components; and
generating, using the one or more processors, a dependency map indicating the layers tracked in each of the plurality of software calls
19. The non-transitory computer-readable storage medium of claim 18, wherein the operation further comprises:
logging each of a plurality of geographical regions for each of the plurality of physical components involved in each of the plurality of software calls; and
annotating each of the plurality of geographical regions with metadata associated with each of the plurality of geographical regions.
20. The non-transitory computer-readable storage medium of claim 18, wherein the operation further comprises:
determining and recording a path accessed by each of the plurality of software calls to a subsequent one of the plurality of the physical components and the logical components from a prior component; and
recording a time to access each path.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. An injection apparatus in a cold chamber die casting molding machine configured to supply molten metal of a light metal material into a material supply mouth of an injection sleeve, the injection sleeve having a plunger injection device configured to inject the molten metal using an inserting plunger, the injection apparatus comprising:
a melting device configured to melt the light metal material, the melting device comprising:
a billet supplying device configured to replenish the molten metal using a plurality of cylindrical rod-shaped billets of the light metal material,
a billet inserting device disposed adjacent to the billet supplying device, the billet inserting device configured to move each billet forward with the inserting plunger andor to retreat the inserting plunger a distance which exceeds an overall length of each billet,
a melting cylinder situated adjacent to the billet supplying device obverse to the billet inserting device, the melting cylinder including a cylinder bore having an inside diameter which does not allow most of the cylinder bore to come into contact with a front end of each billet, the melting cylinder configured to accommodate the plurality of billets moved forward by the inserting plunger and to melt each billet from the front end of said billet to produce several shots of molten metal,
a cooling member disposed between the billet supplying device and the melting cylinder, the cooling member having a through hole and a cooling duct the cooling duct configured to circulate cooling liquid around the through hole, the cooling member configured to cool the billets, and
a cooling sleeve disposed between the cooling member and the melting cylinder, the cooling sleeve having an annular groove with a diameter larger than a diameter of the through hole, the annular groove configured to cool the molten metal and to form an annular seal of solidified molten material on a periphery of the billets; and
a molten metal feeding member configured to pour molten metal from the melting device to the plunger injection device, the molten metal feeding member including a material supplying hole configured to pour the molten metal from a distal end of the cylinder bore of the melting cylinder to the material supply mouth,
wherein the melting device is configured to meter the molten metal by pushing each billet with the inserting plunger and supplying one shot of the molten metal into the injection sleeve after the plunger injection device makes the inserting plunger retreat for replenishing.