Skip to content

Commit

Permalink
feat(sonic): copyedits part dos
Browse files Browse the repository at this point in the history
  • Loading branch information
bradleycamacho committed May 26, 2023
1 parent ee3f49e commit 93bb203
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/content/docs/journey-large-logs/get-started.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ import logsPartition from 'images/logs_screenshot_full-partition.webp'
Modern systems create large amounts of log data. You might be dealing with hundreds of gigabytes to dozens of terabytes today, and the amount will continue to increase as your system scales. When you need to search through your logs, you'll encounter hours of toil trying to uncover valuable and relevant logs. Sending all your logs to a log management tool can help reduce this toil, but you'll quickly encounter organizational hurdles and rising costs as you ingest more logs. New Relic solves this problem by providing tools to ingest only valuable logs to reduce cost, a unified UI to correlate your logs to your services, and various ways to organize your logs before your drown in them.


This tutorial walks you through how to use New Relic to manage a large amount of log ingest. You'll start by forwarding your logs to New Relic, which means sending your log data to New Relic automatically. You'll then identify what logs to ingest and which to drop. Finally you'll organize your logs through partitions and parsing.
Whether you're setting up a log management platform for the first time or you're migrating to New Relic, this tutorial will walk you through how to use New Relic to manage a large amount of log data. You'll start by forwarding your logs to New Relic, which means sending your log data to New Relic automatically. You'll then identify what logs to ingest and which to drop. Finally you'll organize your logs through partitions and parsing.


<img
Expand Down

0 comments on commit 93bb203

Please sign in to comment.