forked from docs/doc-exports
Reviewed-by: Mützel, Andrea <andrea.muetzel@t-systems.com> Co-authored-by: Liu, Siying <liusiying@noreply.gitea.eco.tsi-dev.otc-service.com> Co-committed-by: Liu, Siying <liusiying@noreply.gitea.eco.tsi-dev.otc-service.com>
12 lines
891 B
HTML
12 lines
891 B
HTML
<a name="cts_faq_008"></a><a name="cts_faq_008"></a>
|
|
|
|
<h1 class="topictitle1">Does CTS Support Integrity Verification of Trace Files?</h1>
|
|
<div id="body1481802609182"><p id="cts_faq_008__p8060118">Yes. The following fields must be included in trace files: <strong id="cts_faq_008__b842352706151053">time</strong>, <strong id="cts_faq_008__b842352706151057">service_type</strong>, <strong id="cts_faq_008__b84235270615118">resource_type</strong>, <strong id="cts_faq_008__b842352706151115">trace_name</strong>, <strong id="cts_faq_008__b842352706151120">trace_rating</strong>, and <strong id="cts_faq_008__b842352706151124">trace_type</strong>. Other fields can be added by the services from which traces are collected.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001410799284.html">FAQs</a></div>
|
|
</div>
|
|
</div>
|
|
|