> Markdown version of [/jobs/ext/3904198-observability-and-service-insights-making-our-applications-measurable-understandable-and-reliable](https://www.wearedevelopers.com/jobs/ext/3904198-observability-and-service-insights-making-our-applications-measurable-understandable-and-reliable). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Observability and service insights: making our applications measurable, understandable and reliable - **Company:** Melexis - **Location:** Ieper, Belgium - **Contract:** Internship / Graduate position - **Skills:** Data Visualization, DevOps, Monitoring of Systems, Python (Programming Language), Prometheus, Web Applications, Grafana, Reliability of Systems, Kubernetes - **Published:** October 25, 2026 - **Apply:** https://www.careerjet.be/jobad/beea29b6798768c511013bf74a2c707536 ## About the Role * Student in Bachelor or Master in IT * Interest in software reliability, monitoring and operations (DevOps / SRE) * Minimal: good Python programming skills, understanding of how web applications work * Preferably: first experience with monitoring or observability tools (e.g. OpenTelemetry, Prometheus, Grafana), containers/Kubernetes, or data visualisation ## Description To build and run reliable applications, teams need to understand how those applications behave in production: how they perform, how they are used, where they fail, and whether they meet user expectations. Today, monitoring data is spread across tools and applications, and each team collects it differently. There is no common way to turn that data into useful insight. The student will work towards a consistent, lightweight observability approach for our applications. This covers technical signals (metrics, logs, traces) and application-level insights, such as usage, business metrics and service levels. The approach will first be piloted on one or more applications, then packaged so other teams can adopt it easily. More specifically, you will: * Assess the current state of monitoring and observability across applications * Define a common baseline: which metrics, logs and traces every application should provide, and how * Add meaningful application and business metrics beyond infrastructure health * Define and track service levels (e.g. SLOs, error budgets) and give visibility through dashboards and service scorecards * Pilot the approach, then provide templates, libraries and documentation for wider adoption