Skip to main content
Question

Setting the Ingestion Namespace

  • Sep 14, 2026 4:58 PM UTC
  • 6 replies
  • 116 views

lifeofmorpheus
Forum|alt.badge.img+3

Hi,

I’m trying to build a Native Dashboard that would show the log_count and log_volume for GCP Projects but owned by different business units in the org.

Also, all ingestion into SecOps is via Direct Ingest

Using the below query, the namespace returns null value - which tells me the namespace must be set somewhere pre-processing:

ingestion.component = "Ingestion API"

$Namespace = ingestion.namespace

match:
$Namespace

outcome:
$Total_GB = math.round(sum(ingestion.log_volume) / math.pow(1000, 3), 2)

 

Please, any ideas on how to set the namespaces or perhaps other methods that would extract the project names or IDs pre-processing and can be used in a dashboard.

 

All suggestions would be greatly appreciated.

6 replies

MitchellR
Forum|alt.badge.img+3
  • Bronze 1
  • Sep 14, 2026 5:21 PM UTC

Hi ​@lifeofmorpheus - 

 

When all ingestion is via Direct Ingestion for Google Cloud logging, the default is for the namespace to = the Google Cloud Project ID for Cloud Audit logs, else [untagged] for the other sources. This is set via the parser itself. You can modify this, if desired, via utilizing the Bindplane DPM setup.

 

If you are referring, however, to Feeds, then the desired namespace per feed is defined as one of the optional values at time of configuration. This is found under Advanced Options and Asset Namespace per feed. 

 

 


lifeofmorpheus
Forum|alt.badge.img+3

Hi ​@MitchellR 

Thanks for your message.  Regarding Direct Ingestion, my understanding is the same as what you mentioned that Namespace = Google Cloud Project ID.

However, that is not the case with my instance as shown below:

 

 

Please, any ideas on what else I need to check both on the side of Cloud Logging and the SecOps sides.

 


hzmndt
Staff
Forum|alt.badge.img+12
  • Staff
  • Sep 21, 2026 9:43 AM UTC

​@lifeofmorpheus the feature to support ingestion labels is going to be supported soon, as of today, not supported, will test and confirm back once the feature is released  


MitchellR
Forum|alt.badge.img+3
  • Bronze 1
  • Sep 21, 2026 2:49 PM UTC

Hey ​@lifeofmorpheus, yeah it’s a bit messy. 

 

It used to be parsed into `metadata.base_labels.namespace` and also `principal.namespace`, but a parser change moved the field into `security_result.about.namespace`. 
 

So the data is there, but it is not in a place that the `ingestion.` table has access to since it’s a UDM event field, not a metadata attribute. 

 

The only way currently to overcome this is via using DPM in Bindplane to copy the project field from the raw payload to the namespace attribute, or to another field as desired. 


lifeofmorpheus
Forum|alt.badge.img+3

​@hzmndt ​@MitchellR 

Thanks to you both for your responses.
Please, what’s the Bindplane method you refer to.  We are currently not using bindplane in our architecture.  Hence, the Direct Ingestion method.
If we are to use Bindplane, that’d require a re-architecting of the ingestion/processing pipelines, correct? 


hzmndt
Staff
Forum|alt.badge.img+12
  • Staff
  • Sep 25, 2026 2:20 PM UTC