DX Unified Infrastructure Management

 View Only
  • 1.  messagegtw v1.44 probe log 5 not showing payload content

    Posted Oct 22, 2020 03:49 PM
    Hello,
    Does anyone know why or how to get the messagegtw probe to show the actual payload package it builds and sends out in the logs? I was previously running version 1.29 and at log level 3 it would show this in the logs. It was great. 
    Example:
    Oct 21 16:11:12:355 [/UIM_PROD_to_SNOW, messagegtw] DefaultHttpclient.sendHttpRequest:197: << Response: {"records":[{"resolution_state":"New","processing_sn_node":"","description":"DISK - X:\\ is now 70319 MB ( 68.7 GB - 5% ), which is below the threshold 204103 MB ( 199 GB - 15% ) out of total size 1328.8 GB ( 100% )","source":"CAUIM-PROD-MsgGtw","sys_updated_on":"2020-10-21 20:11:12","type":"cdm","ci_identifier":"","sys_id":"b47af1f81b802010a24974c4bcbe7","sys_updated_by":"SVC_EVENT","ci_type":"","metric_name":"cdm-Disk","processing_notes":"","sys_created_on":"2020-10-21 20:11:12","sys_domain":"3910746adb4276e8c30cf9d96194c","state":"Ready","message_key":"RV51944083-32012","sys_created_by":"SVC_EVENT","time_of_event":"2020-10-21 20:11:12","__status":"success","severity":"4","error_msg":"","cmdb_ci":"","resource":"Disk","sys_mod_count":"0","classification":"0","sys_domain_path":"","sys_tags":"","bucket":"64","node":"xxxxxsql","processed":"","additional_info":"{'ClientName':'xxx','Robot':'xxx'}"

    I then upgraded to v1.44 and even at log level 5 it just still only shows basic, entries.
    Oct 22 15:40:14:100 [pool-5-thread-14, messagegtw] UimMessageListener.lambda$processIncomingMessages$0:301: Done processing message [0]
    Oct 22 15:40:14:741 [/UIM_PROD_to_SNOW, messagegtw] UimMessageListener.processIncomingMessages:339: Listener /UIM_PROD_to_SNOW successfully took 3 messages off the queue in 642ms
    Oct 22 15:40:25:552 [/UIM_PROD_to_SNOW, messagegtw] UimMessageListener.processIncomingMessages:289: Incoming PDS array contains 2 messages. Initializing latch to same size.
    Oct 22 15:40:25:553 [pool-5-thread-12, messagegtw] UimMessageListener.lambda$processIncomingMessages$0:301: Done processing message [0]

    It doesn't show me the package it sends out and doesn't show me the response back from end point.
    Something went wrong in this version and I need the logs to show the package content so I can check issues.

    ------------------------------
    Daniel Blanco
    Enterprise Tools Team Architect
    DBlanco@alphaserveit.com
    ------------------------------


  • 2.  RE: messagegtw v1.44 probe log 5 not showing payload content

    Posted Oct 23, 2020 10:48 AM
    Don't have a setup to test so from a general perspective as a test:
    deploy the old version of the probe so see if the log populates again
    deactivate, rename the probe folder, redeploy, test

    ------------------------------
    Support Engineer
    Broadcom
    ------------------------------



  • 3.  RE: messagegtw v1.44 probe log 5 not showing payload content

    Posted Nov 02, 2020 12:25 PM
    Hi Dave, yeah no that didn't do anything. I have 2 instances and they both do the same behavior.
    DEV needs to fix this so I can debug issues now.

    ------------------------------
    Daniel Blanco
    Enterprise Tools Team Architect
    DBlanco@alphaserveit.com
    ------------------------------



  • 4.  RE: messagegtw v1.44 probe log 5 not showing payload content

    Posted Nov 03, 2020 04:11 AM
    Hi Daniel,

    See if loglevel = 6 helps you. I use the probe, but at loglevel 5 am able to see my payload messages.
    Extract from my log:
    Nov 03 10:04:54:195 [/alarms, messagegtw] UimMessageListener.publishEvent:360: Attempting to publish to AMQP Exchange: EIS,Routing Key: ****.****.INBOUND.CA-UIM,AMQP Connection details following,Hostname: ****.****.****.com,Port: 5671,Username: **-****-uat,Password: ******
    Nov 03 10:04:54:320 [/alarms, messagegtw] RabbitMqMessagePublisher.publish:85: publishing to exchange EIS with routing key ****.****.INBOUND.CA-UIM, payload: {"events":[{"severity":2,"metric_id":"M59f59591b69a0d2640df539c4da9f968","source_management_platform":"cauim","description":"QOS_INTERFACE_OPERSTATUSPOLLABLE \u003d 2.0 from source east_ADC-DEV02_001 targeting Fa1/2(FastEthernet1/2) has crossed the major static threshold of !\u003d1.0","source":"CHADC-DEV02P001-ONP-EU_NL_AMS","metric_class":"MetricFamily.Interface","ci_id":"DD-east.ADC-DEV02","name":"QOS_INTERFACE_OPERSTATUSPOLLABLE \u003d 2.0 from source east_ADC-DEV02_001 targeting Fa1/2(FastEthernet1/2) has crossed the major static threshold of !\u003d1.0","event_name":"static_threshold.major.source_and_target","company":"ADC-DEV02","alarm_id":"UB51151187-07763","source_id":"M59f59591b69a0d2640df539c4da9f968","category":"Availability","close_on_inactive_after":3600,"last_modified":1604394294,"status":"Active"}]}
    Nov 03 10:04:54:320 [/alarms, messagegtw] UimMessageListener.processIncomingMessages:339: Listener /alarms successfully took 1 messages off the queue in 188ms

    ------------------------------
    Chris
    ------------------------------