Skip to content

fix(monitoring): add sentry monitoring #934

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

Merged
merged 6 commits into from
Apr 15, 2025
Merged

Conversation

avallete
Copy link
Member

For better performances tracing and error alerting use sentry

Closes: PGMETA-54

@avallete avallete requested review from a team as code owners April 14, 2025 18:05
@coveralls
Copy link

coveralls commented Apr 14, 2025

Pull Request Test Coverage Report for Build 14464190965

Details

  • 189 of 211 (89.57%) changed or added relevant lines in 6 files are covered.
  • 2 unchanged lines in 1 file lost coverage.
  • Overall coverage increased (+0.07%) to 75.773%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/server/admin-app.ts 0 3 0.0%
src/server/sentry.ts 37 43 86.05%
src/lib/db.ts 147 160 91.88%
Files with Coverage Reduction New Missed Lines %
src/lib/db.ts 2 92.62%
Totals Coverage Status
Change from base Build 14429680954: 0.07%
Covered Lines: 5060
Relevant Lines: 6600

💛 - Coveralls

@@ -22,7 +22,7 @@ import { init } from './db.js'
import { PostgresMetaResult, PoolConfig } from './types.js'

export default class PostgresMeta {
query: (sql: string) => Promise<PostgresMetaResult<any>>
query: (sql: string, customQuery?: boolean) => Promise<PostgresMetaResult<any>>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use a more explicit param name (e.g. trackQueryInSentry)? It's not obvious outside the context of pg-meta what's a custom query and what's not

@avallete avallete merged commit da7ccfa into master Apr 15, 2025
5 checks passed
@avallete avallete deleted the chore/add-sentry-monitoring branch April 15, 2025 07:56
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

Successfully merging this pull request may close these issues.

3 participants