<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Andrew Ngo on Medium]]></title>
        <description><![CDATA[Stories by Andrew Ngo on Medium]]></description>
        <link>https://medium.com/@andrewtienngo?source=rss-1c36c9e1fc9d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ftV28Ta2naKxKUeNa6lXCQ.png</url>
            <title>Stories by Andrew Ngo on Medium</title>
            <link>https://medium.com/@andrewtienngo?source=rss-1c36c9e1fc9d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:36:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andrewtienngo/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[MicrObserv: Observability Simplified]]></title>
            <link>https://medium.com/@andrewtienngo/microbserv-observability-simplified-341875ebcf63?source=rss-1c36c9e1fc9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/341875ebcf63</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[observability]]></category>
            <dc:creator><![CDATA[Andrew Ngo]]></dc:creator>
            <pubDate>Thu, 10 Nov 2022 20:47:22 GMT</pubDate>
            <atom:updated>2022-11-10T20:47:22.267Z</atom:updated>
            <content:encoded><![CDATA[<p>With microservice architecture becoming the new standard for developing applications, one of the main issues that arise deals with observability. Microservices are constantly communicating with each other, but because they are completely isolated, logs and error messages are spread all across their respective databases. This makes debugging and tracing incredibly tedious and difficult.</p><p>The solution to this is to take all logs and message tracers across all microservices for a given application and consolidate them into one centralized database. This is exactly what <a href="https://github.com/oslabs-beta/MicrObserv/tree/main"><strong>MicrObserv</strong></a> achieves.</p><p>MicrObserv is an open source product that is able to track the time it takes for any http request to resolve between each microservice as well as any consoles logs and stores them in a centralized database. It also comes with a dashboard that displays every log and the latency of each request to aid with debugging and to quickly make informed decisions for your application.</p><p>All that’s needed is to install our NPM package into each of your microservices, launch our application, and input your PostgreSQL URI for storing logs and tracers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/519/1*QeRpXudQEXNiig-UjzQMHA.gif" /></figure><p>Once completed, MicrObserv will display any logs and latency for all http requests between each microservice in real time!</p><p>Check out MicrObersv <a href="https://github.com/oslabs-beta/MicrObserv"><strong>here</strong></a><strong> </strong>and play around with it yourself!</p><h3><strong>MicrOberv Engineering Team:</strong></h3><p>Andrew Ngo| <a href="https://www.linkedin.com/in/andrew-tien-ngo/">https://www.linkedin.com/in/andrew-tien-ngo/</a></p><p>Chance Kupersmith| <a href="http://www.linkedin.com/in/chance-kupersmith">http://www.linkedin.com/in/chance-kupersmith</a></p><p>Otis Jones| <a href="https://github.com/Otis-Jones">https://github.com/Otis-Jones</a></p><p>Vardan Vanyan| <a href="https://www.linkedin.com/in/vardanvanyan/">https://www.linkedin.com/in/vardanvanyan/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=341875ebcf63" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>