Question about Adapter behavior/initialization

[rfichoke]

I'm writing an Adapter for integrating notifications from an in-house application and have some questions.

Our custom application generates log messages that have hostnames (and sometimes FQDNs) instead of IP addresses.  When I call updateLogMessage(), it expects a Device "Identification," which seems to be an IP address rather than a hostname.  The message volume is quite high, so I don't really want to be doing host lookups every time I receive a logging message.

I had considered using the initialize() method in my Adapter to retrieve the contents of the Device table and set up a map from IP addresses to hostnames, which will make the process much more efficient.  However, someone else has written a set of scripts to update the Device table from application configs every day, so the Device table changes frequently.

How often is initialize() called?  Are Adapter instances frequently created and destroyed as message volume from the feeders increases and decreases?  Is there a better solution to my problem?

As a side matter, I had wondered if new Adapter instances were created in separate threads from a thread pool to meet changing volume as well.  I thought I saw something about a thread pool in the source, but I'm new to Java and GroundWork and therefore not certain about how everything works.

[rfichoke]

Anybody home?

[Dr. Dave]

I don't have an answer on the initialize() questions you are asking
about. However, many customers us nscd or equivalent so that name
resolution is not as taxing as you would think. Also, define *quite*
high. While Foundation can store millions of log messages, is there
value in doing so unless many of them will match consolidation
criteria rules for your application?

On Feb 17, 8:35 am, rfichoke <rfich...@gmail.com> wrote:
> Anybody home?

[rfichoke]

Ultimately, we'll be processing (though not necessarily storing) several thousand messages per second.  Most of those will involve translating a hostname into an IP.  The alternative is to just use the hostname for the Device on the call to updateLogMessage().  I just don't know what the implications of that are because I'm not that familiar with the database schema yet.

I mean, there's Device, but there's also Host.  And there's a Monarch database that looks like it imposes some kind of logical layer on top of GWCollageDB.  But maybe I'm misunderstanding that.

The nscd approach is a good suggestion though.  I'll look into that.  Thanks!