January 2019 Summaries

Sentry and nginx are used together to trace errors by generating a unique request ID that is passed along in each request. This allows for stitching together logs from multiple systems, such as load balancers and web servers, to help identify the root cause of performance issues. The request ID is configured in nginx's access logs and then bound to the Sentry SDK, enabling it to be used as a tag in Sentry's UI. With this setup, errors can be tracked across different systems and correlated with traditional access logs, providing deeper understanding and context to debug better.

Kubernetes is a container orchestration system that automates deployment and scaling processes for containers. It was initially unfamiliar to the author, who had heard people talk about it but didn't understand what it was. The author learned Kubernetes by following tutorials, reading books, and asking questions to experts in their organization. They found that understanding Kubernetes was an accessible concept once they grasped its role in automating manual processes for container deployment and scaling. With the help of tools like Minikube and resources from Kelsey Hightower, the author gained a solid foundation in Kubernetes and began to appreciate its flexibility and efficiency benefits.

Sentry can be used to debug front-end errors by utilizing fingerprints, breadcrumbs, tags, and flags. Fingerprints group similar error events together, making it easier to identify and resolve issues. Breadcrumbs provide a trail of events that occurred before the issue, helping to determine the cause of the bug. Tags allow for quick search and observation on how errors impact users, while flags enable recording complex state as additional data. By customizing these properties, developers can gain more visibility into their application's behavior and optimize Sentry's debugging capabilities.

Kathrin Bierhaus has joined Sentry's Vienna office after 8 years in a business law firm where she worked as a team assistant and business development assistant. She is still trying to prove her non-Austrian identity. In her free time, Kathrin enjoys entertaining her colleagues with K-Pop and taking care of her pets, including virtual dwarves and gnomes.

Sentry Workflow — Alert phase focuses on custom alerts to provide immediate visibility into errors impacting users and help teams work efficiently with the existing workflow. Sentry's notifications give developers actionable insights to proactively decide the next step, allowing them to fix multiple instances at once and streamline their workflow. Custom alerts can be tailored according to an organization's specific workflow, stack, communication style, and objectives, making it easier to receive targeted notifications without disruption. With customizable rules and conditions, teams can set up alerts based on project-specific rules, customer behavior, or error spike duration, allowing for increased accountability and timely remediation of issues.

Bruno Garcia has joined Sentry as a Software Engineer in the Vienna office. He brings over 10 years of professional experience in C# and .NET application development, having worked in various countries including the Czech Republic, Brazil, and Austria. In his free time, Bruno enjoys traveling, sailing, and learning new languages such as German and Rust.

The June Sentry Scouts Meetup focused on bots and their potential use cases in various industries. Bots can simplify processes by answering FAQs quickly, passing customers to human agents when necessary, and lightening the mood with humor. Potential use cases for bots are seemingly endless, including customer service, HR, project management, restaurant and travel reservations, and even stock trading through chatbots. Developers should consider adding personality to their bots to reinforce brand identity. Training bots is challenging but can be improved by using natural language processing (NLP) and rules-based approaches. A hybrid of machine learning and rules has shown good results in bot development.