clef.exe import exported loggins - traceid missing and no trace timings #2329
-
Hello, I'm looking at the SEQ import functionality by using CLEF files. I exported one day of logging in two ways:
Both ways are configured like documented on the SEQ website. However, upon import using the latest clef.exe, I notice that a lot of information is missing after import. I see these new columns after import, which were not there before: Did I do anything wrong? UPDATE! I did some searching and debugging and I noticed the following. When importing from a clef file, it seems that something goes wrong with the @sp and @tr tags? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @TomDC-DX,
On Windows, Hope this helps, |
Beta Was this translation helpful? Give feedback.
Hi @TomDC-DX,
clef.exe
is in maintenance mode and hasn't been updated to support these newer properties. Instead, tryseqcli ingest --json -i <FILENAME>
using a recent version ofseqcli
.On Windows,
seqcli
should already be on your path if you have Seq installed on Windows; it's also available as adotnet tool
, binaries, or as a Docker container. Check out https://github.com/datalust/seqcli for all the info.Hope this helps,
Nick