fix(deps): ensure traces are sent to application insights

[arealmaas]

Description

After some debugging, we found out that the only thing different that is related to opentelemetry are updates of these dependencies.

1.47.1 seemed to work, but not 1.47.2. 88a9217...d9281fc

(this is a bit fragile, so we need to consider other options, or adding alerts that notify us if we don't get any traces anymore)

Reverted commit: 75c7a24.

Related Issue(s)

• #{issue number}

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., if applicable)

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request involves downgrading OpenTelemetry-related package references from version 1.11.0 to 1.10.0 across multiple project files in the Digdir.Domain.Dialogporten solution. The changes are consistent across four project files: GraphQL, Janitor, Service, and WebApi. The downgrade specifically affects three packages: OpenTelemetry.Exporter.Console, OpenTelemetry.Exporter.OpenTelemetryProtocol, and OpenTelemetry, while maintaining other package versions.

Changes

File	Change Summary
src/.../Digdir.Domain.Dialogporten.GraphQL.csproj	Downgraded OpenTelemetry packages from 1.11.0 to 1.10.0
src/.../Digdir.Domain.Dialogporten.Janitor.csproj	Downgraded OpenTelemetry packages from 1.11.0 to 1.10.0
src/.../Digdir.Domain.Dialogporten.Service.csproj	Downgraded OpenTelemetry packages from 1.11.0 to 1.10.0
src/.../Digdir.Domain.Dialogporten.WebApi.csproj	Downgraded OpenTelemetry packages from 1.11.0 to 1.10.0

Possibly related PRs

• fix(app): Add missing telemetry setup GraphQL and Service #1695: Telemetry setup in GraphQL and Service components
• chore(deps): Remove unnecessary explicit NuGet-refs #1721: Downgrading OpenTelemetry packages in Service project
• fix(service): Avoid too many logs in app insights #1730: OpenTelemetry tracing settings modifications

Suggested reviewers

• oskogstad
• knuhau

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3b821d0 and c658afc.

📒 Files selected for processing (4)

• src/Digdir.Domain.Dialogporten.GraphQL/Digdir.Domain.Dialogporten.GraphQL.csproj (1 hunks)
• src/Digdir.Domain.Dialogporten.Janitor/Digdir.Domain.Dialogporten.Janitor.csproj (1 hunks)
• src/Digdir.Domain.Dialogporten.Service/Digdir.Domain.Dialogporten.Service.csproj (1 hunks)
• src/Digdir.Domain.Dialogporten.WebApi/Digdir.Domain.Dialogporten.WebApi.csproj (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Dry run deploy apps / Deploy job sync-resource-policy-information-job to test
• GitHub Check: Dry run deploy apps / Deploy job sync-subject-resource-mappings-job to test
• GitHub Check: build / build-and-test

🔇 Additional comments (4)

src/Digdir.Domain.Dialogporten.Service/Digdir.Domain.Dialogporten.Service.csproj (1)

9-12: Downgrade of OpenTelemetry packages is consistent with PR objectives.

The downgrade from 1.11.0 to 1.10.0 for OpenTelemetry packages aligns with the PR's goal to fix trace sending to Application Insights. This is a known issue between versions 1.47.1 and 1.47.2 as mentioned in the PR description.

Consider implementing the following to make the solution more robust:

1. Add monitoring alerts to detect if traces stop being sent to Application Insights
2. Create a test that verifies trace sending functionality
3. Document this version constraint in a central location for future reference

Would you like me to help create a monitoring solution or test implementation?

src/Digdir.Domain.Dialogporten.GraphQL/Digdir.Domain.Dialogporten.GraphQL.csproj (1)

18-21: Package versions are consistent with other projects.

The OpenTelemetry package versions match those in the Service project, maintaining consistency across the solution.

src/Digdir.Domain.Dialogporten.WebApi/Digdir.Domain.Dialogporten.WebApi.csproj (1)

20-23: Package versions are consistent with other projects.

The OpenTelemetry package versions match those in other projects, maintaining consistency across the solution.

src/Digdir.Domain.Dialogporten.Janitor/Digdir.Domain.Dialogporten.Janitor.csproj (1)

23-26: Package versions are consistent with other projects.

The OpenTelemetry package versions match those in other projects, maintaining consistency across the solution.

Let's verify compatibility with the Azure Monitor OpenTelemetry package:

✅ Verification successful

OpenTelemetry package versions are consistent and compatible

The review comment is correct. All projects maintain consistent versions of OpenTelemetry packages (1.10.0), and these versions are compatible with Azure.Monitor.OpenTelemetry.AspNetCore 1.2.0 used across the solution.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check compatibility between Azure.Monitor.OpenTelemetry.AspNetCore and OpenTelemetry packages

# Get package dependencies for Azure.Monitor.OpenTelemetry.AspNetCore 1.2.0
curl -s "https://api.nuget.org/v3/registration5-gz-semver2/azure.monitor.opentelemetry.aspnetcore/1.2.0.json" | jq -r '.packageContent' | xargs curl -s | jq '.dependencyGroups[] | select(.targetFramework == "net6.0") | .dependencies[] | select(.id | test("OpenTelemetry"; "i"))'

Length of output: 422

---

Script:

#!/bin/bash
# Find all .csproj files and check OpenTelemetry package versions
echo "=== OpenTelemetry package versions across projects ==="
fd -e csproj --exec grep -A 5 "OpenTelemetry" {}

# Check Azure Monitor OpenTelemetry package reference if exists
echo -e "\n=== Azure Monitor OpenTelemetry package reference ==="
fd -e csproj --exec grep "Azure.Monitor.OpenTelemetry" {}

Length of output: 5174

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.