DX Infrastructure Manager

Expand all | Collapse all

UIM metrics not posted in AXA 17.3.2 (standalone) on premise

  • 1.  UIM metrics not posted in AXA 17.3.2 (standalone) on premise

    Posted 02-18-2020 04:55 AM
      |   view attached
    Hello,
    I am trying to integrate UIM 9.2.0 with AXA 17.3.2 in my lab because one of our customer hasn't acquired a DOI license so he is using only AXA and UIM in its environment.
    He is trying to have AXA as a single point of checking metrics from all the rest monitoring systems like APM, UIM etc.

    I have used axagateway probe in UIM to send metrics to AXA but it seems something is not properly configured so I would like to ask your help to understand what I am doing wrong.

    The messages I mostly get in the log of axagateway probe are :
    1.
    Feb 18 11:45:11:766 [QOS_PROCESSOR_THREAD, axagateway] Cannot Send QoS Information to AXA as it doesn't satisfies the Selection Criteria.

    2.
    Feb 18 11:45:13:567 [QOS_PROCESSOR_THREAD, axagateway] For the QoS :: QOS_CPU_UTILIZATION probe( pollagent ) is not matching selection criteria.

    You can find axagateway's configuration attached.

    I have already manually added the related index patterns in kibana tool of AXA and I am currently trying to send the data from UIM to AXA.
    I checked that the related queues are getting messages from the probe and that the Sent value is always increasing, so I assume that the messages are sent.
    However I can't determine where is the problem (UIM configuration or AXA configuration).

    Can you help me identify the issue ?
    I know I am trying to make a custom configuration, but unfortunately this is what our customer has asked for.
    Thank you in advance

    ------------------------------
    Infrastructure Software-Systems Engineer
    ------------------------------


  • 2.  RE: UIM metrics not posted in AXA 17.3.2 (standalone) on premise

    Posted 02-18-2020 10:29 AM
    that is really not enough to go on.
    I would set the loglevel to 5 and logsize to 75000 and restart the probe and try to get more details.
    as you have only one HUB, origin and probe listed the message you are seeing is what I would expect if the message was from anything else.

    ------------------------------
    Gene Howard
    Principal Support Engineer
    Broadcom
    ------------------------------



  • 3.  RE: UIM metrics not posted in AXA 17.3.2 (standalone) on premise

    Posted 02-19-2020 02:33 AM
    Hello Gene,
    Log level was already set to 5 and logsize is 99999, so I didn't make any change.
    I deactivated the probe some minutes ago, cleared the log file and then activated it back, in order to attach a clean log file in this post.
    I am also attaching the configuration file in case you can take a look.
    Kind regards
    Vaggelis

    ------------------------------
    Infrastructure Software-Systems Engineer
    ------------------------------



  • 4.  RE: UIM metrics not posted in AXA 17.3.2 (standalone) on premise

    Posted 02-19-2020 03:02 AM
      |   view attached
    And the attach.

    ------------------------------
    Infrastructure Software-Systems Engineer
    ------------------------------

    Attachment(s)

    zip
    axagateway.zip   83K 1 version


  • 5.  RE: UIM metrics not posted in AXA 17.3.2 (standalone) on premise

    Posted 02-24-2020 10:59 AM
    in the logs we can see the following:
    Feb 19 09:26:36:861 [QOS_PROCESSOR_THREAD, axagateway] Pattern Map Values ({probe=(?i)^cdm$})
    Feb 19 09:26:36:861 [QOS_PROCESSOR_THREAD, axagateway] Pattern Map Values ({origin=(?i)^uim172_hub$, probe=(?i)^cdm$})
    Feb 19 09:26:36:861 [QOS_PROCESSOR_THREAD, axagateway] Pattern Map Values ({origin=(?i)^uim172_hub$, host=(?i)^.*, probe=(?i)^cdm$})
    Feb 19 09:26:36:861 [QOS_PROCESSOR_THREAD, axagateway] For the QoS :: QOS_EVL_COUNT probe( ntevl ) is not matching selection criteria.
    Feb 19 09:26:36:862 [QOS_PROCESSOR_THREAD, axagateway] For the QoS :: QOS_INTERFACE_QUEUEDROPSIN probe( pollagent ) is not matching selection criteria.
    Feb 19 09:26:36:862 [QOS_PROCESSOR_THREAD, axagateway] For the QoS :: QOS_INTERFACE_BYTESOUT probe( pollagent ) is not matching selection criteria.
    so it looks like currently, you have this setup for only one origin which is hub uim172_hub and one probe from that hub which is CDM.

    from your .cfg
    <qos_selection>
    included_hosts =
    included_origins = uim172_hub
    bulkconfig_enabled = false
    probe_regex = cdm
    metric_regex = .*
    </qos_selection>

    so all of the other messages will be dropped expect CDM probe messages from this hub. Have you set up QOS messages in CDM on this hub?

    I can see where CDM data is being posted.
    Feb 19 09:26:36:903 [QOS_PROCESSOR_THREAD, axagateway] Entering sendHttpRequest..doPost.
    Feb 19 09:26:36:903 [QOS_PROCESSOR_THREAD, axagateway] POST Json payload : { "documents": [{"header": {"product_id" : "ao","tenant_id" : "nbg-userstore","doc_type_id" : "itoa_metrics_uim","doc_type_version" : "1"},"body": [{"deviceType":"VirtualMachine","cs_id":"1027","metric_unit":"pct","product":"UIM","product_version":"9.2.0","origin":"uim172_hub","ip":"10.100.0.169","ci_name":"Total","metric_value":0.2203,"source":"10.100.0.169","probe":"cdm","dev_id":"DED3D9CCAAA587D393F843BBC9932DC64","target":"WIN-OUFA6BRHV5P","robot":"win-oufa6brhv5p","ci_id":"CFEBAC0DB1F88BCA1A6600C04ABCCB6DB","qos_name":"QOS_CPU_USAGE","ci_type":"System.CPU","metric_name":"System.CPU:Aggregate CPU Usage","hub":"uim172_hub","domain":"uim172_domain","host":"WIN-OUFA6BRHV5P","metric_type":"1.5:1","met_id":"MA24992760669C1A6D0AAE4D9DCB37FE9","timestamp":"2020-02-19T15:27:59Z"}]},{"header": {"product_id" : "ao","tenant_id" : "nbg-userstore","doc_type_id" : "itoa_metrics_uim","doc_type_version" : "1"},"body": [{"deviceType":"VirtualMachine","cs_id":"1027","metric_unit":"pct","product":"UIM","product_version":"9.2.0","origin":"uim172_hub","ip":"10.100.0.169","ci_name":"Total","metric_value":57.319486,"source":"10.100.0.169","probe":"cdm","dev_id":"DED3D9CCAAA587D393F843BBC9932DC64","target":"WIN-OUFA6BRHV5P","robot":"win-oufa6brhv5p","ci_id":"C7D2BF846523A92098964B8A8D55D5205","qos_name":"QOS_MEMORY_PERC_USAGE","ci_type":"System.Memory","metric_name":"System.Memory:Memory Usage","hub":"uim172_hub","domain":"uim172_domain","host":"WIN-OUFA6BRHV5P","metric_type":"1.6:2","met_id":"MA70A717C281390193690351E2A740A44","timestamp":"2020-02-19T15:27:59Z"}]},{"header": {"product_id" : "ao","tenant_id" : "nbg-userstore","doc_type_id" : "itoa_metrics_uim","doc_type_version" : "1"},"body": [{"deviceType":"VirtualMachine","cs_id":"1015","metric_unit":"pct","product":"UIM","product_version":"9.2.0","origin":"uim172_hub","ip":"10.100.0.121","ci_name":"Total","metric_value":3.7113,"source":"10.100.0.121","probe":"cdm","dev_id":"DFA5A67F8E3D33ECD2E85A6EC47F98460","target":"BMCREMEDY19.syntaxlab.local","robot":"bmcremedy19","ci_id":"C14265A92F45395DBEBED5BD466CBDA51","qos_name":"QOS_CPU_USAGE","ci_type":"System.CPU","metric_name":"System.CPU:Aggregate CPU Usage","hub":"uim172_hub","domain":"uim172_domain","host":"BMCREMEDY19.syntaxlab.local","metric_type":"1.5:1","met_id":"MD11B56B514B1AFDDAF96EEA5472177F2","timestamp":"2020-02-19T07:30:50Z"}]},{"header": {"product_id" : "ao","tenant_id" : "nbg-userstore","doc_type_id" : "itoa_metrics_uim","doc_type_version" : "1"},"body": [{"deviceType":"VirtualMachine","cs_id":"1015","metric_unit":"count","product":"UIM","product_version":"9.2.0","origin":"uim172_hub","ip":"10.100.0.121","ci_name":"Total","metric_value":0,"source":"10.100.0.121","probe":"cdm","dev_id":"DFA5A67F8E3D33ECD2E85A6EC47F98460","target":"BMCREMEDY19.syntaxlab.local","robot":"bmcremedy19","ci_id":"C14265A92F45395DBEBED5BD466CBDA51","qos_name":"QOS_PROC_QUEUE_LEN","ci_type":"System.CPU","metric_name":"System.CPU:Processor Queue Length","hub":"uim172_hub","domain":"uim172_domain","host":"BMCREMEDY19.syntaxlab.local","metric_type":"1.5:9","met_id":"M40E5E4E519DAA4D82F63BED1AF2C4023","timestamp":"2020-02-19T07:30:50Z"}]},{"header": {"product_id" : "ao","tenant_id" : "nbg-userstore","doc_type_id" : "itoa_metrics_uim","doc_type_version" : "1"},"body": [{"deviceType":"VirtualMachine","cs_id":"1015","metric_unit":"pct","product":"UIM","product_version":"9.2.0","origin":"uim172_hub","ip":"10.100.0.121","ci_name":"Total","metric_value":72.09766,"source":"10.100.0.121","probe":"cdm","dev_id":"DFA5A67F8E3D33ECD2E85A6EC47F98460","target":"BMCREMEDY19.syntaxlab.local","robot":"bmcremedy19","ci_id":"C9253BE687FE34EB5A8786D392B7006A3","qos_name":"QOS_MEMORY_PERC_USAGE","ci_type":"System.Memory","metric_name":"System.Memory:Memory Usage","hub":"uim172_hub","domain":"uim172_domain","host":"BMCREMEDY19.syntaxlab.local","metric_type":"1.6:2","met_id":"M24E3A4C44FF6DF070C2A39097831CBBE","timestamp":"2020-02-19T07:30:50Z"}]},{"header": {"product_id" : "ao","tenant_id" : "nbg-userstore","doc_type_id" : "itoa_metrics_uim","doc_type_version" : "1"},"body": [{"deviceType":"VirtualMachine","cs_id":"1015","metric_unit":"pct","product":"UIM","product_version":"9.2.0","origin":"uim172_hub","ip":"10.100.0.121","ci_name":"C:\\","metric_value":48.640708,"source":"10.100.0.121","probe":"cdm","dev_id":"DFA5A67F8E3D33ECD2E85A6EC47F98460","target":"C:\\","robot":"bmcremedy19","ci_id":"C4505F0FBF9D45128FCAB623E696008A2","qos_name":"QOS_DISK_USAGE_PERC","ci_type":"System.Disk","metric_name":"System.Disk:Disk Usage","hub":"uim172_hub","domain":"uim172_domain","host":"BMCREMEDY19.syntaxlab.local","metric_type":"1.1:3","met_id":"M06FE90ADE43C27B7F6C3642A439A5A86","timestamp":"2020-02-19T07:31:01Z"}]}]}
    Feb 19 09:26:36:907 [QOS_PROCESSOR_THREAD, axagateway] Total time to execute client request : 4
    Feb 19 09:26:36:957 [QOS_PROCESSOR_THREAD, axagateway] Not a valid json response object: ok
    Feb 19 09:26:36:957 [QOS_PROCESSOR_THREAD, axagateway] HTTP Request Status: 200

    So this looks to be working as you have it set up currently.

    Please review these keys in the documentation if you would like to change what is sent
    http://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/axagateway-ca-app-experience-analytics-gateway/axagateway-ac-configuration.html#concept.dita_392a53f40470eaf81a8bbf7d1fe7d6546b399aef_OptionalConfigureLoggingProperties




    ------------------------------
    Gene Howard
    Principal Support Engineer
    Broadcom
    ------------------------------