Closed srikanthccv closed 7 months ago
[!WARNING]
Rate Limit Exceeded
@srikanthccv has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 13 minutes and 3 seconds before requesting another review.
How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.How do rate limits work?
CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://coderabbit.ai/docs/faq) for further information.Commits
Files that changed from the base of the PR and between b531173042168c448b59dc6ddc4a1226549c9472 and 02509073c8e017402575bdf8ee6816681ca555d1.
This change focuses on modifying how instance IDs are handled within the aggregateMetrics
function. Specifically, it replaces the usage of semconv.AttributeServiceInstanceID
with a custom signozID
, aiming to address issues related to the display of service instance IDs in the Signoz backend. This adjustment is intended to ensure that the specified name for service.instance.id
is accurately reflected, rather than appearing as a hex encoded string.
File | Change Summary |
---|---|
.../signozspanmetricsprocessor/processor.go |
Replaced semconv.AttributeServiceInstanceID with signozID in aggregateMetrics function |
Objective | Addressed | Explanation |
---|---|---|
Correct display of service.instance.id as specified name instead of hex string (#283, #4338) |
✅ | |
Ensure service.instance.id value is accurately reflected in Signoz backend (#283, #4338) |
✅ |
In the realm of code, where bugs like to hide, A rabbit hopped in, with a mission wide. With a leap and a bound, it tackled the task, Replacing a string, no questions to ask.
🐰 "Fear not," it said, "for I bring a fix, To make instance IDs as solid as bricks." Now in Signoz, the names do appear, Thanks to the rabbit, we cheer and revere!
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?
Fixes https://github.com/SigNoz/signoz-otel-collector/issues/283 Fixes https://github.com/SigNoz/signoz/issues/4338
In the past, we created our own ID
signoz.collector.id
for the uniqueness guarantees and then moved to use theservice.instance.id
from the collectorTelemetrySettings
. This conflicts with theservice.instance.id
coming from the Client SDK with the signoz-otel-collector. Users want to see their instance instead of the SigNoz deployment under theservice.instance.id
attribute. This is a reasonable ask. We will honour their settings and maintain our own attributesignoz.collector.id
as we did earlier.Summary by CodeRabbit