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

Db Validation is not Azure App Insights friendly #14314

Closed
ShaneCourtrille opened this issue Sep 11, 2023 · 8 comments
Closed

Db Validation is not Azure App Insights friendly #14314

ShaneCourtrille opened this issue Sep 11, 2023 · 8 comments
Labels
Milestone

Comments

@ShaneCourtrille
Copy link
Contributor

Since updating to 1.5 we have started seeing dependency failures in App Insights when we provision new clients with the following exception "Microsoft.Data.SqlClient.SqlException (0x80131904): Invalid object name 'Document'."

I've traced this to the the Db validation step executing a select TOP against this table which does not yet exist.

It would be nice if OC could work without extraneous failures being logged in external telemetry systems as I suspect other systems like App Dynamics and what have you will also detect the same failure.

@Piedone
Copy link
Member

Piedone commented Sep 13, 2023

Do you mean this is an exception during setup of a tenant, right? Because in Application Insights while that shows up in Live metrics for some reason, it's not actually logged (it shouldn't, it's caught).

@ShaneCourtrille
Copy link
Contributor Author

@Piedone It shows up as a Dependency failure when you look at Requests or if you go look into the Failures / Dependency view

@Piedone
Copy link
Member

Piedone commented Sep 14, 2023

Indeed, you're correct. What I remembered is that they don't cause request failures.

@sebastienros
Copy link
Member

Is there a way to create faulty SQL queries, and mark them as expected in App Insight?

@Piedone
Copy link
Member

Piedone commented Sep 29, 2023

These can be filtered out with a telemetry processor, see here. I've created an issue for our AI module: Lombiq/Orchard-Azure-Application-Insights#68 I don't think this is a bug in Orchard but rather a peculiarity of collecting telemetry with AI.

@ShaneCourtrille
Copy link
Contributor Author

Yeah, we've tried this for the other "already an object named Identifiers in the database" but I wasn't happy with the end result. I'll take another look to see if I can solve both at the same time.

@ShaneCourtrille ShaneCourtrille closed this as not planned Won't fix, can't repro, duplicate, stale Sep 29, 2023
@Piedone
Copy link
Member

Piedone commented Oct 20, 2023

We've done it in our module here: Lombiq/Orchard-Azure-Application-Insights#69.

@MikeAlhayek MikeAlhayek modified the milestones: 1.x, 1.8 Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants