Configuring events and alerts
The OpsCenter Event Log page in the Activities section displays a continuously updated list of events and alerts.
The OpsCenter Event Log page in the Activities section displays a
continuously updated list of events and alerts. The following list reflects the most detailed
logging level available for Cassandra, DataStax Enterprise, and OpsCenter events:
DEBUG(0)INFO(1)WARN(2)ERROR(3)CRITICAL(4)ALERT(5)
Alerts
Optionally, you can configure OpsCenter to send alerts for selected levels of events. These alerts can be provided remotely by email, or through HTTP to a selected URL. Alerts are disabled by default.
Alerts are triggered only by events from the OpsCenter API or UI. For example, a nodetool move operation submitted from the command line does not trigger an alert. However, a move operation launched using controls in the OpsCenter does trigger an alert.
All alerts contain the following information about each event captured:
| Field | Description | Example |
|---|---|---|
api_source_ip |
IP that originally sent the request. | 67.169.50.240 |
target_node |
Destination of a STREAMING action. | 10.1.1.11 |
event_source |
Component that caused the event. | OpsCenter (i.e., restart, start) |
user |
OpsCenter user that caused the event. | opscenter_user |
time |
Normal timestamp for the event. | 1311025650414527 |
action |
Type of event (see Event action types) | 20 |
subject |
Customizable subject line of the email alert. | [WARN] OpsCenter Event - Node reported as being down: 127.0.0.1 |
message |
Description of the event. | Garbage Collecting node 10.1.1.13 |
level |
Numerical code for the log level. | 1 |
source_node |
Node where the event originated. | 10.1.1.13 |
level_str |
Logging level of the event. | INFO |