Monitor actions

Documentation Index

Fetch the complete documentation index at: https://docs.chronosphere.io/llms.txt

Use this file to discover all available pages before exploring further.

When viewing all monitors, you can select an individual monitor to view its details and take actions for that monitor. Chronosphere Observability Platform populates these monitor pages with information necessary to understand, investigate, and control a monitor’s alerts. For a description of what the monitor detail page displays, including query results, alert history, and change events, see Monitor details. To create a monitor, see Create a monitor on the monitors overview.

​

Mute a monitor

If a monitor has any active muting rules, Observability Platform reports the number of active muting rules and when they expire in a banner. The banner displays even if there aren’t active alerts. The monitor’s Status also reports as Muted if all alerts are muted, and its Alert analysis summary breaks down the muting or severity for all of the monitor’s alerts. To mute the selected monitor, a signal from that monitor, or any stored time series, click Mute monitor to add a muting rule. If a muting rule already exists, the button is named Add muting rule. When you create a muting rule from a monitor, Observability Platform prepopulates the muting rule’s Name field with the monitor’s name. For more information about creating and editing muting rules, see Muting rules.

​

Edit a monitor

To edit a monitor, click Edit to open the Edit monitor drawer, or use Chronoctl or Terraform to make your changes.

​

Send a test notification

A test notification sends synthetic alert traffic for the selected monitor through the same notification path as a real alert, so you can confirm that notifiers and notification templates behave as expected. The monitor must have a notification policy assigned. If the monitor has no policy, Observability Platform returns an error when you run the test. Test notifications respect the same routing rules as production alerts for the selected monitor and severity. They don’t change the monitor’s status on the graph and aren’t a substitute for validating query thresholds. To send a test notification from a monitor’s details page:

1. In the navigation menu, select Alerting > Monitors, and then open the monitor you want to test.
2. Click Test notifications.
3. Under Select severity level for testing, choose Critical or Warning to match the severity you want to exercise in the notification policy.
4. Click Run test.

If the request succeeds, Observability Platform shows a confirmation message. Check the configured destinations, for example, email inboxes or chat channels, to verify delivery and formatting. Observability Platform rate-limits test notifications. When a limit applies before a request is sent, Run test is disabled in the drawer. Hold the pointer over Run test to see how long to wait. When the server rejects a run for rate limiting, Observability Platform shows a persistent error notification that states the limit and tells you to try again later. Users who have read-only access to Observability Platform can’t run test notifications. The Run test action is unavailable for read-only users.

​

View additional actions

​

Add a comment

To comment on a monitor:

1. On the monitor’s page, click Add comment. If Add comment isn’t visible, click the three vertical dots icon, and then click Add comment.
2. Follow the instructions to add a comment.

​

Explore the query

To open the monitor query in Metrics Explorer, click Open in explorer on the query results chart. If Open in explorer isn’t visible, click the three vertical dots icon on the chart, and then click Open in explorer. For more information, see Query results.

​

Create a custom event

Create a custom change event and associate it with a monitor directly from the monitor’s page:

1. On the monitor’s page, click Create event. If Create event isn’t visible, click the three vertical dots icon, and then click Create event.
2. Follow the instructions to create a change event.

​

View version history

To view the history of changes for a monitor, click Version history. If Version history isn’t visible, click the three vertical dots icon, and then click Version history. Click Version history to display a panel with two tabs:

• Code config: Displays a code representation of the selected entity as of the time of the selected revision.
• Code diff: Displays a Git-style diff of the most-recent change made to the entity, in Chronosphere API format. To compare the selected revision to another revision in the history, click the Compare With dropdown and select the timestamp of the revision that you want to compare.
  • Click Unified to see the diff stacked horizontally.
  • Click Split to see changes side by side.

You can see the user, service account, or actor which made and the method used for the last change at the top of the list of changes. To view a revision in the history, click any entry in the list of timestamped revisions. The timestamps default to your local timezone. You can view unchanged lines within the diff by clicking the Expand X lines links. For a natural language description of the differences between versions, click Explain what has changed. An information box appears with a summary of the changes. This summary can help users who are less familiar with code updates understand changes. Use the thumbs up or thumbs down icon to indicate whether the explanation was helpful or not.

​

Connect monitors to services or collections

Services and collections can own monitors, but you can also connect a monitor to any service or collection. Manage connections opens a panel where you can manage connections between the selected monitor and any service or collection.

1. On the monitor’s page, click Manage connections. If Manage connections isn’t visible, click the three vertical dots icon, and then click Manage connections.
2. Add or remove a connection.