Forum Discussion
Helper IOn-premises Power BI Enterprise Data Gateway logs - missing (expected) log fields
Super Usergrabbing a copy of those items (what's shown in the PowerShell) works just fineThat is only half of the story. A last modified timestamp on a file does not reveal the actual last row of data written into that file. Again - our experience is that the gateway service only flushes data to the files occasionally, every couple hours at best and every 24 hours at worst.
Helper IObviously, some logs are (reused) in a round-robin fashion, some are not.
What the log Spooler does (when it writes to logs, etc.), needs to have the logic "plumbing" extended that (when you have a "log shipping" feature available) it does the best it can to empty what is buffered in the spooler, as part of that feature. (The fact that the spooler hasn't done a complete flush, could be controlled. Like enact the log shipping feature, which would roll into the next log sequence (closing all current log connection files, making them available for shipping).
Like here's a sample of what get's grabbed using the PowerShell mentioned:
(poop, my companies URL isolation security won't let me paste, nor upload that screenshot, but it's simple to run what's there in PowerShell - replacing the locations with yours 🙂
- lbendlin
We are using OneDrive as a cheap replacement for the log shipping process that you mention. But OneDrive can only sync what's flushed. Not bad, but also not sufficient for our needs.
- rkaratzas
so far so good for us (seeing what we are getting per ship cycle), but obviously, a log shipper feature (in the Gateway software) would keep most of us folks (like you and me) a lot happier 🙂
Again, our philosophy: "If you can't monitor it, you can't manage it"