Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

APM libraries and this library #88

Open
juliankock opened this issue Apr 25, 2024 · 1 comment
Open

APM libraries and this library #88

juliankock opened this issue Apr 25, 2024 · 1 comment

Comments

@juliankock
Copy link

Hey Elastic!

Thanks for bridging the gap between OpenTelemetry and the native features of ElasticSearch telemetry.

I stumbled upon this repository, and I have been battling a lot with how to configure apps correctly.

Currently, we use Serilog, with the EcsTextFormatter and the APM Serilog enricher with the Serilog console sink in our k8s pods, which gets picked up by a Filebeat scraping the stdout of the containers and with manual instrumentation of APM.

All of our application code currently uses the MEL ILogger<T>, with Serilog behind the scenes, and we also use message templates across our solutions.

I was wondering, since I don't seem like I can find any example that shows this. How do these APM libraries, and this library, cooperate? Is it either this, or the APM library?

I look forward to hearing from you.

@juliankock juliankock changed the title Logging with Serilog APM libraries and this library Apr 25, 2024
@Mpdreamz
Copy link
Member

Mpdreamz commented May 2, 2024

Hey @juliankock thanks for opening this conversation.

We'll continue to support the Elastic.Ingest.* and Elastic.CommonSchema.* libraries.

They remain super useful for logging to file and having filebeat/Elastic Agent pick them up. Or when you want to write data directly to Elasticsearch.

With OTLP logs ECS and Semantic Conventions are merging and so we'll continue to ensure structured logging is a first class citizen in this setup as well.

Most likely the APM correlation libraries as part of ecs-dotnet will be deprecated in the long run though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants