Skip to content

ROPOROS/Monitoring_stack

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

📈 Observability & Monitoring – UWAS

Internship project focused on implementing end-to-end observability for Coral-IO’s UWAS production platform using New Relic, Kubernetes, and Ansible automation.


🚫 Repository Notice

⚠️ Due to confidentiality, the original source code and dashboards are private under Coral-IO’s internal GitLab environment.
This repository serves as a case study summarizing the project architecture, objectives, and outcomes.


🧩 Tech Stack

New Relic Ansible Kubernetes Linux Prometheus


📚 Table of Contents

  1. Overview
  2. Objectives
  3. Architecture
  4. Automation
  5. Challenges & Achievements
  6. Author

Overview

During my internship at **Coral-IO **, I implemented an observability strategy for the UWAS web application — a cloud-native production system.

The goal was to enhance monitoring, tracing, and alerting across multiple microservices using New Relic, Ansible, and Kubernetes.


Objectives

  • Assess existing monitoring maturity using the Observability Maturity Model (OMM)
  • Establish unified observability pipelines for infrastructure, applications, and user experience
  • Automate New Relic agent installation and configuration via Ansible
  • Integrate metrics, logs, and distributed tracing
  • Create custom dashboards and performance KPIs for engineering teams

Architecture

The implemented observability stack included:

Layer Tool Purpose
Infrastructure Kubernetes + Linux Application hosting and orchestration
Monitoring New Relic Full-stack observability (APM, metrics, logs)
Automation Ansible Agent provisioning and configuration
Visualization New Relic Dashboards Metrics and KPI visualization
Alerting New Relic Alerts SLA and performance-based alert rules

🔧 High-Level Flow

  1. Ansible deploys and configures New Relic agents on Kubernetes nodes.
  2. Agents collect application performance data, traces, and logs.
  3. Data is pushed to New Relic’s APM platform.
  4. Dashboards display live metrics, errors, and throughput.
  5. Alerts trigger based on pre-defined thresholds (response time, CPU, memory).

Architecture


Automation

All setup was fully automated using Ansible, including:

  • Installing New Relic infrastructure and APM agents
  • Registering services automatically with New Relic
  • Applying standardized dashboard templates per environment

Example playbook snippet:

- hosts: k8s_nodes
  become: true
  tasks:
    - name: Install New Relic infrastructure agent
      ansible.builtin.shell: |
        curl -Ls https://download.newrelic.com/install/newrelic-cli/scripts/install.sh | bash
    - name: Apply license key configuration
      ansible.builtin.copy:
        content: |
          license_key: "{{ newrelic_license }}"
        dest: /etc/newrelic-infra.yml

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published