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
Service search #2143
base: develop
Are you sure you want to change the base?
Service search #2143
Conversation
shared/agent/src/providers/newrelic/errors/observabilityErrorsProvider.ts
Outdated
Show resolved
Hide resolved
shared/agent/src/providers/newrelic/goldenSignals/goldenSignalsProvider.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
couple of comments
const _alertSeverity = entityAccount?.alertSeverity || ""; | ||
const alertSeverityColor = ALERT_SEVERITY_COLORS[_alertSeverity]; | ||
|
||
const observabilityServiceEntityProps = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we could benefit from using React contexts in order to limit the number of props deeply nested components need? @dsellarsnr @eric-j @purplexa ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good idea:
https://react.dev/learn/passing-data-deeply-with-context
… need to associate on click
https://new-relic.atlassian.net/browse/NR-238700