Maser's thesis proposal.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

143 lines
7.0KB

  1. @article{alvaroOKWHYTRACING,
  2. title = {{{OK}}, {{BUT WHY}}? {{TRACING AND DEBUGGING DISTRIBUTED SYSTEMS}}},
  3. author = {Alvaro, Peter},
  4. pages = {14},
  5. annote = {Interesting, it has some more papers referenced.},
  6. file = {/home/martins/Zotero/storage/86F2V4E6/Alvaro - OK, BUT WHY TRACING AND DEBUGGING DISTRIBUTED SYS.pdf},
  7. language = {en}
  8. }
  9. @misc{arbezzanoGianarbSherlock2019,
  10. title = {Gianarb/Sherlock},
  11. author = {Arbezzano, Gianluca},
  12. year = {2019},
  13. month = may,
  14. abstract = {sherlock is a visualization and inspection tool for tracing. It is developed to use Telegraf Zipkin Plugin and InfluxDB},
  15. keywords = {influxdb,opentracing,telegraf,trace,ui,visualization,zipkin}
  16. }
  17. @misc{AWSReInvent,
  18. title = {{{AWS}} Re:{{Invent}} 2018: {{Deep Dive}} into {{AWS X}}-{{Ray}}: {{Monitor Modern Applications}} ({{DEV324}})},
  19. shorttitle = {{{AWS}} Re},
  20. abstract = {Are you spending hours trying to understand how customers are impacted by performance issues and faults in your service-oriented applications? In this session, we show you how customers are using AWS X-Ray to reduce mean time to resolution, get to the root cause faster, and determine customer impact. In addition, one of our X-Ray customers, ConnectWise,\ presents a\ case study and best practices on how it is\ leveraging X-Ray in its\ production environment. We also show you how to use X-Ray with applications built using AWS services, such as Amazon Elastic Container Service for Kubernetes (Amazon EKS), AWS Fargate, Amazon Elastic Container Service (Amazon ECS), and AWS Lambda\ to achieve the above.}
  21. }
  22. @misc{AWSXRayDistributed,
  23. title = {{{AWS X}}-{{Ray}} \textendash{} {{Distributed Tracing System}}},
  24. abstract = {AWS X-Ray helps you debug and analyze your microservices applications with request tracing so you can find the root cause of issues and performance bottlenecks.},
  25. file = {/home/martins/Zotero/storage/4MG36NPM/xray.html},
  26. howpublished = {https://aws.amazon.com/xray/},
  27. journal = {Amazon Web Services, Inc.},
  28. language = {en-US}
  29. }
  30. @article{barrosoWebSearchPlanet2003,
  31. title = {Web Search for a Planet: The Google Cluster Architecture},
  32. shorttitle = {Web Search for a Planet},
  33. author = {Barroso, L.A. and Dean, J. and Holzle, U.},
  34. year = {2003},
  35. month = mar,
  36. volume = {23},
  37. pages = {22--28},
  38. issn = {0272-1732},
  39. doi = {10.1109/MM.2003.1196112},
  40. file = {/home/martins/Zotero/storage/JCT623MY/Barroso et al. - 2003 - Web search for a planet the google cluster archit.pdf},
  41. journal = {IEEE Micro},
  42. language = {en},
  43. number = {2}
  44. }
  45. @misc{FayExtensibleDistributed,
  46. title = {Fay: {{Extensible Distributed Tracing}} from {{Kernels}} to {{Clusters}} - {{Microsoft Research}}},
  47. file = {/home/martins/Zotero/storage/MA2TJNQ6/fay-extensible-distributed-tracing-from-kernels-to-clusters-2.html},
  48. howpublished = {https://www.microsoft.com/en-us/research/publication/fay-extensible-distributed-tracing-from-kernels-to-clusters-2/}
  49. }
  50. @book{ghoshDistributedSystemsAlgorithmic2015,
  51. title = {Distributed Systems : An Algorithmic Approach},
  52. shorttitle = {Distributed Systems},
  53. author = {Ghosh, Sukumar},
  54. year = {2015},
  55. edition = {2nd ed..},
  56. publisher = {{Taylor \& Francis}},
  57. address = {{Boca Raton}},
  58. annote = {Includes bibliographical references and index.},
  59. file = {/home/martins/Zotero/storage/VL6NQBEF/VlRMU19SRVJPUjAwNzg3NjIyOQ==.html},
  60. isbn = {978-1-4665-5297-5},
  61. keywords = {Algorithmes,Algorithmes parallèles,Computer algorithms,Electronic data processing -- Distributed processing,Traitement réparti},
  62. language = {eng},
  63. lccn = {DIUF 1.7.2},
  64. series = {Chapman \& {{Hall}}/{{CRC}} Computer \& Information Science Series}
  65. }
  66. @inproceedings{inproceedings,
  67. title = {Performance Debugging for Distributed Systems of Black Boxes},
  68. author = {Aguilera, Marcos and Mogul, Jeffrey and Wiener, Janet and Reynolds, Patrick and Muthitacharoen, Athicha},
  69. year = {2003},
  70. month = dec,
  71. volume = {37},
  72. pages = {74--89},
  73. doi = {10.1145/1165389.945454},
  74. series = {Operating {{Systems Review}} - {{SIGOPS}}}
  75. }
  76. @misc{nikmd23DistributedTracingAzure,
  77. title = {Distributed {{Tracing}} in {{Azure Application Insights}} - {{Azure Monitor}}},
  78. author = {{nikmd23}},
  79. abstract = {Provides information about Microsoft's support for distributed tracing through our local forwarder and partnership in the OpenCensus project},
  80. file = {/home/martins/Zotero/storage/KIF6LLC6/distributed-tracing.html},
  81. howpublished = {https://docs.microsoft.com/en-us/azure/azure-monitor/app/distributed-tracing},
  82. language = {en-us}
  83. }
  84. @misc{OpenCensus,
  85. title = {{{OpenCensus}}},
  86. file = {/home/martins/Zotero/storage/KMSVEBJM/opencensus.io.html},
  87. howpublished = {https://opencensus.io/}
  88. }
  89. @misc{OpenTelemetry,
  90. title = {{{OpenTelemetry}}},
  91. abstract = {Effective observability requires high-quality telemetry},
  92. file = {/home/martins/Zotero/storage/3XVC8ZQ3/opentelemetry.io.html},
  93. howpublished = {https://opentelemetry.io/},
  94. journal = {OpenTelemetry}
  95. }
  96. @misc{OpenZipkinDistributedTracing,
  97. title = {{{OpenZipkin}} {$\cdot$} {{A}} Distributed Tracing System},
  98. file = {/home/martins/Zotero/storage/233XMACF/zipkin.io.html},
  99. howpublished = {https://zipkin.io/}
  100. }
  101. @misc{PaperDapperGoogle,
  102. title = {Paper: {{Dapper}}, {{Google}}'s {{Large}}-{{Scale Distributed Systems Tracing Infrastructure}} - {{High Scalability}} -},
  103. shorttitle = {Paper},
  104. abstract = {Imagine a single search request coursing through Google's massive infrastructure. A single request...},
  105. file = {/home/martins/Zotero/storage/Y786D2VA/paper-dapper-googles-large-scale-distributed-systems-tracing.html},
  106. howpublished = {http://highscalability.com/blog/2010/4/27/paper-dapper-googles-large-scale-distributed-systems-tracing.html},
  107. language = {en}
  108. }
  109. @article{sigelmanDapperLargeScaleDistributed,
  110. title = {Dapper, a {{Large}}-{{Scale Distributed Systems Tracing Infrastructure}}},
  111. author = {Sigelman, Benjamin H and Barroso, Luiz Andre and Burrows, Mike and Stephenson, Pat and Plakal, Manoj and Beaver, Donald and Jaspan, Saul and Shanbhag, Chandan},
  112. pages = {14},
  113. abstract = {Modern Internet services are often implemented as complex, large-scale distributed systems. These applications are constructed from collections of software modules that may be developed by different teams, perhaps in different programming languages, and could span many thousands of machines across multiple physical facilities. Tools that aid in understanding system behavior and reasoning about performance issues are invaluable in such an environment.},
  114. file = {/home/martins/Zotero/storage/9TFTPSP3/Sigelman et al. - Dapper, a Large-Scale Distributed Systems Tracing .pdf},
  115. language = {en}
  116. }
  117. @misc{WhyYouNeedc,
  118. title = {Why You Need {{Tracing}} in Your Distributed Systems - {{IT Dead Inside}} - {{Medium}}},
  119. file = {/home/martins/Zotero/storage/8J383XUD/why-you-need-tracing-in-your-distributed-systems-c738f0fce088.html},
  120. howpublished = {https://medium.com/it-dead-inside/why-you-need-tracing-in-your-distributed-systems-c738f0fce088}
  121. }
  122. @article{zotero-55,
  123. type = {Article}
  124. }