nano SIEM
Enrichments

Enrichment troubleshooting

Supported in:Self-hosted

Find out why an expected enrichment is missing: check the feed, the ClickHouse dictionaries, and whether the event has something to enrich.

Use these checks to find why an expected enrichment is missing. Check the feed, the ClickHouse dictionaries, and the event's fields in that order.

An event can lack enrichment because it has no matching field, no indicator matched, the feed wasn't current when it arrived, or ClickHouse couldn't load the dictionary.

1. Check the feed

Open Marketplace to see the platform feed bundle: when it was installed, its source (online or offline), each feed's state, and the last check and its error. The same data is available from the API (needs enrichments:view):

curl https://<your-nano-host>/api/enrichment/platform-feeds -H "X-API-Key: $NANO_API_KEY"
Feed stateMeaningWhat to do
freshProduced within the last 7 days, stampingGo to step 2
staleOlder than 7 days, still stampingRun a check (POST /api/enrichment/platform-feeds/check) and look at last_error
expiredPast its hard expiry; new events aren't stampedInstall a newer bundle: run a check, or import one on air-gapped installs

No bundle installed at all? Check that the jobs service can reach nano's feed endpoint (or your PLATFORM_FEEDS_URL mirror), and that PLATFORM_FEEDS_AUTO_UPDATE isn't false.

2. Check ClickHouse memory and dictionaries

The feeds are served from ClickHouse dictionaries, which need memory. With the platform feeds on, give ClickHouse at least 6 GB (CLICKHOUSE_MEM_LIMIT=6G on Docker Compose). If a dictionary can't load, ingest keeps working but events aren't enriched, and SIEM Health reports the dictionary as degraded.

3. Check the event has something to enrich

Find the event and look at the fields the feeds read:

metadata.log_source="my_source" | head 5 | table time, src_endpoint.ip, dst_endpoint.ip, src_endpoint.location.country, enrichments.ioc_dest_ip_threat_type
  • No src_endpoint.ip / dst_endpoint.ip? The parser didn't map the IPs to OCSF endpoints, so IP feeds have nothing to look up. Fix the parser mapping.
  • Private or reserved IPs? IPinfo and prevalence skip them.
  • Country already set by the parser? IPinfo doesn't overwrite it.
  • Domain or hash in another field? Domain matches read url.hostname, http_request.url.hostname and query.hostname; hash matches read the SHA-256 of file and process. See the field reference.

Troubleshoot

Need help with these checks? Contact support with the request ID and time with timezone.

The event predates the feed or the indicator

Enrichment runs at ingest. An indicator added today doesn't enrich last week's events. Search history for it with lookup, an ioc search or a retro hunt.

No geo/ASN on any event

Check the IPinfo Lite feed state (step 1) and ClickHouse memory (step 2). A ClickHouse with 2–4 GB can't hold the IP dictionary.

An IOC list match isn't on the event

On the default OCSF profile, IOC list matches aren't stamped at ingest. Search for them with ioc instead. See IOC lists.

Air-gapped install: feeds never update

Import the signed bundle file with POST /api/enrichment/platform-feeds/import. Bundles are refused if they're older than the installed one or their signature doesn't verify.

Custom enrichments

SymptomLikely causeFix
Validation fails with a network errorThe domain isn't in the allowed list, or doesn't match exactlyAdd the exact host from the URL
Validation fails with a format errorIOC fields placed inside dataPut threat_type, confidence and malware at the top level of each record
Run times outLarge feed or slow APIRaise the timeout (up to 1,800 s), or fetch incrementally with watermark
Run succeeds but nothing matchesWrong key type, or keys not normalized (case, trailing dots, ip:port)Match the key type to the field, and normalize keys in code

Still stuck

Collect the platform feed status, an example event (metadata.uid) and the value you expected to be enriched, and contact support.

What's next

On this page