cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ITOM - Azure Monitor and Kubernetes API

alberto-jesus_d
Newcomer

Hi,

we are handling ITOM integration from Dynatrace to Service Now. There are a lot of events (https://www.dynatrace.com/support/help/dynatrace-api/configuration-api/alerting-profiles-api/get-pro...😞


  • APPLICATION_ERROR_RATE_INCREASED
  • APPLICATION_SLOWDOWN
  • APPLICATION_UNEXPECTED_HIGH_LOAD
  • APPLICATION_UNEXPECTED_LOW_LOAD
  • AWS_LAMBDA_HIGH_ERROR_RATE
  • CUSTOM_APPLICATION_ERROR_RATE_INCREASED
  • CUSTOM_APPLICATION_SLOWDOWN
  • CUSTOM_APPLICATION_UNEXPECTED_HIGH_LOAD
  • CUSTOM_APPLICATION_UNEXPECTED_LOW_LOAD
  • CUSTOM_APP_CRASH_RATE_INCREASED
  • DATABASE_CONNECTION_FAILURE
  • DATA_CENTER_SERVICE_PERFORMANCE_DEGRADATION
  • DATA_CENTER_SERVICE_UNAVAILABLE
  • EBS_VOLUME_HIGH_LATENCY
  • EC2_HIGH_CPU
  • ELB_HIGH_BACKEND_ERROR_RATE
  • ENTERPRICE_APPLICATION_PERFORMANCE_DEGRADATION
  • ENTERPRISE_APPLICATION_UNAVAILABLE
  • ESXI_GUEST_ACTIVE_SWAP_WAIT
  • ESXI_GUEST_CPU_LIMIT_REACHED
  • ESXI_HOST_CPU_SATURATION
  • ESXI_HOST_DATASTORE_LOW_DISK_SPACE
  • ESXI_HOST_DISK_QUEUE_SLOW
  • ESXI_HOST_DISK_SLOW
  • ESXI_HOST_MEMORY_SATURATION
  • ESXI_HOST_NETWORK_PROBLEMS
  • ESXI_HOST_OVERLOADED_STORAGE
  • ESXI_VM_IMPACT_HOST_CPU_SATURATION
  • ESXI_VM_IMPACT_HOST_MEMORY_SATURATION
  • EXTERNAL_SYNTHETIC_TEST_OUTAGE
  • EXTERNAL_SYNTHETIC_TEST_SLOWDOWN
  • HOST_OF_SERVICE_UNAVAILABLE
  • HTTP_CHECK_GLOBAL_OUTAGE
  • HTTP_CHECK_LOCAL_OUTAGE
  • HTTP_CHECK_TEST_LOCATION_SLOWDOWN
  • MOBILE_APPLICATION_ERROR_RATE_INCREASED
  • MOBILE_APPLICATION_SLOWDOWN
  • MOBILE_APPLICATION_UNEXPECTED_HIGH_LOAD
  • MOBILE_APPLICATION_UNEXPECTED_LOW_LOAD
  • MOBILE_APP_CRASH_RATE_INCREASED
  • MONITORING_UNAVAILABLE
  • OSI_DISK_LOW_INODES
  • OSI_GRACEFULLY_SHUTDOWN
  • OSI_HIGH_CPU
  • OSI_HIGH_MEMORY
  • OSI_LOW_DISK_SPACE
  • OSI_NIC_DROPPED_PACKETS_HIGH
  • OSI_NIC_ERRORS_HIGH
  • OSI_NIC_UTILIZATION_HIGH
  • OSI_SLOW_DISK
  • OSI_UNEXPECTEDLY_UNAVAILABLE
  • PGI_OF_SERVICE_UNAVAILABLE
  • PGI_UNAVAILABLE
  • PG_LOW_INSTANCE_COUNT
  • PROCESS_CRASHED
  • PROCESS_HIGH_GC_ACTIVITY
  • PROCESS_MEMORY_RESOURCE_EXHAUSTED
  • PROCESS_NA_HIGH_CONN_FAIL_RATE
  • PROCESS_NA_HIGH_LOSS_RATE
  • PROCESS_THREADS_RESOURCE_EXHAUSTED
  • RDS_HIGH_CPU
  • RDS_HIGH_LATENCY
  • RDS_LOW_MEMORY
  • RDS_LOW_STORAGE_SPACE
  • RDS_OF_SERVICE_UNAVAILABLE
  • RDS_RESTART_SEQUENCE
  • SERVICE_ERROR_RATE_INCREASED
  • SERVICE_SLOWDOWN
  • SERVICE_UNEXPECTED_HIGH_LOAD
  • SERVICE_UNEXPECTED_LOW_LOAD
  • SYNTHETIC_GLOBAL_OUTAGE
  • SYNTHETIC_LOCAL_OUTAGE
  • SYNTHETIC_NODE_OUTAGE
  • SYNTHETIC_PRIVATE_LOCATION_OUTAGE
  • SYNTHETIC_TEST_LOCATION_SLOWDOWN

The thing is that there are NO specific Azure os Kubernetes events like:

- Azure: Suscriptions, Regions, Functions, Load Balancer, Databricks, etc.

- Kubernetes: routing, namesspaces, pods.....in general any issue related to an Kubernetes or OpenShift cluster.

Is planned to get that info from the integration with Azure Monitor or Kubernetes API?

Thanks in advance.

Alberto.

3 REPLIES 3

wolfgang_beer
Dynatrace Champion
Dynatrace Champion

Hi Alberto,

By design our ServiceNow ITOM integration does only push events to ServiceNow ITOM that are part of a Davis Problem on the Dynatrace side. All other events that are not directly picket up by Davis are not pushed over, as those might be too many in general, a lot of info purpose only events.

By using our events API you can of course read all the events from Dynatrace and put them into the ITOM event table, by adding some customization on the ServiceNow side.

Our Professional Services team would be happy to help you with that request, if you need some help doing that on the ServiceNow side.

Best greetings,

Wolfgang

Thanks for your answer. The thing is that I don't see any "Problem" detected by David which its root cause is based on an event os Kubernetes or Azure. I have check all my tenant, even demo.live and I didn't find it out.

Is it possible? Is David able to detect the root cause of a problem based on events not just metrics?

Thanks.

Alberto.

wolfgang_beer
Dynatrace Champion
Dynatrace Champion

Davis is also taking into account events, traces and not just metrics. Reason for your K8S events is that those events are not fed into Davis so far. We are working on that at the moment, so you will see those events as well in the upcoming weeks.