Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #5579: send heartbeat reports if in heartbeat mode #534

Closed

Conversation

ncharles
Copy link
Member

@ncharles ncharles commented Oct 9, 2014

No description provided.

@jooooooon
Copy link
Member

The must_send_heartbeat never seems to be defined, except when reports are sent (ie, the changes reporting is ok, but not heartbeat only). Could you revisit this please, @ncharles ?

vars:
changes_only.send_reports::
"dummy_string" string => "dummy_content",
classes => always("must_send_heartbeat");
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

must_send_heartbeat is defined here

@ncharles
Copy link
Member Author

ha, indeed, part of the PR seems to be missing ..


!full_compliance.heartbeat_enabled.(must_send_heartbeat|!start_report_sent)::
"@@Common@@log_info@@&TRACKINGKEY&@@common@@StartRun@@${g.execRun}##${g.uuid}@#Start execution with config [&RUDDER_NODE_CONFIG_ID&]"
classes => rudder_always_classes_persist("start_report_sent", "${g.heartbeat_interval}");
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually, heartbeat are correctly sent thanks to the persist here

@ncharles
Copy link
Member Author

Replaced by #563

@ncharles ncharles closed this Nov 25, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants