Merge pull request #234 from parca-dev/Sylfrena-patch-1

Update parca-agent-design.md

Author: brancz

docs/parca-agent-design.md

@@ -28,7 +28,7 @@ The way BPF programs communicate with user-space uses BPF maps. The Parca Agent
 Parca Agent reads all data every 10 seconds. The data that is read from the BPF maps gets processed and then purged to reset for the next iteration.
 
 <p align="center">
-  <img alt="Parca Agent BPF program" src="https://docs.google.com/drawings/d/1Xq3VpXzO9wo2k91ZQKVBzzo4axszTA0SCrzRSnosNi4/export/svg" alt="drawing" width="600" />
+  <img alt="Parca Agent BPF program" src="https://docs.google.com/drawings/d/1NW9bP6jJ3i3CTymuuKEOmTfcQGKU-pn1qcWMUk6S3x8/export/svg" alt="drawing" width="600" />
 </p>
 
 ### CPU sampling frequency

docs/parca.md

@@ -6,7 +6,9 @@ If you haven't already, it is a good idea to read the [general overview](./overv
 
 ## Architecture
 
-![Parca Architecture Overview](https://docs.google.com/drawings/d/10VH49EgWlNF1wONKroQb5x3Q1Rkrnsc1BikTUvJNFIE/export/svg)
+<p align="center">
+  <img alt="Parca Architecture Overview" src="https://docs.google.com/drawings/d/1EAyMTbt-Ajf0KIzAFqjQdZNzjUnrm3NCH9922aOS4pI/export/svg" alt="drawing" width="600" />
+</p>
 
 Parca has a purpose built storage, which receives writes either from a pull mechanism that performs HTTP requests, or through a push mechanism via the gRPC API. Parca features two gRPC APIs for pushing data, one for the profiles themselves and one for [debuginfo](https://en.wikipedia.org/wiki/DWARF) metadata. Parca Agent uses the two APIs to minimize the amount of data transferred, it checks that metadata is uploaded only once, and otherwise only the measures statistics are sent.