...
For information about how to enable dynamic peer discovery, see the section Realm Routing Table in 9.1617.2.2 Diameter Routing Profile.
Filtering
In the Event Setup tab, the values for all the event fields are set by default to All in the Match Value(s) column, which will generate event notifications every time a Diameter dynamic event is generated. Double-click on the field to open the Match Values dialog where you can click on the Add button to add which values you want to filter on. If there are specific values available, these will appear in a drop-down list. Alternatively, you can enter a hard coded string or a regular expression.
...
| Info |
|---|
| title | Example - Diameter Dynamic event notification saved in a Log File |
|---|
|
 Image Removed Image Added
This configuration will give you the following notification setup: - When dynamic peer discovery is enabled and the peers of a realm are looked up in DNS, a notification will be generated.
- When this notification is generated, a new line with information will be logged in the diameter_dynamic_event.txt file located in the /home/user/diameter folder, containing the following data:
- The timestamp for when the event was triggered
- The realm name
- A list of peers in the realm
|
...
| Info |
|---|
| title | Example - Diameter Dynamic event notification saved in a database |
|---|
|
Image Removed Image Added This configuration will give you the following notification setup: - When dynamic peer discovery is enabled and the peers of a realm are looked up in DNS, a notification will be generated.
- When this notification is generated, an entry will be added in the diameterdynamic table in the database:
- The timestamp from the EC will be inserted in the timestamp column in the database table.
- The realm name will be inserted in the realm column in the database table.
- The peer information (hostname, port, protocol) will be inserted in the peers column in the database table.
|
...
