-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add OTLP exporters in our apps that send to the new OT agent #1465
Labels
monitoring
Issue related to logging and monitoring
Comments
github-project-automation
bot
moved this to New issues
in ⚠️ Dialogporten / Arbeidsflate - GAMMEL - se https://github.com/orgs/Altinn/projects/146 ⚠️
Nov 14, 2024
4 tasks
arealmaas
moved this from Doing
to Code Review og PR
in ⚠️ Dialogporten / Arbeidsflate - GAMMEL - se https://github.com/orgs/Altinn/projects/146 ⚠️
Dec 10, 2024
arealmaas
added a commit
that referenced
this issue
Dec 16, 2024
<!--- Provide a general summary of your changes in the Title above --> ## Description <!--- Describe your changes in detail --> - Sets up local OTEL setup that match the OTEL configuration in Azure Container Apps - Added fusioncache telemetry - Added Entity Framework telemetry - Missing liveMetrics if we want that. Needs to be considered. Other than that, the most relevant traces are pulled out from the AzureMonitor package. - Metrics are only visible locally for now. Turns out that the Azure Monitor Workspace has a Prometheus instance, but it does not allow for us sending metrics to it, as it does not have an OTEL endpoint 🙃 Solution here was adding the MetricsMonitor to send metrics directly to app insights for now..! - Will add logging in the next PR To see your metrics, spin up the OTEL services by running `docker-compose-otel.yml`. The service should start sending to the OTLP collector automatically. Example of a trace in the local Jaeger: ![CleanShot 2024-12-09 at 17 52 11@2x](https://github.com/user-attachments/assets/295eba27-84e8-4735-9a0e-be4f2fcfed9c) ## Related Issue(s) - #1465 ## Verification - [ ] **Your** code builds clean without any errors or warnings - [ ] Manual testing done (required) - [ ] Relevant automated test added (if you find this hard, leave it and we'll help out) ## Documentation - [ ] Documentation is updated (either in `docs`-directory, Altinnpedia or a separate linked PR in [altinn-studio-docs.](https://github.com/Altinn/altinn-studio-docs), if applicable) --------- Co-authored-by: Ole Jørgen Skogstad <skogstad@softis.net>
arealmaas
moved this from Code Review og PR
to Testing
in ⚠️ Dialogporten / Arbeidsflate - GAMMEL - se https://github.com/orgs/Altinn/projects/146 ⚠️
Dec 17, 2024
arealmaas
moved this from Testing
to Done
in ⚠️ Dialogporten / Arbeidsflate - GAMMEL - se https://github.com/orgs/Altinn/projects/146 ⚠️
Dec 20, 2024
arealmaas
closed this as completed
by moving to Done
in
⚠️ Dialogporten / Arbeidsflate - GAMMEL - se https://github.com/orgs/Altinn/projects/146 ⚠️
Dec 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use the environment variables that are injected in our containers to configure the OTLP endpoints.
OTEL_EXPORTER_OTLP_ENDPOINT
andOTEL_EXPORTER_OTLP_PROTOCOL
https://learn.microsoft.com/en-us/azure/container-apps/opentelemetry-agents?tabs=arm#environment-variables
For local development, consider adding a OTLP endpoint. https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/examples/demo/docker-compose.yaml (this might be a bit crazy for local development, but jaeger is nice to have:))
The text was updated successfully, but these errors were encountered: