@59:31 - right now the integrations for Java is great, just add a dependency and the team is done because the auto instrumentation captures great defaults. The angular (JavaScript) side not so much and after scouring the web for weeks I am still nowhere closer to having the same "just add this as a dependency" on the angular side.
You're not really "done" after adding the java agent. Sure, you get a lot of data, but observability is about more than just the defaults, it's about understanding how YOUR system works, which means you need to add your context to that data (through augmenting spans creating new spans, log scopes, or metrics labels). Frontend observability is coming along, but it's not quite there. Its the paradigm shift which is the issue, since there isn't one "context" Like a HTTP request to work with. Its getting there though.
@DotNetMartin sure you're not done, but it is a great starting place. My argument is you don't even have that starting place with front end and it is incredibly frustrating. I open a GitHub ticket, got told wrong place. Went to the discord server and question was ignored.
@@jscancella the place for this is the OpenTelemetry slack and the github for OpenTelemetry. Yoy could take a look at the new websdk we've built at honeycomb, its in the the process of being upstreamed, that will take some time though.
Awesomeee content!!! thank you!!
@59:31 - right now the integrations for Java is great, just add a dependency and the team is done because the auto instrumentation captures great defaults. The angular (JavaScript) side not so much and after scouring the web for weeks I am still nowhere closer to having the same "just add this as a dependency" on the angular side.
You're not really "done" after adding the java agent. Sure, you get a lot of data, but observability is about more than just the defaults, it's about understanding how YOUR system works, which means you need to add your context to that data (through augmenting spans creating new spans, log scopes, or metrics labels).
Frontend observability is coming along, but it's not quite there. Its the paradigm shift which is the issue, since there isn't one "context" Like a HTTP request to work with. Its getting there though.
@DotNetMartin sure you're not done, but it is a great starting place. My argument is you don't even have that starting place with front end and it is incredibly frustrating. I open a GitHub ticket, got told wrong place. Went to the discord server and question was ignored.
@@jscancella the place for this is the OpenTelemetry slack and the github for OpenTelemetry.
Yoy could take a look at the new websdk we've built at honeycomb, its in the the process of being upstreamed, that will take some time though.