te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数 大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数 大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>Azure Message-Triggered Logic App Workflow Open Telemetry Distributed Tracing with Data Dog - Stack Overflow

科技改变生活-雨落星辰 - 所有的伟大,都源于一个勇敢的开始

    最新消息：雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客
    你的位置： 首页>programmer>Azure Message-Triggered Logic App Workflow Open Telemetry Distributed Tracing with Data Dog - Stack Overflow

    Azure Message-Triggered Logic App Workflow Open Telemetry Distributed Tracing with Data Dog - Stack Overflow

    programmeradmin3浏览0评论

    I have an issue with Open Telemetry distributed tracing and Service Bus Message-triggered Logic App Workflows. We have OTEL and distributed tracing in Azure involving Web APIs, Azure Functions and Logic Apps.

    If a logic app workflow is HTTP-triggered, traceparent and diagnostic-id headers (with the same value) are passed in the HTTP headers and traces are produced correctly. The trace id is being extracted and used.

    If instead a logic app workflow is Azure Service Bus message-triggered, the traceparent and diagnostic-id values are passed as message properties (UserProperties in the message). Here is where we have the problem. In this case the logic app workflow does not extract and does not use the trace id that is passed. It creates and uses new trace ids for each step in the workflow.

    My hypothesis is that this is either some logic app limitation or we have some missing configuration.

    Here is an example of logged json message that triggers the logic app workflow.

    {
    "headers": null,
    "body": {
        "contentData": {
            "greeting": "hello"
        },
        "contentType": "application/json",
        "userProperties": {
            "traceparent": "00-3371dfda4f619ea823086e0945c089c3-ae3de3878ad08241-01",
            "diagnostic-id": "00-3371dfda4f619ea823086e0945c089c3-ae3de3878ad08241-01",
            "dataType": "test"
        },
        "messageId": "197ae0b969b54f17bb470ce017b83847",
        "scheduledEnqueueTimeUtc": "1/1/0001 12:00:00 AM",
        "timeToLive": "14.00:00:00",
        "deliveryCount": 1,
        "enqueuedSequenceNumber": 225,
        "enqueuedTimeUtc": "2025-02-12T15:03:02.614Z",
        "lockedUntilUtc": "2025-02-12T15:04:02.63Z",
        "lockToken": "27133a78-4d53-4df0-b97b-1e406f788864",
        "sequenceNumber": 5
    }
}

    The logic app Diagnostic Settings are the following:

     cpq-dv-diagnostic-log
 Datadog_DS_V2_700b9f7a

    We have also Data Dog Environment variables defined (I am putting the most relevant ones)

    DD_TRACE_DEBUG = true
DD_TRACE_OTEL_ENABLED = true
DD_TRACE_PROPAGATION_EXTRACT_FIRST = true
DD_TRACE_PROPAGATION_STYLE_EXTRACT = tracecontext,datadog
DD_TRACE_PROPAGATION_STYLE_INJECT = tracecontext,datadog

    Can U please suggest a solution? Thanks in advance.

    与本文相关的文章

    发布评论

    评论列表(0)

    1. 暂无评论