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

Add a generic rule for APM->DB relationships #1848

Merged
merged 6 commits into from
Jan 13, 2025
Merged

Conversation

javimb
Copy link
Contributor

@javimb javimb commented Jan 9, 2025

Relevant information

This new rule allows any hostname as DB endpoint, not limiting it to RDS.
It includes a more strict regex which only includes those providers that are supported in the DATABASE candidate category. The regex also filters out those unsupported metric names that contain a ; in the endpoint (legacy format to concat different endpoints in a single metric).

This new rule, which will be internally rolled out, will eventually replace the two other rules present in the file.

Checklist

  • I've read the guidelines and understand the acceptance criteria.
  • The value of the attribute marked as identifier will be unique and valid.
  • I've confirmed that my entity type wasn't already defined. If it is I'm providing an explanation above.

This new rule allows any hostname as DB endpoint, not limiting it to RDS.
It includes a more strict regex which only includes those providers that are supported in the `DATABASE` candidate category.
The regex also filters out those unsupported metric names that contain a `;` in the endpoint (legacy format to concat different endpoints in a single metric).
@javimb javimb force-pushed the javimb/generic-db-rule branch from 20d673b to fabfd94 Compare January 9, 2025 09:33
@javimb javimb added do-not-merge internal review Being reviewed by NR teams / Coordination needed labels Jan 9, 2025
@javimb javimb merged commit f68cbaa into main Jan 13, 2025
10 checks passed
@javimb javimb deleted the javimb/generic-db-rule branch January 13, 2025 13:46
javimb added a commit that referenced this pull request Jan 13, 2025
rohit-bandlamudi-nr pushed a commit to rohit-bandlamudi-nr/entity-definitions that referenced this pull request Jan 15, 2025
This new rule allows any hostname as DB endpoint, not limiting it to RDS.
It includes a more strict regex which only includes those providers that are supported in the `DATABASE` candidate category.
The regex also filters out those unsupported metric names that contain a `;` in the endpoint (legacy format to concat different endpoints in a single metric).

Co-authored-by: Otávio Carvalho <[email protected]>
rohit-bandlamudi-nr pushed a commit to rohit-bandlamudi-nr/entity-definitions that referenced this pull request Jan 15, 2025
This new rule allows any hostname as DB endpoint, not limiting it to RDS.
It includes a more strict regex which only includes those providers that are supported in the `DATABASE` candidate category.
The regex also filters out those unsupported metric names that contain a `;` in the endpoint (legacy format to concat different endpoints in a single metric).

Co-authored-by: Otávio Carvalho <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal review Being reviewed by NR teams / Coordination needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants