chore: added doc title to messaging queues

[SagarRajput-7]

Summary

Related Issues / PR's

Screenshots

Affected Areas and Manually Tested Areas

---

Important

Add specific titles for Kafka and Celery task views in titles.json.

• Titles Update:
  • Added MESSAGING_QUEUES_KAFKA, MESSAGING_QUEUES_KAFKA_DETAIL, and MESSAGING_QUEUES_CELERY_TASK to titles.json for specific messaging queue views.
  • Updated MESSAGING_QUEUES_OVERVIEW to SigNoz | Messaging Queues.

^{This description was created by for fe9d3d2. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to fe9d3d2 in 1 minute and 52 seconds

More details

• Looked at 16 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 3 drafted comments based on config settings.

1. frontend/public/locales/en/titles.json:64

• Draft comment:
  Both 'MESSAGING_QUEUES_KAFKA' and 'MESSAGING_QUEUES_KAFKA_DETAIL' have identical values. Confirm if duplication is intentional.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50%
  Looking at the rules, we should not make comments that ask authors to "confirm" things. The duplication of values could be intentional as these are different keys (one for list view, one for detail view) that happen to have the same title text. This is a common pattern in web apps. Even if it wasn't intentional, it's not causing any functional issues.
  The duplicate values could potentially indicate a mistake or oversight that should be fixed. Having different keys with the same value might be confusing for maintainers.
  While duplicate values might be confusing, this appears to be a valid pattern where different routes/views share the same page title. The keys clearly indicate their different purposes (list vs detail view).
  Delete this comment as it violates the rule against asking authors to "confirm" things, and the duplication appears to be a valid pattern rather than an issue requiring changes.

2. frontend/public/locales/en/titles.json:63

• Draft comment:
  Ensure Kafka titles are distinct if overview and detail pages differ; currently both 'MESSAGING_QUEUES_KAFKA' and 'MESSAGING_QUEUES_KAFKA_DETAIL' have the same title.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50%
  The comment starts with "Ensure that..." which is a red flag according to our rules. However, it does point out a legitimate potential UX issue where two different pages have identical browser titles, which could be confusing for users with multiple tabs open. But this seems more like a product/UX decision than a code issue - maybe they want these pages to have the same title.
  The duplicate titles might be intentional - perhaps these pages are closely related and should share the same title. We don't have enough context about the UX requirements.
  While the duplicate titles could be intentional, having different pages share identical titles generally makes for poor UX and tab management.
  Delete the comment. While it raises a valid UX consideration, it starts with "Ensure that..." which violates our rules about verification requests, and we don't have enough context to know if the duplicate titles are intentional.

3. frontend/public/locales/en/titles.json:70

• Draft comment:
  The key 'METRICS_EXPLORER_EXPLORER' appears to contain a duplicated word ('EXPLORER'). Please check if this is intentional or a typo. Consider renaming it if it's a mistake.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_5HY1hygG6xGqxCjz

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.