Forum Discussion
Heartbeat Action Query Not Sent to Source
- 1 month ago
Hello lyancy ,
I'm not able to test this myself, unfortunately.
Just to be sure that this is not a misconfiguration or a glitch in the background, recreating the same logic in a new eventstream is recommended.
If this does not help, and because the configuration discussed is quite generic, creating a ticket for support from Microsoft would be the next step.
Hello lyancy
welcome to this Fabric community forum.
You want to enter the heartbeat query for this PostgreSQL connection:
This query depends on a table in the source database, as you mentioned already.
The documentation does not provide a real sample:
I have no hands-on experience with this database, but I did some research that could help you out.
It seems your solution should work because it looks a lot like this idempotent call:
CREATE TABLE public.test_heartbeat_table (
id integer primary key,
last_seen timestamptz not null
);
INSERT INTO public.test_heartbeat_table (id, last_seen)
VALUES (1, now());
[idempotent call]
UPDATE public.test_heartbeat_table
SET last_seen = now()
WHERE id = 1;
A simplified alternative table and call could look like:
CREATE TABLE public.test_heartbeat_table (
id bigserial primary key,
text text not null,
created_at timestamptz not null default now()
);
INSERT INTO public.test_heartbeat_table (text)
VALUES ('test_heartbeat');
I found this post, which could be linked. There, a more elaborate solution is proposed:
INSERT INTO my_schema.fabric_heartbeat (id, heartbeat_ts)
VALUES (1, NOW())
ON CONFLICT(id)
DO UPDATE SET heartbeat_ts = EXCLUDED.heartbeat_ts;
These are three possible solutions that could hopefully point you in the right direction.
Please let us know which actually works for you.
---
If this answer helps you, marking it as the accepted answer is appreciated. All community members with similar questions will benefit by doing so. Your contribution is highly appreciated.
Hi svelde,
Thank you for the solution options you shared.
I tested for the other two heartbeat query and the issue is still the same. The Eventstream has been active for about 5 hours and nothing has been sent to the heartbeat table. Is there maybe a configuration regarding the heartbeat interval?