gcp - add stack driver logging initial setup #3820
Conversation
Dkhanas
force-pushed
the
logging
branch
2 times, most recently
from
b944d63
to
bd79995
Compare
Dkhanas
force-pushed
the
logging
branch
4 times, most recently
from
88400e6
to
155217c
Compare
Dkhanas
force-pushed
the
logging
branch
2 times, most recently
from
5546a63
to
6941b80
Compare
|
per comment in #4046, for any resource here implementing a get method, please also include a gcp api log test event to verify the assumptions being made about key structure of those events. |
Dkhanas
force-pushed
the
logging
branch
2 times, most recently
from
23f265b
to
589f72f
Compare
|
Removed "log-monitored-resource-descriptor" resource, and updated all get methods |
|
Generally, logs are considered as confidential information. As a use case, Custodian can control 'syncs' which are used to export log entries to other destinations withing GCP project. Logs-based 'metrics' can also be used to extract values from logs and can be considered as sensitive data too. Custodian can control absence/existence of a certain metrics and their content: for example, to make sure that there are no metrics which include logs of specific types/labels/sources and automatically delete them (upon enabling of such an action later). |
|
Hello @kapilt can we move on with this pr? |
| resource = p.run() | ||
| self.assertEqual(len(resource), 1) | ||
|
|
||
| def test_get_log_sink(self): |
There was a problem hiding this comment.
this test doesn't seem to be utilizing the event data
There was a problem hiding this comment.
Made test through event data
|
Hello @kapilt, can we move on with this pr? any questions/concerns - please let us know. |
Added initial classes with query and get functionality for projects sinks, sinks, metrics, log project, project, exclusions, log and monitored resource descriptors resources in Stackdriver logginig service