Monitoring and Metrics - chrisdacel/Backend_EcoRisaralda GitHub Wiki

The Conexión EcoRisaralda system implements a set of monitoring strategies and metric collection in order to ensure its proper functioning, detect errors in a timely manner, and analyze user behavior within the platform.

Tools

Development and programming

  • Laravel: Backend framework used for system logic and request management.
  • React: Used for a dynamic and interactive user interface.
  • MySQL: Database management system for information storage.

Document management

  • GitHub: Project version control and documentation in the Wiki.
  • Technical documentation and manuals organized within the repository.

Monitoring and deployment

  • Web server: Responsible for hosting the system and handling requests.
  • Laravel logs: Record of errors, exceptions, and important system events.
  • Server logs: Allow identification of infrastructure-level failures.

Documentation and collaboration

  • Use of the repository Wiki to document processes, architecture, and functionalities.
  • Collaborative work through version control.

System metrics

Below are the main metrics implemented in the system and their source:

Registered users

Allows knowing the total number of users on the platform.

Metric source:

Obtained directly from the MySQL database, specifically from the users table.

Example query:

SELECT COUNT(*) FROM users;

Logins

Measures the number of accesses to the system by users.

Metric source:

Obtained from Laravel's authentication system. It can be recorded through logs or an additional table that stores accesses (for example, login_logs).

Usage:

Allows analyzing the frequency of platform usage.

Tourist site posts

Indicates the number of tourist places registered in the system.

Metric source:

Obtained from the database, in the table corresponding to tourist places (for example, turistic_places).

Example query:

SELECT COUNT(*) FROM turistic_places;

Created ecotourism events

Measures the number of events registered on the platform.

Metric source:

Obtained from the events table in the database.

Example query:

SELECT COUNT(*) FROM events;

System errors

Allows identifying failures and issues within the system.

Metric source:

Obtained from logs automatically generated by Laravel.

Location:

storage/logs/laravel.log

Content:

Includes errors, exceptions, connection failures, and issues in system execution.

System performance

Evaluates the speed and efficiency of the application.

Metric source:

  • Browser tools (loading times in React)
  • Server response (Laravel)
  • Server logs

Usage:

Allows identifying high loading times and optimizing the user experience.

User activity

Allows analyzing user behavior within the system.

Metric source:

Obtained through user interaction with the system, such as:

  • Creation of posts
  • Event registration
  • Logins

Usage:

Helps understand which functionalities are most used.

Monitoring strategy

System monitoring is carried out through:

  • Periodic queries to the database
  • Review of logs generated by Laravel
  • Server supervision
  • Analysis of user behavior on the frontend

Monitoring objective

The purpose of system monitoring is to:

  • Ensure application stability
  • Detect errors early
  • Improve user experience
  • Optimize system performance
  • Support data-driven decision making

Conclusion

The use of metrics in the Conexión EcoRisaralda system allows maintaining proper control over its operation, facilitating problem identification and continuous improvement of the platform.