reportador

App Time Metrics Discussion

• Discussing the need for metrics related to App Time, which is frequently inquired about by team members.

• Emphasizing the importance of uptime metrics and how to categorize different operational aspects.

• Mentioning the assistant operations feature and its initial deliverables focused on a central operations hub.

Incident Management Features

• Proposing a bot-like feature for incident reporting and management within the system.

• Suggesting interactive options for users to inquire about App Time and SLA performance.

• Highlighting that this chatbot should be accessible via internet or VPN with proper authentication.

Integration Challenges

• Discussing integration within an existing Angular project while maintaining stability.

• Addressing concerns about not disrupting current functionalities during development.

• Planning for a structured assistant that can evolve without compromising existing systems.

Operational News Updates

• Outlining the need for a news update mechanism to keep all team members informed of changes.

• Aiming to eliminate communication gaps by providing direct updates rather than relying on word-of-mouth.

• Encouraging accountability among team members to report significant operational changes promptly.

Discussion on Operational Updates

Current Challenges

• Discussion about the lack of operational traffic and updates, highlighting a need for improvement.

• Emphasis on creating a basic structure for operational updates to facilitate communication.

• Need for dynamic updating of operational news to keep all team members informed.

Metrics and Analysis

• Importance of analyzing key metrics like QR codes and payment times for effective operations.

• Complexity in calculating SLA (Service Level Agreement) metrics based on ticket analysis.

• Mention of consulting Samad for real-time data regarding ticket statuses and SLAs.

Ticket Management

• Explanation of how tickets exceeding SLA are tracked using escalation fields in Samad.

• Discussion on the importance of accurate ticket logging to ensure proper SLA tracking with vendors.

• Highlighting the need for accountability in ticket management practices among team members.

Future Considerations

• Suggestion to create reports summarizing time taken on various tasks as part of ongoing improvements.

• Focus on centralizing tools to streamline operations and improve user experience for new team members.

• Responsibility shared among team members to keep resources updated, enhancing overall efficiency.

Overview of Application Features

• Discussion on integrating reporting features within the app, including monthly SLA and daily reports.

• Mention of evidence folders for PCI tracking and organizational considerations for deployment.

• Initial version planning with potential links and automation requests from operations.

Centralized Information Management

• Emphasis on having a single point for accessing all information to streamline processes.

• Introduction of an assistant feature that utilizes API access to gather user comments and feedback.

• Potential for users to analyze tickets more effectively based on prior knowledge.

Documentation and Knowledge Base Development

• Importance of documenting cases to build a comprehensive knowledge base over time.

• Need for clear task definitions and documentation practices as part of the workflow improvement.

• Proposal for creating specific documentation servers containing source code and detailed info.

Metrics and Reporting Enhancements

• Discussion on updating operational news sections with relevant metrics from various sources.

• Plan to develop clearer SLA reporting mechanisms once foundational elements are established.

• Consideration of graphical interface improvements based on user experience feedback.

Discussion on EPAGO 2 and Repository Management

• Discussion about the EPAGO 2 repository in Azure, emphasizing the importance of not disrupting branches.

• Mention of a specific repository called "pay maintainer" and the need to work carefully without breaking anything.

• Plan to create a branch from the repository and discuss project status by Tuesday afternoon.

Project Dependencies and Timeline Considerations

• Acknowledgment of limitations regarding dependencies and the need for careful management.

• Anticipation of PCI requirements starting around May, with most documentation already prepared.

• Collaboration with team members Faril, Fede, and Lee to manage workload effectively.

Metrics Monitoring Challenges

• Issues with monitoring metrics due to potential conflicts with dynamic routing affecting data accuracy.

• Importance of ensuring no other pipelines are interfering with metric collection.

• Suggestion to broaden dynamic routing parameters for better connectivity testing.

Next Steps in Dynamic Routing

• Recommendation to simplify dynamic routing criteria for improved performance.

• Emphasis on testing connections before making further adjustments.