{"slug": "new-relic", "name": "New Relic", "category": "observability", "category_name": "Monitoring and analytics", "description": "", "recommenders": 3, "commenters": 8, "warners": 1, "score": 2.878, "rising": -0.98, "first": "2025-11-07", "latest": "2026-07-04", "why": "with tools like NewRelic there's no need to slow the code down with profiling cruft.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 4, "compare": 0, "warn": 1}, "spark": [0, 0, 0, 1, 0, 1, 0, 0, 1, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "with tools like NewRelic there's no need to slow the code down with profiling cruft.", "kind": "", "icon": true, "domain": "newrelic.com", "github_repo": null, "official_url": "https://newrelic.com/", "pricing": "", "aliases": ["New Relic"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 780613120, "item_id": 48788320, "url": "https://news.ycombinator.com/item?id=48788320", "by": "hparadiz", "date": "2026-07-04", "version": null, "stance": "recommend", "quote": "with tools like NewRelic there's no need to slow the code down with profiling cruft.", "excerpt": "You can always make the ORM Model based on a view. Sometimes a background job compiling a simple result set table is the appropriate answer. Almost all ORMs boil down their queries down to a single query handler so it's actually super easy to find the query. My ORM for example: *Read paths* - Models/Factory/Getters/GetAllRecords.php:28 - table(...) when indexField is set. - Models/Factory/Getters/GetAllRecords.php:31", "context": "", "use_case": "query profiling", "switched_from": "", "story": "What ORMs have taught me: just learn SQL (2014)"}, {"id": 761902560, "item_id": 47618910, "url": "https://news.ycombinator.com/item?id=47618910", "by": "mandeepj", "date": "2026-04-02", "version": null, "stance": "recommend", "quote": "checkout", "excerpt": "checkout https://newrelic.com/instant-observability/sqlite", "context": "", "use_case": "Observability for SQLite", "switched_from": "", "story": "Modern SQLite: Features You Didn't Know It Had"}, {"id": 751529392, "item_id": 46970587, "url": "https://news.ycombinator.com/item?id=46970587", "by": "tootie", "date": "2026-02-10", "version": null, "stance": "recommend", "quote": "using New Relic or the like is just way, way better", "excerpt": "I'm nigh on 50 and feel very differently. I honestly loved the 2010s and the adoption of frameworks, SaaS, continuous deployment, cloud and even agile. Delivering software felt a lot more professional and less artisan which I really appreciated. I can fondly recall opening 4 ssh windows and running tail -f on every prod server log, but using New Relic or the like is just way, way better. It feels more satisfying to c", "context": "", "use_case": "Application monitoring", "switched_from": "", "story": "I started programming when I was 7. I'm 50 now and the thing I loved has changed"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 733567536, "item_id": 45847971, "url": "https://news.ycombinator.com/item?id=45847971", "by": "yread", "date": "2025-11-07", "version": null, "stance": "warn", "quote": "I use New Relic and I'm not sure I would recommend it.", "excerpt": "I use New Relic and I'm not sure I would recommend it. Sure it was easy to install on all the server but now I keep getting alerts every months (on like the 2nd day) that I ran out of some \"quota\" of 100GB. I thought that's impossible as I almost don't use it but apparently they (used to) send by default list of running processes every second and that gunks things up. Also I setup alerts - for >50% CPU or >90% disk f", "context": "", "use_case": "monitoring and alerting", "switched_from": "", "story": "OpenTelemetry: Escape Hatch from the Observability Cartel"}]}], "who": [{"by": "Reith", "context": "back-end engineer in Vancouver", "url": "https://news.ycombinator.com/item?id=46902393", "date": "2026-02-05"}], "tags": [], "use_cases": ["query profiling", "observability for sqlite", "application monitoring", "monitoring and alerting"], "compared": [{"slug": "datadog", "name": "Datadog", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "postgresql", "name": "PostgreSQL", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=48742175", "title": "What ORMs have taught me: just learn SQL (2014)", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47616704", "title": "Modern SQLite: Features You Didn't Know It Had", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47414356", "title": "We give every user SQL access to a shared ClickHouse cluster", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47304597", "title": "Show HN: Using Isolation forests to flag anomalies in log patterns", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47067632", "title": "Show HN: Faultline \u2013 Open-source AI agent for infrastructure debugging", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46960675", "title": "I started programming when I was 7. I'm 50 now and the thing I loved has changed", "mentions": 1}], "sentiment_by_month": {"2025-11": {"warn": 1}, "2025-12": {}, "2026-01": {}, "2026-02": {"neutral": 2, "recommend": 1}, "2026-03": {"neutral": 2}, "2026-04": {"recommend": 1}, "2026-05": {}, "2026-06": {}, "2026-07": {"recommend": 1}, "2026-08": {}, "2026-09": {}, "2026-10": {}}, "versions": [], "version_unnamed": 0, "family_ref": null, "runs_on": null, "lines": [], "quotes": [{"id": 780613120, "item_id": 48788320, "url": "https://news.ycombinator.com/item?id=48788320", "by": "hparadiz", "date": "2026-07-04", "version": null, "stance": "recommend", "quote": "with tools like NewRelic there's no need to slow the code down with profiling cruft.", "excerpt": "You can always make the ORM Model based on a view. Sometimes a background job compiling a simple result set table is the appropriate answer. Almost all ORMs boil down their queries down to a single query handler so it's actually super easy to find the query. My ORM for example: *Read paths* - Models/Factory/Getters/GetAllRecords.php:28 - table(...) when indexField is set. - Models/Factory/Getters/GetAllRecords.php:31", "context": "", "use_case": "query profiling", "switched_from": "", "story": "What ORMs have taught me: just learn SQL (2014)"}, {"id": 761902560, "item_id": 47618910, "url": "https://news.ycombinator.com/item?id=47618910", "by": "mandeepj", "date": "2026-04-02", "version": null, "stance": "recommend", "quote": "checkout", "excerpt": "checkout https://newrelic.com/instant-observability/sqlite", "context": "", "use_case": "Observability for SQLite", "switched_from": "", "story": "Modern SQLite: Features You Didn't Know It Had"}, {"id": 759570290, "item_id": 47473143, "url": "https://news.ycombinator.com/item?id=47473143", "by": "leetrout", "date": "2026-03-21", "version": null, "stance": "neutral", "quote": "like a knock off of what new relic does", "excerpt": "I built something on top of DuckDB last year but it never got deployed. They wanted to trust Postgres. I didn't use the in browser WASM but I did expose an api endpoint that passed data exploration queries directly to the backend like a knock off of what new relic does. I also use that same endpoint for all the graphs and metrics in the UI. Just filtered out the write / delete statements in a rudimentary way. DuckDB ", "context": "", "use_case": "", "switched_from": "", "story": "We give every user SQL access to a shared ClickHouse cluster"}, {"id": 756873569, "item_id": 47304598, "url": "https://news.ycombinator.com/item?id=47304598", "by": "kvaranasi_", "date": "2026-03-08", "version": null, "stance": "neutral", "quote": "connects to existing Loki/New Relic/Datadog, etc", "excerpt": "Consider you have logs at ~100k/hour. And you are looking for a log that you have never seen before or one that is rare to find in this pool of 1000s of look-alike errors and warnings. I built a tool that flags out anomalies. The rarest of the rarest logs by clustering them. This is how it works: 1. connects to existing Loki/New Relic/Datadog, etc - pulls logs from there every few minutes 2. Applies Drain3(https://gi", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: Using Isolation forests to flag anomalies in log patterns"}, {"id": 753082529, "item_id": 47067658, "url": "https://news.ycombinator.com/item?id=47067658", "by": "pranav_rajs", "date": "2026-02-18", "version": null, "stance": "neutral", "quote": "It connects to New Relic, Sentry, AWS, GitHub, and PagerDuty using MCP", "excerpt": "Hi HN, We built Faultline at Chatwoot to help our team debug infrastructure incidents faster. It's an AI agent you can ask questions in plain English \u2014 it autonomously queries your monitoring tools, cloud infrastructure, and codebase, then comes back with a root cause analysis. It connects to New Relic, Sentry, AWS, GitHub, and PagerDuty using MCP (Model Context Protocol) servers and native integrations. You ask some", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: Faultline \u2013 Open-source AI agent for infrastructure debugging"}, {"id": 751529392, "item_id": 46970587, "url": "https://news.ycombinator.com/item?id=46970587", "by": "tootie", "date": "2026-02-10", "version": null, "stance": "recommend", "quote": "using New Relic or the like is just way, way better", "excerpt": "I'm nigh on 50 and feel very differently. I honestly loved the 2010s and the adoption of frameworks, SaaS, continuous deployment, cloud and even agile. Delivering software felt a lot more professional and less artisan which I really appreciated. I can fondly recall opening 4 ssh windows and running tail -f on every prod server log, but using New Relic or the like is just way, way better. It feels more satisfying to c", "context": "", "use_case": "Application monitoring", "switched_from": "", "story": "I started programming when I was 7. I'm 50 now and the thing I loved has changed"}, {"id": 750438299, "item_id": 46902393, "url": "https://news.ycombinator.com/item?id=46902393", "by": "Reith", "date": "2026-02-05", "version": null, "stance": "neutral", "quote": "Monitoring: Datadog, OpenTelemetry, GCP Monitoring, Prometheus, Grafana, New Relic", "excerpt": "Location: Vancouver, Canada Role: Back-end engineer Technologies: Programming: Python, JavaScript, Network Programming, Go, Erlang Platforms: GCP, Kubernetes, Temporal, Pulumi Databases: PostgreSQL, Elasticsearch, Cassandra, PL/pgSQL Monitoring: Datadog, OpenTelemetry, GCP Monitoring, Prometheus, Grafana, New Relic Data: Spark, Druid, Kafka, PubSub, BigQuery CV: short: https://drive.google.com/file/d/1c7ayN_qN9ayABWc", "context": "back-end engineer in Vancouver", "use_case": "", "switched_from": "", "story": "Ask HN: Who wants to be hired? (February 2026)"}, {"id": 733567536, "item_id": 45847971, "url": "https://news.ycombinator.com/item?id=45847971", "by": "yread", "date": "2025-11-07", "version": null, "stance": "warn", "quote": "I use New Relic and I'm not sure I would recommend it.", "excerpt": "I use New Relic and I'm not sure I would recommend it. Sure it was easy to install on all the server but now I keep getting alerts every months (on like the 2nd day) that I ran out of some \"quota\" of 100GB. I thought that's impossible as I almost don't use it but apparently they (used to) send by default list of running processes every second and that gunks things up. Also I setup alerts - for >50% CPU or >90% disk f", "context": "", "use_case": "monitoring and alerting", "switched_from": "", "story": "OpenTelemetry: Escape Hatch from the Observability Cartel"}]}