Merge pull request #8152 from juliangiuca/patch-1

Changes to how log volume estimates

src/content/docs/data-apis/manage-data/calculate-data-ingest.mdx

@@ -111,19 +111,12 @@ For how to manage your data ingest, see [Manage data ingest](/docs/data-apis/man
   >
 For this section, you add an estimated amount of ingest in gigabytes.
 
-When estimating log data ingest:
-
-* Use current logs volume. For example:
-  * Pull information from existing ELK, Splunk, or Sumo storage and divide by total months that data is currently retained to get a per-month rate.
-  * Multiply your average log file size by the number of logs you use, and extrapolate to get a per-month rate.
-* Subtract security (PCI/HIPAA) and audit logs.
-  * Generally, 40-50% of current ELK, Splunk, and Sumo storage is used for troubleshooting.
-* Understand your retention requirements.
-  * Typically, troubleshooting logs are not that valuable after 30 days of retention.
-
-In section 5, add your estimated monthly log data ingest, in GB. You can estimate this as 40-50% of your existing ELK (Elasticsearch, Logstash, Kibana), Splunk, or Sumo data ingest.
+Because each vendor measures log data differently, there is no easy way to establish a baseline estimate of log volume in New Relic from an existing implementation. The best way to estimate your log volume is to send a sample amount of log data and extrapolate.
+
+Log events are stored and metered as JSON objects, which are always larger than the original raw log on disk.
 
 For how to manage your data ingest, see [Manage data ingest](/docs/data-apis/manage-data/manage-data-coming-new-relic/#adjust-ingest).
+
   </Collapser>
 
     <Collapser