| >How can I get the notification number also start again? (automatically)
There's no way to do this.
>If you receive lots ( because of PCSA , the customer what to know when all nodes
>go up and down), the max number of notifications is reached fairly quickly, even
>if you set a high number.
Are you confusing the "ID" number that identifies
each notification and the customizable number that determines the size of
the notification buffer? The two are numbers are independent.
A notification ID is just a tag to help users "name" a notification.
The buffer size controls how many notifications can be kept in memory.
>Also having the counter restart at midnight the customer has an idea on the
>number of events per day.
There are a whole lot of things that we should be able to do with
notification data that we presently can't do. Among them:
- record them permanently in a more usable format than
plain ascii
- retreive/playback recorded notifications via the same or similar
presentation mechanisms
- use various powerful visualization tools to help perform
various management tasks based on notification data
- share the data intelligently among various interested
managers
TeMIP did some of these things already by putting another layer on top
of the events/notifications to create "alarm objects". The next generation
of notification services should probably move in a similar direction
rather than one-plussing the current design.
|