Hello team,
I have successfully integrated Egress on my team env using following logic:
req = api.RoomCompositeEgressRequest(
room_name=ctx.room.name,
audio_mixing=api.AudioMixing.DUAL_CHANNEL_AGENT,
audio_only=True,
webhooks=[
api.WebhookConfig(
url=webhook_url,
signing_key=live_kit_api_key,
)
],
file_outputs=[
api.EncodedFileOutput(
file_type=api.EncodedFileType.OGG,
filepath=new_file_name,
disable_manifest=True,
s3=api.S3Upload(
bucket=bucket_name,
region=region,
access_key=credentials[“AccessKeyId”],
secret=credentials[“SecretAccessKey”],
session_token=credentials[“SessionToken”],
),
)
],
)
but when i have further deployed the changes to the upper env all the settings and code logic is same but my Egress webhook is not getting triggered i have checked the configuration and everything looks fine. I am able to access my webhook URL.
May i know how can i debug this issue and check where my webhook is getting failed ?
Do you get any error when you start the egress? Can you share an egress ID EG_ I can look at the server logs for this
No i didn’t get any such error from ergress side. the recording gets successfully uploaded on the s3 bucket and egress status is completed too but the webhook attached with the Egress not triggered ever in the entire lifecycle on upper env. One of my egress ID is : EG_SDGeaJqKt9d2
I see logs that egress_started and egress_updated messages were successfully sent, I will DM you with the payload inc. URL. Note we also have this guide for managing webhooks: Best practices for managing webhook event streams | LiveKit
Will there be an issue if i will not configure the webhook on the livekit cloud but configure a webhook within the egress request itself will that still work right?
Note: I haven’t done that on development env but still receiving proper events.
If you have this working with an existing environment, I’m not sure why this wouldn’t work in your other env if all the config is the same