Skip to content

standardize locations/sources for GeoIP database #394

Description

@mmguero

@mmguero cloned issue idaholab/Malcolm#485 on 2024-06-06:

Arkime has its geoip database (see arkime/scripts/arkime_update_geo.sh) and logstash uses the geoip filter (see logstash/pipelines/beats/12_lookups.conf and logstash/pipelines/enrichment/11_lookups.conf), but they don't necessarily use the same database.

We should standardize:

  1. Where these databases (the mmdb files) come from, probably just pull them once outside of the containers' Dockerfiles build and then include them into the docker containers rather than pull them as part of the Dockerfile

  2. Coordinate periodic updates (this is a bit tricker, where do the files get stored?)

  3. examine other uses of GeoIP if any (I don't think we're doing it with Zeek, as we're pushing that off to logstash)

Activity

  1. added
    arkimeRelating to Malcolm's use of Arkime
    bugSomething isn't working
    logstashRelating to Malcolm's use of Logstash
    on Nov 4, 2024
  2. added theissue type on Apr 8, 2025
  3. added this to the z.staging milestone on Apr 8, 2025
  4. removed this from the z.staging milestone on Sep 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    arkimeRelating to Malcolm's use of ArkimebugSomething isn't workinglogstashRelating to Malcolm's use of Logstash

    Fields

    No fields configured for Feature.

    Projects

    • Status
      No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions