Review Beacon Suggestions

Before you start

• Let Beacon ingest enough real traffic to produce useful suggestions.
• Be ready to reject weak suggestions instead of importing noisy structure.

Do this

1. Open Alerts and switch to Suggestions.
2. Filter the queue by type or search term if you are reviewing one service area at a time.
3. Open each suggestion and read the proposed system or function name, supporting samples, and occurrence count.
4. Link the suggestion to an existing catalog object when Beacon has identified the right target but the object already exists.
5. Create a new system or function only when the suggestion represents a stable part of your service model.
6. Leave weak, duplicate, or one-off suggestions unaccepted.
7. Revisit suggestions after you improve source mapping so the next batch is cleaner.

Check it worked

• Accepted suggestions create or link the expected catalog objects.
• The catalog becomes easier to route against instead of more cluttered.
• The remaining queue is smaller and higher quality.

If it does not work

• If suggestions are vague, improve summary mapping on the underlying sources first.
• If Beacon keeps proposing duplicates, review naming consistency in your catalog.
• If a suggestion should match an existing object but does not, link it manually instead of creating a duplicate.

Next

• Create systems and functions
• Assign ownership