'reporting' Database

DX NetOps Spectrum
Report Manager (SRM) uses a MySQL database named 'reporting' to store data. This database contains all the tables that are required to store the data that is used by SRM application to generate reports.
casp1031
At startup, the
DX NetOps Spectrum
Report Manager retrieves the data from the primary Archive Manager for each SpectroSERVER through OneClick and stores the data in the SRM databases.
Following is the list of tables and views in the '
reporting
' database.
3
The relations shown in the following diagrams merely indicate table relations. They do not indicate 1:1 or 1: many relations.
Interpret the column icons as indicated below:
'reporting' database_Primary Key.png
- Represents a Primary Key
'reporting' database_NOT NULL attribute.png
- Simple NOT NULL column
'reporting' database_NULL attribute.png
- Simple column which can be NULL
Tables
alarm_user
Description
This table lists the users who can manage the alarms in
DX NetOps Spectrum
.
Columns
Field
Type
Null
Key
Default
Extra
Comment
alarm_user_name
char(255)
NO
UNI
Name of the
DX NetOps Spectrum
user, who can manage the alarms.
alarm_user_key
int(10) unsigned
NO
PRI
auto_increment
Unique key for each user, who manages the alarm in
DX NetOps Spectrum
Relations
imageanil.JPG
alarmactivity
Description
The alarmactivity table stores all the alarm activity that is monitored by SRM. The activity field denotes the type of alarm event generated. This field can be one of the following:
  • Set alarm event
  • Acknowledge alarm event
  • Assign troubleshooter alarm event
  • Clear alarm event
  • User cleared alarm event
  • Assign trouble ticket alarm event
Columns
Field
Type
Null
Key
Default
Comment
user
char(50)
NO
MUL
Name of the user, handling the alarm
time
datetime
NO
MUL
0000-00-00 00:00:00
Time of the activity performed in the alarm.
data
char(255)
YES
alarm_key
int(11) unsigned
NO
MUL
Key value for specific type of Alarms.
activity
int(10) unsigned
NO
MUL
Activity that is performed by the user on the specific alarm.
Relations
AlarmactivityNew.jpg
alarmcondition
Description
This table represents the alarm criticality and condition.
Columns
 
Field
Type
Null
Key
Default
Comment
criticality
tinyint(2)
NO
UNI
Criticality of the alarm like Minor, Major, Critical
condition_name
varchar(11)
NO
Condition name of the alarm, which is mapped to the criticality.
condition_id
int(10) unsigned
NO
PRI
Unique ID for the alarm condition.
Relations
alarminfo
Description
This table contains all the alarm information including the assignee and trouble ticket IDs.
The alarminfo table stores relevant information for an alarm. There is one entry per unique alarm id, as opposed to the alarmactivity table which can have multiple entries for a single Alarm ID. An entry in this table is created when a “set alarm event” is received by SRM. The table is updated through the life of the alarm as each of the other alarm events are received by SRM.
Columns
  
Field
Type
Null
Key
Default
Comment
set_troubleticket_user_key
int(10) unsigned
YES
MUL
Trouble ticket user key for the specific alarm.
set_troubleticket_time
datetime
YES
Time of the trouble ticket assigned.
set_troubleticket_id
char(255)
YES
Trouble ticket ID of the alarm.
set_time
datetime
YES
MUL
Originated time of the alarm.
persistent
int(10) unsigned
YES
MUL
2
orig_event_type
int(10) unsigned
YES
Originating event type for the alarm.
orig_event_key
bigint(20) unsigned
YES
Originating event key for the Alarm.
model_key
int(10) unsigned
NO
MUL
0
Unique model key for each alarm.
model_h
int(10) unsigned
NO
MUL
Model handle of the device, which has the alarm on it.
last_assigning_user_key
int(10) unsigned
YES
MUL
last_assigned_user_key
int(10) unsigned
YES
MUL
last_assigned_time
datetime
YES
landscape_h
int(10) unsigned
NO
Landscape handle of the server, where the alarm present.
impact_severity
int(10) unsigned
NO
0
Severity of the alarm.
first_assigning_user_key
int(10) unsigned
YES
MUL
first_assigned_user_key
int(10) unsigned
YES
MUL
first_assigned_time
datetime
YES
First assigned time of the alarm to specific user.
condition_id
int(11)
YES
Condition of the alarm, which is mapped to the criticality.
clear_user_key
int(10) unsigned
YES
MUL
clear_user
char(50)
YES
User who acknowledge the alarm.
clear_time
datetime
YES
When the alarm is cleared from
DX NetOps Spectrum
.
cause
int(10) unsigned
YES
MUL
Cause/Event ID of the specific alarm.
alarm_title_id
int(10) unsigned
NO
MUL
1
Unique ID for alarm title.
alarm_key
int(11) unsigned
NO
PRI
Unique ID for each alarm present in
DX NetOps Spectrum
alarm_id
char(36)
NO
UNI
Alarm ID for specific type of alarms.
ack_user_key
int(10) unsigned
YES
MUL
Specific key for the user who acknowledges the alarm.
ack_time
datetime
YES
When the user acknowledge the alarm.
Relations
AlarmInfoNew.jpg
alarmtitle
Description
This table represents the title information of
DX NetOps Spectrum
alarms.
Columns
  
Field
Type
Null
Key
Default
Extra
Comment
title
varchar(255)
YES
Title of the Alarm.
cause_id
int(10) unsigned
NO
MUL
Cause or Event ID of specific type of alarm in
DX NetOps Spectrum
alarm_title_id
int(10) unsigned
NO
PRI
auto_increment
Unique ID for each alarm present in
DX NetOps Spectrum
.
Relations
AlarmTitileNew.jpg
backups
Description
This table contains list of database backups.
bo_only_user
Description
This table includes the Business object user information.
boxi_user_sync
Description
This table includes the Business object user sync information.
bucketactivitylog
Description
This table includes the event information from the landscape to process in SRM database.
ca_reportstrings
Description
This table represents the information of localized string for the identifier.
configchangelog
Description
This table contains the information about NCM configuration file and logs.
Columns
   
Field
Type
Null
Key
Default
Extra
Comment
last_modified
bigint(20)
NO
Last_Modified time of the configuration file.
id
int(10) unsigned
NO
PRI
auto_increment
Unique ID of Configuration file.
filename
varchar(255)
NO
Name of the Configuration file.
content
blob
NO
Content of the configuration file
contentpkg
Description
This table represents the installation content package information.
The contentpkg table associates content packages with Crystal Enterprise folder IDs. This table is not meant to be reported against, but instead is actually used by the Report Manager to help identify installation and security issues. A content package might only be installed once and this table helps identify if that is the case.
creator
Description
This table includes the model creator information.
Relations
CreatorNew.jpg
data_retention_policy_changelog
Description
This table includes the information about the data retention policy.
devicemodel
Description
This table represents the complete device model information.
The devicemodel table is filled in initially as the Report Manager extracts model information from the respective SpectroSERVERs. New records are added by the Report Manager as it responds to model creation events for device models.
Certain attributes of this table can change and as such the Report Manager needs a way to keep up with these changes. To keep up with these changes, the Report Manager periodically requests current values for these attributes. These requests are made to the appropriate models through the OneClick architecture. Initially this period for updating device data is set to once every 24 hours.
The user-defined fields are to be left blank, but provide the administrator an opportunity to extend the Report Manager database to include data that is applicable to their assets.
Relations
devicemodelNew.jpg
devicemodel_uda
Description
The devicemodel_uda table contains user-defined polling attribute information.
devicemodule
Description
This table includes the chassis information like module name, serial number etc.
This table captures the relationship between Chassis device models and the board modules contained within. This table is dynamically kept up to date.
Relations
devicemoduleNew.jpg
Columns
(till 10.2.1 release)
Field
Type
Null
Key
Default
Extra
module_id
int(10) unsigned
NO
PRI
NULL
auto_increment
model_key
int(10) unsigned
YES
MUL
NULL
module_index
int(10)
YES
NULL
module_name
varchar(255)
YES
NULL
serial_nbr
varchar(255)
YES
NULL
software_rev
varchar(255)
YES
NULL
Columns
(from 10.2.2 release)
Field
Type
Null
Key
Default
Extra
module_id
int(10) unsigned
NO
PRI
NULL
auto_increment
model_key
int(10) unsigned
YES
MUL
NULL
physical_index
int(10)
YES
NULL
physical_modelname
varchar(255)
YES
NULL
physical_name
varchar(255)
YES
NULL
physical_class
int(10)
YES
NULL
physical_contained_in
int(10)
YES
NULL
serial_nbr
varchar(255)
YES
NULL
software_rev
varchar(255)
YES
NULL
entity
Description
This table maintains distinct devices/interfaces across ALL landscapes.
The entity table is used to identify all entities uniquely that can be reported on. As new unique entities are added to the database, new entity records are created. Entity table record creation is closely tied to devicemodel and interfacemodel table record creation. The current_model, create_time, and destroy_time columns always correspond to the most recently created model.
Relations
entityNew.jpg
entitygroup
Description
This table is about taking t