Shulou(Shulou.com)06/03 Report--

This article introduces the relevant knowledge of "what are the key knowledge of DevOps". In the operation of actual cases, many people will encounter such a dilemma. Next, let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

1. Deployment frequency

It is very important to maintain competitive advantage, high quality, accurate delivery of updates, new features and technology enhancements after development. The opportunity to increase delivery intensity helps to increase flexibility and better meet changing consumer needs.

Measuring the frequency of deployment on a regular basis will provide greater visibility of which improvements are successful and which parts need to be changed. If the frequency drops rapidly, it may represent other tasks or manual operations that interfere with the workflow. For sustainable growth and development, small but continuously changing deployment frequency indicators are recommended. Determine the frequency of deployment and optimize for early stages to make tests easier to manage.

two。 Deployment time

It may seem irrelevant that this metric measures how long it takes to execute a deployment, but measuring deployment time can identify potential problems. For example, if your deployment takes an hour, there must be a problem. So it's best to focus on smaller but more frequent deployments in a way that captures the build time.

3. Automated test pass rate

It is highly recommended that you use unit testing and integration testing to maximize speed. Because DevOps relies heavily on automation, useful DevOps metrics are used to measure the effectiveness of automated testing. Knowing how many code adjustments can lead to test crashes can help you take advantage of this effectively.

4. Code submission

The number of times the computing team commits the software before putting it into production can measure not only the speed of development, but also the accuracy of the code. The team should propose the scope of standard code submission that everyone should follow. A large number of commits may mean problems such as poor code quality and a lack of clear development goals. The team may be unproductive because the number of people is below the standard. It is necessary to find out the reasons for reducing or increasing the number of submissions, to maintain efficiency and project progress, and to maintain happiness among team members.

5. Unplanned work

As the name implies, in standard projects, the unplanned work rate should not exceed 25%. Too high unplanned work rates may cause unexpected errors at work, which can be more serious if they are not found early in the workflow. The rework rate is also an attempt to solve the problems in tickets.

Mean time to failure (MTTF) is the average time it takes for a defective system to run until a failure occurs. Used to track the status of unrepairable system components and to assess how long they can work before they fail. It allows the DevOps team to maintain the condition of mission-critical systems when identifying failures.

6. Application performance

Before performing a deployment, be sure to check for performance failures, unknown errors, and other problems. Monitor changes in the entire program output during and after deployment. And the use of published SQL queries, Web server calls and other program requirements. If it is normal for major adjustments to occur, you can use the monitoring tool, which can display the changes more accurately.

7. Average test time (MTTD)

When problems really arise, the point is to identify them immediately. Otherwise, when there is a serious local or large machine failure, the situation will become very serious without knowing it. Remember to set up powerful application monitoring to help you find errors easily.

8. Mean recovery time (MTTR)

The average recovery time is an index to measure the effectiveness of enterprises in solving problems. The ability to analyze the effectiveness of the business and customer experience provides the required perspective. MTTR calculates the total response time from failure to resolution and provides information about whether the client has lost control, experienced a delay, or abandoned the system. Improving it can greatly reduce the impact.

In a word, under the circumstances of high labor cost, fierce market competition, and frequent changes in user demand, DevOps is a path that must be chosen.

This is the end of the content of "what are the key knowledge of DevOps". Thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.