style(Logs screenshots): Obfuscation, blobs

FOR DOC-7769

src/content/docs/logs/ui-data/long-logs-blobs.mdx

@@ -9,6 +9,9 @@ redirects:
   - /docs/logs/log-management/ui-data/long-logs-blobs
 ---
 
+import LogBlobQuery from 'images/log-blob-query.png'
+
+
 Extensive log data can help you troubleshoot issues. But what if an attribute in your log contains thousands of characters? How much of this data can New Relic store? And how can you find useful information in all this data?
 
 ## How blobs work [#blob-example]
@@ -76,6 +79,16 @@ newrelic.ext.message: <next 128,000 bytes as a 'blob'>
 
 ## Query your data for blobs [#query-blob]
 
+<img
+  title="Query log extended data (blobs)"
+  alt="Screenshot of Log blobs query in UI"
+  src={LogBlobQuery}
+/>
+
+<figcaption>
+  **[one.newrelic.com](https://one.newrelic.com) > Logs**: To query extended blob data in your logs, be sure to include backticks in your attribute's blob syntax.
+</figcaption>
+
 To query for any log data in New Relic, run the following query:
 
 ```

src/content/docs/logs/ui-data/obfuscation-ui.mdx

@@ -7,6 +7,9 @@ import obfuscationCreateExpressionUi from 'images/obfuscation-create-expression-
 
 import obfuscationCreateRuleUi from 'images/obfuscation-create-rule-ui.png'
 
+import obfuscationUi from 'images/log-obfuscationUI-041422.png'
+
+
 After logs have been shipped to New Relic, any sensitive information in the logs can be obfuscated before being stored in [NRDB](/docs/data-apis/get-started/nrdb-horsepower-under-hood/), our New Relic database, by using obfuscation rules.
 
 Sensitive information might include personally-identifiable information such as credit card numbers, Social Security numbers, national IDs, or other data that you may be required by regulation to protect when stored.
@@ -283,6 +286,24 @@ To obfuscate your logs:
 * Define how you will capture them using NRQL.
 * Define which obfuscation actions need to be applied to each of them. Ask yourself: Will I need to query my logs using this sensitive information later (consider using `HASH`), or do I need to remove this information entirely from my logs (consider using `MASK`)?
 
+
+
+
+<img
+  title="Logs obfuscation in UI"
+  alt="Screenshot of Logs obfuscation UI"
+  src={obfuscationUi}
+/>
+
+<figcaption>
+  **[one.newrelic.com](https://one.newrelic.com) > Logs > Obfuscation**: First create one or more obfuscation expressions, then create your obfuscation rules.
+</figcaption>
+
+<Callout variant="tip">
+  The **Logs Obfuscation** UI includes a **Hashing tool** so that you can find a hash from a known value and copy it for use with other expressions and rules.
+</Callout>
+
+
 ## Obfuscation expressions [#expressions]
 
 You can create, read, update, or delete obfuscation expressions by using the New Relic UI or by using NerdGraph, our GraphQL Explorer.