Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions content/metadata-stats/metadata/subscribe.textile
Original file line number Diff line number Diff line change
Expand Up @@ -109,11 +109,16 @@ channel.Subscribe(context.Background(), "channel.closed", func(msg *ably.Message

h2(#log). Log events

The @[meta]log@ and @[meta]log:push@ metachannels publish events that aren't otherwise available to clients. For example, if Ably receives an error response when delivering a webhook to your endpoint, Ably sends an event to @[meta]log@ with information about the error.
The @[meta]log@ and "@[meta]log:push@":/push#Error metachannels publish events that aren't otherwise available to clients.

Errors where the client can be directly notified are **not** published to the metachannels. For example, if a client attempts to publish a message but exceeds a channel rate limit, the client will be notified by an error callback passed to the "publish()":/api/realtime-sdk/channels#publish method.

@[meta]log@ publishes errors related to all resources other than Push Notifications, which are published to @[meta]log:push@.
The following example subscribes to the @[meta]log@ channel:

```[javascript]
const channel = realtime.channels.get('[meta]log');
channel.subscribe(msg => console.log(msg));
```

h2(#stats). App statistics events

Expand Down
2 changes: 1 addition & 1 deletion content/push/configure/device.textile
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Configure and activate devices
meta_description: "Learn how to set up and manage device activations for push notifications with Ably, including platform installation, device registration, and handling lifecycle events."
meta_keywords: "Push, push notifications, Apple push notification service, Google firebase cloud messaging service, Web Push, activate, subscribe"
meta_keywords: "Push, push notifications, Apple push notification service, Google firebase cloud messaging service, activate, subscribe"
languages:
- kotlin
- java
Expand Down
14 changes: 13 additions & 1 deletion content/push/index.textile
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Push notifications
meta_description: "Ably delivers push notifications to user devices."
meta_description: "Ably delivers push notifications to user devices or browsers."
meta_keywords: "Push, push notifications, Apple push notification service, Google Firebase cloud messaging service, APNs, FCM, Web Push"
redirect_from:
- /general/push
Expand Down Expand Up @@ -79,3 +79,15 @@ Each push target device or browser is associated with a unique @deviceId@ and au
* By employing a standard "Ably key":/auth/basic or "Token":/auth/token, with a @deviceIdentityToken@, a credential generated during registration to assert the device's or browser's identity, included in the request header.

The service credential management is handled by the "Ably SDK":https://ably.com/docs/sdks, removing the need for the client application to manage device credentials unless accessing the "push admin API":/api/realtime-sdk/push-admin directly via HTTP.


h4(#Error). Error handling

Metachannels, such as @[meta]log:push@, publish events and errors that aren't otherwise available to clients. It's important to note that client-returned errors will not be published to this channel.

The following example subscribes to the @[meta]log:push@ channel:

```[javascript]
const channel = realtime.channels.get('[meta]log:push');
channel.subscribe(msg => console.log(msg));
```