Configure filter for audit
Define filtering conditions to control the scope of Telecom Discrepancy audits. These filters ensure that audits run only on the desired set of CIs, improving performance and targeting accuracy.
Antes de Iniciar
Role required: admin
Por Que e Quando Desempenhar Esta Tarefa
Understanding Filtering Conditions in Telecom Discrepancy Audits
- Audits use filtering conditions to narrow the scope of CIs being evaluated.
- Filtering conditions are essential for narrowing down audit targets.
- You can define and modify conditions per audit instance to meet specific audit requirements.
- Filtering by
discovery_sourceis a common condition to filter records associated with particular integration sources (e.g., TSOM and Altiplano). Additionally, you can customize the filter according to the audit requirements. - Each version of the audit can have a different filtering condition.
The following are the audit filters:
- Telecom Logical Connections Discrepancy Audit: This audit runs at the logical connection table. The default filter condition is defined as
discovery_sourcelike TSOM. This condition is applied on each CI in the logical connection table. - Telecom Network Topology Discrepancy Audit: This audit runs at the network topology table. The default filter condition is defined as
discovery_sourcelike TSOM. This condition is applied on each CI in the network topology table. - Telecom Discrepancy Audit: This audit runs at the relationships table. The default filter condition is defined as
discovery_sourcelike TSOM. This condition is applied on each CI at the equipment level.
The following screenshot helps to understand the user interface of the certification filter .
Procedimento
Resultado
You can use the filter in the logical connection audit.