Track missing organization context

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

We still have code paths that have no organization context. This indicate code paths that don't set Current.organization at all.

A signal for these is searching for json.meta.organization_source:fallback in the Kibana logs.

This issue can be closed if searching Kibana for json.meta.organization_source:fallback returns nothing.

How to find code paths:

The logging is controlled by a feature flag. First, check if the feature flag is enabled using Slack #production channel

/chatops gitlab run feature get track_organization_fallback

If it is disabled, enable it:

# 1 percent
/chatops gitlab run feature set track_organization_fallback 1 --actors

Then look in the logs for log entries that match json.meta.organization_source:fallback. Add the column json.meta.caller_id and find out why the fallback is triggered

Repeat.

Use these kibana indexes:

  • pubsub-rails-inf-gprd
  • pubsub-sidekiq-inf-gprd
Edited by 🤖 GitLab Bot 🤖