Buried point
Record class or method call information and error log information;
The information and status of the call are displayed in the form of data in a table. Error logs are presented in the form of graphs, charts and detail pages. Clear and intuitive. Easy to view, find and manage.
The above picture is a screenshot of the successful docking. The picture shows: the other party's IP, the other party's method of adding a buried point, the method call status, and logview can click to view the log or the sub-method called (the sub-method also needs to add a buried point).
Project docking is very simple: because now it is automatically adding buried points, that is, adding buried points in the form of annotations, and quoting annotations requires referencing the jar package.
This is a project developed by our group and is currently only used within the company, because the company has many platforms and has been docking with other platforms for a long time (in fact, this project is made for them to facilitate their project management).
After the docking is successful, in our project, they search for the project name app.name defined by themselves, and their method of adding buried points will appear.
In fact, when I first started working on this project with buried points, I felt that it didn’t matter whether the project existed or not, because each project has its own log file. According to the previous habit, it is the most direct to look at the log file.
Later, when the project was completed, we needed to allow other platforms to access it. When I went to connect, I still had no confidence. . . . I don't know how to convince them to take the time to work on our project (because they're all busy). In the end, I still procrastinated. With my advantages (fortunately, I am a girl ("▔□▔)), I have successfully connected with the commodity platform and the order platform (I am responsible for both commodity and order platforms).
The docking of other platforms is completed, just in time for the big promotion. Taking advantage of this time, the projects docked by each platform have sent the code to production, and finally we can show the role of our project and see the whole picture. . . . .
Our projects are displayed on the large screen. Each platform searches its own burying point by searching its own defined app.name (only adding burying points to the methods that need to be monitored). Now it is not refreshed from time to time, and it needs to be searched manually. Therefore, each platform will come and search at intervals. If you see a high error rate, you can check the log on the page to see the reason. If the average time exceeds one minute, you can also directly check the log on the page to see what caused it.
Now, the company is using this project with additional buried points, and now I am more confident, haha, the visual project log management is really practical, and now I feel that the overtime work some time ago is worth it.
Manually burying points is more troublesome, but practical. Which use to add.