This topic describes how to publish (Notifications and Monitoring services) An alert published to all subscriptions in the specified topic. Each message is delivered at least once per subscription. directly using the Notifications service. You can manually enter the message content or allow a service or app to programmatically define the message content.
Each message is broadcast to all (Notifications service) An endpoint for a topic; typically a URL or email address. Published messages are sent to each subscription for a topic. in the specified (Notifications service) A communication channel for sending messages to the subscriptions in the topic.. Every message sent out as email contains a link to unsubscribe from the related topic.
Message delivery rate limits per endpoint: 60 messages per minute for HTTP-based protocols. (HTTP-based protocols use URL endpoints that begin with "http:" or "https:".) 10 messages per minute for Email protocol.
Warning
Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Oracle Cloud Infrastructure Console, API, or CLI.
You can create automation based on state changes for your Oracle Cloud Infrastructure resources by using event types, rules, and actions. For more information, see Overview of Events.
In the Publish Message dialog box, fill in the fields:
Title: Enter the title you want to send.
Protocol | Rendering of the title |
---|---|
Subject line of the email message. | |
HTTPS (Custom URL) | Not rendered. |
PagerDuty | Title field of the published message. |
Slack | Not rendered. |
Message: Enter the content you want to send.
Note
Message size limit per request: 64KB.
For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.
Use these API operations to publish messages:
About Oracle | Contact Us | Legal Notices | Terms of Use | Privacy | Document Conventions |
Copyright © , Oracle and/or its affiliates. All rights reserved.