Date parsed: 5/4/2000 1:30:07 PM
Date: Thu, 4 May 2000 12:30:07 +0200

Hi Daniel,

as you noticed already, the 'message extraction' feature didn't make it =
into
v2.1. Including this feature in v2.1 would have delayed the release of =
v2.1
for quite some time and I had to put v2.1 out the door as soon as =
possible,
because some customers needed the new v2.1 features badly.

The 'message extraction' feature is the top-priority item on the feature
list for the next version but currently I can't give you an exact date =
when
it will be available. My current estimation is 3Q/2000.

Franz



"Daniel Easley" <deasley@c-base.com> wrote in message
news:3A25DBCDF73F2245957BD0B041BEDAF00116B1@is1.netal.com...
> When will this message extractions feature be available?
>
> "Franz Krainer" <franzk@netal.com> wrote in message
> news:C1CEE8E342DDD111A5720020AFE7798F172708@is1.netal.com...
> > Yes, there are plans:
> >
> > One item on the feature list for the next (v2.1) version is to =
support
> > extracting of information elements of the message text (by using =
regular
> > expression syntax) and to make these extracted information elements
> > available
> > for all actions (including log-to-ODBC-DB).
> >
> > Franz
> >
> > "Chuck" <chuck@luedke.com> wrote in message
> > news:C1CEE8E342DDD111A5720020AFE7798F1720AE@is1.netal.com...
> > > Any plans to provide a method to break out the data portion of the
> > syslog
> > > entry into fields for sql data stores or to provide a coding hook =
for
> > the
> > > same purpose?
> > >
> > > Chuck
> > >
> >
>