Micrometer Mastery: Unleash Advanced Observability in your JVM Apps by Tommy Ludwig & Jonatan Ivanov

แชร์
ฝัง
  • เผยแพร่เมื่อ 13 ต.ค. 2024
  • Spring I/O 2024 - 30-31 May, Barcelona
    Slides: speakerdeck.co...
    Repo: github.com/jon...
    Is your application a black box? Is your current observability instrumentation not good enough? Do you want to add more to your metrics and distributed tracing? Join us and unlock the full potential of Micrometer and its cutting-edge observability features!
    Dive into:
    Micrometer Observation API: Instrument once and have multiple benefits out of it.
    Observation Conventions: Instrumentation with standardized naming and tagging.
    Automated Documentation: Effortlessly generate rich observability descriptions from your code.
    We’ll showcase:
    Practical code examples for instrumenting real-world applications.
    Advanced techniques to extract deeper insights and troubleshoot issues faster.
    Real-world use cases demonstrating the power of Micrometer’s observability toolkit.
    Ready to elevate your observability game using the industry’s golden standard? This talk is your one-stop shop for Micrometer mastery!

ความคิดเห็น • 5

  • @eded22319
    @eded22319 3 หลายเดือนก่อน +3

    The presentation was amazing!

  • @andmal8
    @andmal8 3 หลายเดือนก่อน +2

    Thank you for the great video!

  • @adrienl1020
    @adrienl1020 3 หลายเดือนก่อน +3

    Superbe présentation

  • @kappaj01
    @kappaj01 3 หลายเดือนก่อน +1

    Great talk... but.
    Looking at the repo it is insane the amount of code you need to write just to instrument two services. Just image a project with 100 services and 200 REST endpoints!
    At some point you are just going to abandon it as you will not have enough time from the project owner/bean-counters to implement all of that....
    Sorry - just an observation from the floor.

    • @JonatanIvanov
      @JonatanIvanov 3 หลายเดือนก่อน +1

      Could you please elaborate what you mean by insane amount of code? Spring components (e.g.: controllers/endpoints that you are referring to) are auto-instrumented out of the box, you don't need to write any code, you need to include dependencies (e.g.: actuator). If you want to do customizations for a lot of apps, you should not do it one by one but through a common module you include in each of them (this is not observability-related though). Some of the customizations (code) in the repo is only there for demo purposes, their purpose is to show an example (if you need to use them, there's how). There are users with thousands of applications who are using this.
      Please also feel free to open an issue in the repo if you have questions/improvement ideas.