Don't automatically label all resources

Question

Don't automatically label all resources

datnth-cavn opened this issue a year ago · 2 comments

I installed it with the default settings, but there are no labeled resources. I also tried the manual trigger but it didn't work.
I have provided some information below
Thanks.

./deploy.sh

2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Sent do_label message for acoustic-gizmo-400701 , Subscriptions
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Finished publisha attempt   iris_schedulelabeling_topic: {"project_id": "acoustic-gizmo-400701", "plugin": "Topics"}
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Sent do_label message for acoustic-gizmo-400701 , Topics
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Finished publisha attempt   iris_schedulelabeling_topic: {"project_id": "<project-id>", "plugin": "Bigquery"}
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Sent do_label message for <project-id> , Bigquery
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Finished publisha attempt   iris_schedulelabeling_topic: {"project_id": "<project-id>", "plugin": "Buckets"}
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Sent do_label message for <project-id> , Buckets
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Finished publisha attempt   iris_schedulelabeling_topic: {"project_id": "<project-id>", "plugin": "Cloudsql"}
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Sent do_label message for <project-id> , Cloudsql
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Finished publisha attempt   iris_schedulelabeling_topic: {"project_id": "<project-id>", "plugin": "Disks"}
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Sent do_label message for <project-id> , Disks
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Finished publisha attempt   iris_schedulelabeling_topic: {"project_id": "<project-id>", "plugin": "Instances"}
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Sent do_label message for <project-id> , Instances
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Finished publisha attempt   iris_schedulelabeling_topic: {"project_id": "<project-id>", "plugin": "Snapshots"}
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Sent do_label message for <project-id> , Snapshots
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Finished publisha attempt   iris_schedulelabeling_topic: {"project_id": "<project-id>", "plugin": "Subscriptions"}
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Sent do_label message for <project-id> , Subscriptions
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Finished publisha attempt   iris_schedulelabeling_topic: {"project_id": "<project-id>", "plugin": "Topics"}
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; Sent do_label message for <project-id> , Topics
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; schedule() sent 16 messages to label 2 projects
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; GAEInst x100no {'schedule': 1}; end schedule; RAM 398m; Libs:[pubsub_v1,resourcemanager_v3];
2024-01-10 06:42:25 iris3[20240110t044551]  INFO; iris_auto_label; Trace: 2ede21;o=1; /schedule; timing: schedule(): 4350 ms

config.yaml
# Copy this to make your config.yaml;
# You can also make  config-dev.yaml and config-test.yaml

# The default values as-is should work out-of-the-box.

# Keys:

# projects: Only resources in these projects will get labeled.
# But if the value is empty, *all* projects in the organization are included.
projects: []
#  - projects/<project-id>

# plugins: Only these plugins are enabled.
# For example, add some of these to tiris3/uninstall_scriptshe list:
#     bigquery, buckets, disks,  cloudsql, instances, snapshots, subscriptions, topics
# But if the value is empty, *all* plugins are enabled.
plugins: []

# iris_prefix plus underscore is prefixed to the key of each label that is added.
#    If empty string is used (the default), then no prefix and no underscore is addded.
iris_prefix: iris_auto_label

# specific_prefixes gives a prefix per resource type, instead of iris_prefix.
# The default is that there is no override.
# About the meaning of null (missing) values vs empty-string:
#  - A null (missing) value, as in the Buckets ex ample below,
#   will not replace the general iris_prefix.
#  -  Empty string as "", as in the Bigquery example below, overrides
#   the iris_prefix, so that you get labels with no prefix.
# For an example, see the comment below.
specific_prefixes: {}

# Example:
# specific_prefixes:
#   Buckets:
#   Bigquery: ""
#   Cloudsql: sql
#   Disks: gcedisk
#   Instances: gce
#   Snapshots:
#   Subscriptions:
#   Topics:

# If from_project is True, then for each resource we are labeling, copy the labels from its project onto it.
# The default is False.
from_project: True

# If label_all_on_cron is False (the default), then to save money,
#  only resources of certain types get labeled on cron: those whose plugins either
#    - return True on relabel_on_cron() (like Disks)
#    - or return False in is_labeled_on_creation() (like Cloud SQL)
# If it isTrue, then all resource types will be labeled on every Cloud Scheduler cycle.
#   This is useful for labeling existing resources when you first launch Iris3.

label_all_on_cron: True

# Optionally change this token before first deployment for added security in
# communication between PubSub and the Iris App on App Engine.
# You could even re-generate a new token per deployment.
# Note that this token-based approach is not very secure, though it  was once recommended by Google.
# However, so long as the GCP project running the Iris3 AppEngine service is otherwise secure,
# this token protects against unwanted invocations of labeling.
pubsub_verification_token: 0b0a30cde7e3489f0a9cd74bb51c514d

# If running (i.e., in AppEngine) in a project with one of the strings in the name,
# then *scheduled* labelings (those created by the Cloud Scheduler)
# will fail if more than 3 projects are enabled.
# This is intended to prevent a situation where you forget to limit the scope of
# labeling in development (see "projects" key above),
# and so accidentally labeling your entire org with test-labels.
test_or_dev_project_markers:
  - playground
  - test
  - dev
  - qa

Answer 1 · 2024-01-10T09:07:38.000Z

What is the "manual trigger", please? Do you mean that you triggered Cloud Scheduler manually?
Is your goal to label all existing resources? This can be done as described here.. But perhaps that is what you did.
Thank you for the logs. It seems that PubSub messages were sent, but that they never reached the /do_label endpoints. This probably means that the PubSub topics/subscriptions are not set up correctly. If you would like, please contact me by email at joshua @ doit . com and we can look into it

Answer 2 · 2024-01-10T09:21:22.000Z

Thanks so much, i will contact to email.