Introducci贸n

1

Lo que aprender谩s sobre DevOps con GitLab

2

驴Qu茅 es Devops?

3

El ciclo de vida del Devops

4

Introducci贸n a Gitlab

5

Gitlab vs Github

Administraci贸n

6

Autenticaci贸n

7

Grupos

8

Autorizaci贸n

9

Auditor铆a

10

Proyectos

Planificaci贸n

11

Tipos de desarrollo

12

Planificaci贸n en Gitlab-Issues

13

Planificaci贸n en Gitlab-Etiquetas

14

Planificaci贸n en Gitlab-Pesos

15

Planificaci贸n en Gitlab-Milestones

16

Planificaci贸n en Gitlab-Boards

17

Planificaci贸n en Gitlab-Service Desk

18

Planificaci贸n en Gitlab-Quick actions

Verificaci贸n

19

Inicializaci贸n del repositorio

20

Merge requests

21

Profundizando en Merge requests

22

Continuous Integration-CI

23

Gitlab CI

24

Automatizacion con GitLab Cl

25

Validacion de la configuracion con GitLab Cl

26

gitlab-ci.yml

27

Gitlab pages

28

Implementando Gitlab pages

29

驴Qu茅 es el Desarrollo 脕gil?

30

Gitlab autodevops

31

Implementando GitLab autodevops

32

Habilitando autodevops

Empaquetaci贸n

33

Gitlab container registry

34

Introducci贸n a contenedores

Seguridad

35

Introducci贸n a DevSecOps

36

Firmas de seguridad

37

Pruebas est谩ticas de seguridad

38

Escaneo de contenedores

39

Escaneo de dependencias

40

Pruebas din谩micas de seguridad

41

Gitlab security dashboard

Distribuci贸n

42

Continuous Delivery (CD)

43

Ambientes

44

Review apps

45

Estrategias de Distribuci贸n

46

Feature Flags

47

Rollback

Monitoreo

48

驴Por qu茅 monitorear?

49

M茅tricas de desempe帽o (performance metrics)

50

M茅tricas de salud (health metrics)

51

Metricas de equipo

52

Rastreo de errores

Conclusiones

53

驴Por qu茅 desarrollar con Gitlab?

You don't have access to this class

Keep learning! Join and start boosting your career

Aprovecha el precio especial y haz tu profesi贸n a prueba de IA

Antes: $249

Currency
$209
Suscr铆bete

Termina en:

2 D铆as
9 Hrs
19 Min
28 Seg

Rastreo de errores

52/53
Resources

Why is error tracing essential in monitoring?

Error tracing is an essential part of application monitoring. Understanding what errors are occurring on our customers' devices allows us to continuously improve and adjust our software. While we monitor health and performance metrics, it is crucial to know what part of the code is generating errors. This is even more critical when our audience is non-technical, as it makes it difficult to try to reproduce the error based simply on user descriptions of the problem.

How can Sentry help you with bug tracking?

Sentry is a powerful tool for bug tracking integration. This open source platform allows both the use of your infrastructure and the private management of your own server. The integration with Sentry and GitLab (GitClear) allows us to quickly identify bugs, browser details, and other device data, leading us exactly to the problem.

How do I integrate with GitLab?

  1. Acquire your API ID from Sentry: We generate a project in Sentry and set up our account to get the necessary data for the API.

  2. Configure GitLab with Sentry: In GitLab, we activate the option to communicate with Sentry by entering the authentication token and selecting the corresponding project.

  3. Set appropriate permissions: Limit token permissions to only those necessary (must include project and event:write), avoiding unnecessary exposure.

  4. Verify the connection: With all the data in place, we connect both platforms and test the integration by generating a test event.

What information can you get about errors?

The integration between Sentry and GitLab allows any error generated to be reported with:

  • Error details: type of error and line of code responsible.
  • Device information: Browser and operating system where the error occurred.
  • Impact of the error: Number of affected users and recurrence of the error.

In addition, GitLab will display these bugs in its interface, allowing you to see in detail their origin and how they may have impacted users.

Why is it critical to have visibility into bugs?

Without proper monitoring, bugs can anger users and damage your business. Efficient bug tracking and resolution facilitates the implementation of constant improvements and ensures that users have the best possible experience with your application.

That's why it's vital to have tracking processes in place that enable continuous integration, as Sentry does, to maintain robust applications and efficiently manage issues before they become major inconveniences for users. If you ever have problems with integration, remember that you can consult or share your experiences in the comments - keep learning and improving!

Contributions 6

Questions 1

Sort by:

Want to see more contributions, questions and answers from the community?

Wooow! La herramienta de SENTRY es incre铆ble, inmediata-mente la voy a implementar en mis proyectos!!!
Platzi 鉂わ笍 DevOps

Hoy en d铆a esta en la opci贸n Monitor->Error Tracking

falto ocultar el token.

Genial, hoy he conocido una nueva aplicaci贸n para ser m谩s pro en el desarrollo de aplicaciones.

Super interesante, esto en verdad hace una gran diferencia al momento de hacer monitoreo.

Una muy buena herramienta!