* Add resourse onprem monitoring Grafana Mimir.

* Add resourse onprem tracing Grafana Tempo.

* Added Yarp (Reverse Proxy) from Microsoft

Upscaled 96x96 icon to 256x256. Yarp is located at
https://github.com/microsoft/reverse-proxy
https://microsoft.github.io/reverse-proxy/index.html

* Update diagrams/onprem/network.py

Added newlines

Co-authored-by: Dov Benyomin Sohacheski <b@kloud.email>

Co-authored-by: Dov Benyomin Sohacheski <b@kloud.email>

* Add jfrog artifactory node

* Added jfrog image

* updated docs

* Update registry.py

* Add Portworx to onprem storage.

* Remove website/static/img/resources/resources/

* Updated + Added extra Elastic icons

* Updated from Master

* Removed website images

* Revert "Removed website images"

This reverts commit ac7cb2d8d4.

* Removed resources/resources

* Add EMQX as a On-Prem Queue entry

* Add larger EMQX icon

* Add MLflow to OnPrem MLOps

* Update MLflow entry in doc

* Added dir resources/onprem/registry, added Harbor Container Registry icon resources/onprem/registry/harbor.png from https://github.com/cncf/artwork/blob/master/projects/harbor/icon/color/harbor-icon-color.png. Ran convert resize command to resize original. Ran autogen.sh via Docker. Registry.py now exists in diagrams/onprem/ dir. docs/nodes/onprem.md auto-updated.

Co-authored-by: dryhn <dryhn>

* Updated docs to include images of nodes

* Updated docs to include images of nodes

* Added icons to docs

* Added black formatting

* Added back png that removed due to incorrect naming convention

* Revert yarn.lock changes

* feat(node): add Generic OS Debian (#549)

* [Fix] picture size

Adding xMatters node to alerting.

Co-authored-by: jared.curtis <jared.curtis@everbridge.com>

* Add Raspberry Pi logo for describing RPis.

* Added raspbian.png for Raspberry Pis.

* update raspbian.png for size

* Basic support for C4 model primitives.

* Use the "rect" shape for nodes

With the record shape we used before, graphviz would trip over
edges that set constraint=False.

* Adopt C4 terminology: Rename Dependency -> Relationship

* Adopt C4 terminology: Rename type -> technology

* Extract a shared C4Node

This makes the code more DRY, but also allows to add company-
specific extensions more easily. One need we have is to slightly
adapt the terminology. At Spotify, we happen to call `Container`
a `Component` for example. This is now easier to implement on top
of the shared `C4Node`.

* Add "C4" shield to the README

* Document how to produce a C4 diagram

Add a GraphQL programming framework node

* feat(output): Generate dot file and support multi outformat.(#441)

* [fix] forget to clean the dot generated file.

* [fix] indentation

* [fix] Review + add more cases in unittest

* [fix] Add dot in the test

* Added DigitalOcean provider

* Fix PR comment

* Reran the autogen script

Co-authored-by: Chris Skaaning <cskaaning@digitalocean.com>

* Add Nagios in OnPrem monitoring

* Update Nodes docs for Nagios in OnPrem monitoring

* Removed over-nesting in resources file and added test

* Update test_diagram.py

updated doc string of test function

* Add: SVN

* updated the png file to remove the green background as suggested by gabriel-tessier

* Add Dynatrace in monitoring category

* resized the dynatrace icon

This terminology is frowned upon within my firm and I accidentally forwarded this example to 750 staff.

* Added the LaTeX logo

* Ran the auto update script

* Added GCP Endpoints

* Added k3s

Co-authored-by: Guy Zylberberg <guy.z@claroty.com>

* Added IBM Provider

* Added IBM Provider

* Added IBM Provider

* Added IBM Provider

* Add IBM Provider

* Add IBM Provider

* Add IBM Provider

* Add IBM Provider

* Add IBM Provider

* Add IBM Provider

* Modified image after review comments

* Deleted resources

* Modified after review comments

* Modified as per code review

* Modified as per code review

* Modified as per code review

* Modified as per code review

* Modified as per code review

* feat(node): update Azure icons (#448)

* feat(node): fix broken resources

* Add AWS resources

* Add some aliases for the ELB

Co-authored-by: Dan Aharon-Shalom <dan.ash@sparkbeyond.com>