model.model_name in the Spectrum Report Manager reporting database is not populated for some port models
search cancel

model.model_name in the Spectrum Report Manager reporting database is not populated for some port models

book

Article ID: 281243

calendar_today

Updated On:

Products

Network Observability Spectrum

Issue/Introduction

We are using Grafana to display information from the Spectrum Report Manager (SRM) reporting database. We noticed that for some port models, the model_name field in the model table is blank as seen when running the below mysql query:

/mysql --defaults-file=../my-spectrum.cnf -uroot -p<PASSWD> reporting -e "select * from model where model_h like "2197816928";"

You will notice the model_name column is blank.

+-----------+------------+------------+---------+-------------+-----------------+---------------------+-------------+--------------+-----------------+-----------------+-----------+------------------+
| model_key | model_h    | model_name | mtype_h | model_class | network_address | first_event_time    | landscape_h | destroy_time | security_string | isClusterEntity | tenant_id | SDM_Host_Address |
+-----------+------------+------------+---------+-------------+-----------------+---------------------+-------------+--------------+-----------------+-----------------+-----------+------------------+
|      3926 | 2197816928 |            | 2162868 |          15 | 10.255.68.54    | 2024-01-25 08:38:18 |  2197815296 | NULL         |                 |               2 |        -1 | 0.0.0.0          |
+-----------+------------+------------+---------+-------------+-----------------+---------------------+-------------+--------------+-----------------+-----------------+-----------+------------------+

Environment

Version: Any
Component: Spectrum Report Manager

Cause

We have identified the root cause to be with event generation which does not set the model name in the event itself. Since the model name is not in the event then it does not get populated in the reporting database.

Resolution

The resolution for this issue is targeted for DX NetOps Spectrum 23.3.8.