What data is the Write-Telemetry function sending to posthog? #662
Replies: 2 comments
-
|
Actually, I might have posted this in haste. I think I get what it does so if someone could just validate if I'm right I'd appreciate.
So the only thing Maester is tracking is the TenantID of the tenant Maester was used it. I'm assuming the intent is to understand how often and how widely Maester is being implemented. I didn't realize the DisableTelemetry flag were present as well so I can stop this behavior. This is probably an open and shut discussion but still would love some feedback. |
Beta Was this translation helpful? Give feedback.
-
|
@gabecorsini yes, we only track the tenantId each time Invoke-Maester is called, no other information is sent. We do this so we can track usage (one tenant running many tests vs and multiple tenants) and yes it can be disabled with the DisableTelemtry |
Beta Was this translation helpful? Give feedback.
-
I got an interesting question from my team about whether Maester sends any of our data outside of its usage on a localhost. While I initially said no, I decided to dig a little into the module itself and I noticed the Write-Telemetry module, which is taking in an $Event parameter and sending it to a posthog endpoint with an API key.
Can someone explain what is actually getting sent to posthog? How much data about my environment is being sent to a log collection source that I can't access? As an organization that's trying to leverage this tool for writing custom tests to monitor configuration changes to compliance configurations, we are concerned about where our data goes if it's not just producing reports on the host that runs the module.
Thanks for any insight y'all can provide. While the obvious answer for us would just be to fork the repo and unwind the telemetry portion so we don't have that worry, that would make it hard to get the new updates as Maester improves (I think, I'm a git noob so I could be wrong).
Cheers!
Beta Was this translation helpful? Give feedback.
All reactions