dynatrace-oss / dynatrace-azure-log-forwarder Goto Github PK

See:

ActiveGate state check checks if response from ${TARGET_URL}/rest/health equals RUNNING string, but mentioned ActiveGate endpoint returns "RUNNING", so check should expect \"RUNNING\" string.

Fixed code:

check_activegate_state() {
  if ACTIVE_GATE_STATE=$(curl -ksS "${TARGET_URL}/rest/health" --connect-timeout 20); then
    if [[ "$ACTIVE_GATE_STATE" != "\"RUNNING\"" ]]; then
      echo -e ""
      echo -e "\e[91mERROR: \e[37mActiveGate endpoint is not reporting RUNNING state. Please verify provided values for parameters: --target-url (${TARGET_URL})."
      exit 1
    fi
  else
      echo -e "\e[93mWARNING: \e[37mFailed to connect with provided ActiveGate url ($TARGET_URL) to check state. It can be ignored if ActiveGate does not allow public access."
  fi
}

As Dynatrace moves more managed Azure services to Custom Devices instead of discrete entity types, the linking between logs and entities is increasingly breaking. This is frustrating as logs and related events are linked to unavailable entities and can not use any of the metadata related to the correct custom devices. For example, log for an Azure SQL database will try to link to a legacy entity type instead of one of the new Custom Device types and clicking into the entity brings up a 404 page.

To resolve this, it would be nice if there was a parameter or property file that could be deployed to the Log Forwarder that would mark specific Azure entity types that have been migrated to new Custom Devices (since it would not be the same for all use cases or tenants) and have a lookup system in the forwarder to query for the right entity by typing metadata or name.