SnowPlow Micro - Iglu Central Not Found

For engineers Troubleshooting
1

Hello,

I already have snowplow up and running, sending data to databricks. I’m trying to setup SnowPlow Micro for testing and I’m getting this error:

[WARN] EventLog - BAD {
  "schemaKey" : "iglu:io.celus/user/jsonschema/1-0-0",
  "error" : {
    "error" : "ResolutionError",
    "lookupHistory" : [
      {
        "repository" : "Iglu Central",
        "errors" : [
          {
            "error" : "NotFound"
          }
        ],
        "attempts" : 2,
        "lastAttempt" : "2023-10-26T10:01:54.676Z"
      },
      {
        "repository" : "Iglu Central - Mirror 01",
        "errors" : [
          {
            "error" : "NotFound"
          }
        ],
        "attempts" : 2,
        "lastAttempt" : "2023-10-26T10:01:56.102Z"
      },
      {
        "repository" : "Iglu Client Embedded",
        "errors" : [
          {
            "error" : "NotFound"
          }
        ],
        "attempts" : 1,
        "lastAttempt" : "2023-10-26T09:59:46.548Z"
      }
    ]
  }
}

The user schema does exist, the path is correct, I’m sending data to databricks using this schema and it works. Why is it returning “not found” for these repositories?

2

Hey @vparoni ,

The error here describes where Micro is looking for schemas - Iglu Central, it’s mirror, and the embedded cache - so effectively just the schemas in Iglu Central are available. Iglu Central is the public registry for all the standard events.

Your event uses a custom schema, which you will have uploaded to your private repositiory - this is what the prod pipeline will be using.

You can follow the guidance here to have your micro reach your private Iglu schemas - basically it would need to use the same iglu_resolver configuration as the prod pipeline does.

I hope this helps. :slight_smile:

2 Likes