Redis Monitoring Metrics

https://www.datadoghq.com/blog/how-to-monitor-redis-performance-metrics/

Advertisements

Monitoring

Hiểu về Monitoring Metrics

Thiết lập Alert Policies

Phân chia cấp độ Alert Critical, High hoặc Normal.

Notification alert group có thể phân chia theo cấp độ alert (Critical, High, Normal) hoặc là cấp độ Service cụ thể.

Một service cần định nghĩa những alert nào cần quan tâm và đưa vào Notification alert group.

Các alert giúp phát hiện sự cố sau khi nó đã xảy ra. Tuy nhiên tốt hơn hết là định nghĩa các policy dự đoán trước sự cố có xảy ra hay không.

Refers:

Redis monitoring metrics

https://www.datadoghq.com/blog/how-to-monitor-redis-performance-metrics/

CICDCD

View story at Medium.com

Định nghĩa Continuous Integration

Định nghĩa Continuous Delivery

Định nghĩa Continuous Deployment

Một định nghĩa về Continuous Deployment pipeline:

A CD pipeline delivers, as per business needs, quality products frequently and predictably from test to staging to production in an automated fashion.

Quality

Frequently

Predictability

Continuous Delivery Pipeline Phase:

  1. Component Phase: library built
  2. Subsystem Phase: microservices, database, independent deployed, … Ex: gRPC
  3. System Phase: ex: Dataflow
  4. Production Phase: ZDD zero downtime deployment

SHIFT LEFT, DEVSECOPS in Software Development Life Cycle (SDLC)

TESTINGs

Testing : Unit test, Integration test, Regression test, Acceptance test, UI test, Functional test

Functional test: all customer use case: internationality (I18N), localization (L10N), data quality, accessibility, negative scenarios, product functions per customer expectations.

Performance test: benchmark

Security test:  discover security vulnerabilities. Ex: check 3rd-party libraries (OSS open source software)

Smoke test : subset of integration, performance, security test suite. Integration smoke, performance smoke, DAST smoke, A/B test

View story at Medium.com

REFERS:

  1. https://www.atlassian.com/continuous-delivery/ci-vs-ci-vs-cd <— giải thích một cách tổng quát và dễ hiểu về CI/ CD.
  2. https://www.atlassian.com/continuous-delivery/pipeline <— giải thích các phase của continuous delivery.
  3. https://www.infoworld.com/article/3271126/ci-cd/what-is-cicd-continuous-integration-and-continuous-delivery-explained.html  <— nêu các bước hoạt động cơ bản của một CICD tool.
  4. https://medium.com/@nirespire/what-is-cicd-concepts-in-continuous-integration-and-deployment-4fe3f6625007 <— đưa ra các project ví dụ cụ thể sử dụng các CICD tools.
  5. http://www.getlaura.com/testing-unit-vs-integration-vs-regression-vs-acceptance/  <— giải thích unit test, integration test, regression test và acceptance test.

Đang đọc:

https://martinfowler.com/articles/continuousIntegration.html

https://www.synopsys.com/blogs/software-security/agile-cicd-devops-glossary/

https://viblo.asia/p/ci-cd-va-devops-07LKXYXDZV4

https://jenkins.io/

https://www.infoworld.com/article/3239666/devops/what-is-jenkins-the-ci-server-explained.html

https://www.tutorialspoint.com/jenkins/jenkins_overview.htm

http://blog.jonasbandi.net/2010/09/acceptance-vs-integration-tests.html

https://stackoverflow.com/questions/4904096/whats-the-difference-between-unit-functional-acceptance-and-integration-test

 

 

 

 

View story at Medium.com

View story at Medium.com

View story at Medium.com

Versioning

Major.Minor.Patch.BuildNumber

Given a version number MAJOR.MINOR.PATCH, increment the:

  1. MAJOR version when you make incompatible API changes
  2. MINOR version when you add functionality in a backward-compatible manner
  3. PATCH version when you make backward-compatible bug fixes.
  4. BUILD NUMBER: CI/CD tool (ex: GoCD) is responsible for making the number change.

Refers: