![]() That's fine in an on-premise solution or a cluster that you own, but when sending metrics into the cloud, there must be a better option. Even if there was, there isn't much support for authentication and encryption with Statsd either. One important point to note is that there is no Grafana Cloud Statsd server to send metrics to. Let's take a look at what I discovered and see if that was enough to alleviate my concerns I'd certainly not even do that if my metrics were stored on-premise or my own cluster.Īuthentication The transport for sending metrics must have both authentication and encryption PII I would make sure to not send any personally identifiable information. For me, purely based on my interactions with the open-source Grafana and their Github issues. Trust Obviously the first thing is that you need to have a level of trust with the place you're sending metrics. Well, I have a couple of thoughts on that. The first thing that might cross your mind is questioning whether it is safe to put your metrics into the cloud.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |