Skip to main content

Our 23.10 deployment complains about BAM Reporting filters being too restrictive, 

>2024-05-14T11:56:10.947+03:00] config] error] endpoint applier: The configured write filters for the endpoint 'centreon-bam-reporting' are too restrictive and will be ignored. bam categories are mandatory.
>2024-05-14T12:22:35.887+03:00] config] error] endpoint applier: The configured write filters for the endpoint 'centreon-bam-reporting' are too restrictive and will be ignored. bam categories are mandatory.
 

but BAM filter is selected and enabled, so to me this error makes no sense.

central-broker.json content for centreon-bam-reporting

            {
                "type": "bam_bi",
                "filters": {
                    "category":  
                        "bam"
                    ]
                },
                "check_replication": "no",
                "queries_per_transaction": "0",
                "db_port": "3306",
                "db_type": "mysql",
                "db_name": "centreon_storage",
                "db_password": "redacted",
                "db_user": "redacted",
                "db_host": "redacted",
                "name": "centreon-bam-reporting"
            },

 

Is this a bug?

Hi @thakala I’m on 24.04.0 with same configuration and I don’t have this error.

Did you use the last version of Centreon Broker component?

Do you have Centreon BAM reporting available?


We are not necessarily on latest patch release

  • centreon-broker-23.10.5-1.el9.x86_64
  • centreon-broker-core-23.10.5-1.el9.x86_64
  • centreon-broker-cbd-23.10.5-1.el9.x86_64

Yes we have BAM reporting deployed.


Latest version is 23.10.6-1 for centreon-broker and this version fix some issues with BAM.

You can try to update it.

Release note: https://docs.centreon.com/docs/23.10/releases/centreon-os/#23106-1


Yes 23.10.6-1 upgrade is planned for later this week as it also contains one of our reported crash bug for cbd, we just have limited number of maintenance windows for each month. But I guess we have a consensus that this is a bug as configuration should be valid.


Reply