Open in ChatGPTOpen in Claude

Provider Status Monitoring

Note

This feature is available for early-access customers. To request access and confirm your organization meets the feature criteria, contact your account representative or Support.

The Provider Status Monitoring page gives you a single view of the third-party services your applications depend on, such as cloud platforms, SaaS applications, developer tools, and other external providers. Rather than checking each dependency separately, you can track them all in one place.

To open the Provider Status Monitoring page, select Integrations, then Provider Status Monitoring in the navigation sidebar. The page lists providers sorted by their status. For each provider, you can see how many components are monitored, its uptime over the selected time range, and when its status was last checked. Use it to quickly determine whether a problem in your environment coincides with a known outage at one of your dependencies.

What you need

Before you start monitoring providers, make sure you have:

• These permissions:
  • INTEGRATIONS:READCONFIG to view the Provider Status Monitoring page.
  • INTEGRATIONS:DEPLOY to add, edit, or delete a provider, and to connect services to it.
  • ALERTS:READCONFIG to view the Alerts tab and a provider's Alerts section.
  • ALERTS:UPDATECONFIG to create, edit, enable, disable, or delete an alert, and to use the Alerts step when adding a provider.
• An archive configured on your storage service, to view a provider's recent incidents and maintenance periods. Learn more about configuring your Amazon S3 or connecting a Google Cloud Storage archive bucket.

Provider overview

Each provider card shows its category and tier, its uptime history, and the number of alerts watching it.

Status and severity

A provider or component might report any of the following statuses, sorted by increasing severity:

• Operational: Service is operating normally.
• Degraded: One or more monitored components report degraded performance.
• Partial outage: Service is partially unavailable.
• Major outage: Provider reports a significant outage.

A provider's status reflects the most severe status of any of its components. Similarly, a component group's status reflects the most severe status of any component it contains, and a component's status reflects the most severe status of any of its regions.

A provider or component can also report:

• Maintenance: Provider is in a scheduled maintenance window.
• No data: Coralogix does not have status information for the component yet.

Category and tier

Coralogix assigns each provider a category and a tier.

The category describes what kind of service the provider offers, such as DevOps, Security, or Cloud Infrastructure. You cannot change a provider's category, but you can use categories to filter the provider list or search for providers in a specific category.

The tier determines how often Coralogix checks the provider's status page: Tier 1 providers are checked every minute, and Tier 2 providers every five minutes. While a provider has an active incident, Coralogix checks its status every 30 seconds regardless of tier, and returns to the regular tier frequency after three consecutive checks find no active incident.

Uptime history

Each provider's Uptime history bar covers the selected time range. Select 24h, 3d, 7d, or 30d to apply that time range to the provider list and any single provider you view. The bar is segmented into blocks, each color-coded to reflect the provider's status during that period.

Block length depends on the selected time range:

Time range	Block length
24 hours	15 minutes
3 days	1 hour
7 days	1 hour
30 days	12 hours

Manage providers

You can add providers, edit existing ones, and delete providers you no longer want to monitor.

Add a provider

To add a provider:

1. In the top right corner of the page, select Add provider, then select the provider you want to monitor.

   

2. In the Select services step, select what to monitor, then select Next:

   • Region scope: Providers that report per region have a region scope that every selected component inherits. To modify the scope, select Edit regions.
   • Components: Select the components you want to monitor. Providers that organize their components into groups show them as an expandable tree.

   

3. In the Alerts (optional) step, set up alerts for the new provider. You can do one or both of the following:

   • Add to existing multi-provider alerts: Add this provider to any existing cross-provider alert.
   • Create an alert for this provider: Create a single-provider alert for this provider.
   Note

   Alerts are automatically updated to match what you monitor. When you:

   • Stop monitoring a provider's components or regions, the alerts covering them are updated to match.
   • Delete a provider, its single-provider alerts are deleted, and cross-provider alerts that include it are updated to match.

4. In the Connected services (optional) step, select the services that depend on the provider and what they depend on.

5. Select Add provider.

   The provider appears on the Provider Status Monitoring page.

   

Edit or delete a provider

Editing a provider lets you change its region scope and monitored components. To edit or delete a provider, select the more actions menu on the provider's card, then select Edit or Delete. Deleting a provider also deletes the alerts scoped to it.

When services are connected to the provider, Coralogix warns you before the change takes effect:

• When you delete the provider, its connections are kept but become inactive.
• When you stop monitoring components or regions that connected services depend on, the connections are kept but no longer cover what you removed.

View a single provider

Select any provider to view its summary, the components being monitored, and a list of recent incidents and maintenance periods.

The summary shows the following information:

• Uptime: Provider's uptime over the selected time range.
• Monitored components: Number of components being monitored.
• Reachability: Whether Coralogix can reach the provider's status page for updates. It does not reflect the provider's health. While a provider is unreachable, its components report No data.
• Last checked: When the provider's status was last checked.

The Uptime history bar reflects the selected time range, segmented into color-coded blocks.

The Components section shows the status and uptime of each monitored component, followed by the Alerts section that lists all alerts applied to the provider.

When your storage service has an archive configured, the Incidents & maintenance section lists recent incidents and maintenance periods.

Connect services to a provider

Connect the services in your Service Catalog to the providers they depend on, so you can see which of your services a provider incident affects. Each connected service shows the current status of its providers in the Providers column of the APM Services page and in the header of its APM drilldown. A service can be connected to many providers, and a provider to many services. A connection applies to the service in every environment.

By default, a connection covers all the provider's monitored components and regions, but you can scope the connection to the components and regions the service actually uses. This prevents an incident in a component or region the service doesn't use from being attributed to it.

To connect services to a provider:

1. Select the provider. In the Connected services section of its side panel, select Add services.

2. In the Services dropdown menu, select one or more services. Services already connected to the provider are marked Already connected.

3. Under Depends on, set what the services depend on. By default, all the components you monitor are selected.

   • Region scope: For providers that report per region, the regions every selected component inherits. To modify the scope, select Edit regions.
   • Components: Select the components the services depend on. Each component Follows scope by default. To set regions for a single component, expand it. A region you add is marked Added and kept, even when the region scope drops it. A region you remove is marked Removed and excluded, even when the region scope includes it.

   

4. Select Connect.

The services appear in the Connected services section with what they depend on, either All components or the components and regions you selected, and the provider's card shows the number of connected services.

You can also connect services when you add a provider.

To change a connection, select Edit next to the service, update what it depends on, then select Save. To remove a connection, select Remove and confirm.

Connections no longer monitored

A connection only covers components and regions you monitor. When you edit the provider to stop monitoring some of them, the connection is marked:

• Partly monitored: Some of the components or regions the service depends on are no longer monitored.
• Not monitored: None of the components the service depends on are monitored anymore.

To restore full coverage, either narrow the connection to the components you still monitor, or monitor the removed components again.

Alerts

An alert sends you a notification when a provider you depend on has degraded. Notifications are delivered by your Notification Center routers, so a provider outage reaches the same channels as the rest of your alerts.

Defining an alert

You can create alerts that apply for one, multiple, or all monitored providers. An alert of this type applies to each included provider in full, across all of its components and regions. To watch only part of a provider, create an alert that applies to a single provider. A provider can have multiple alerts with different scopes, statuses, and notification targets.

You can also create both types of alerts while adding a provider.

Every alert has the following:

• Name: Identifies the alert in the Alerts list and in the notifications it sends. Coralogix fills it in from the providers and status you select, and you can replace it with your own.
• Status: The status that triggers the alert. An alert triggers at the status you select or worse. An alert set to Degraded also fires on Partial outage and Major outage.
• Priority: The priority the alert carries when it fires. Each status has a default you can change: P3 for Degraded, P2 for Partial outage, and P1 for Major outage.
• Notification targets: The Team, Service, and Environment labels your Notification Center routers use to decide where the notification goes.

In the Alerts list, you can enable, disable, edit, or delete an existing alert.

Note

Editing or deleting a provider also updates the alerts scoped to it.

Create a cross-provider alert

A cross-provider alert covers one, several, or all of the providers you monitor, each across all of its components and regions. To create one:

1. Select the Alerts tab, then select Create alert.
2. Optionally, replace the Name. Coralogix fills it in from the providers and status you select.
3. Under What to alert on, select Edit providers, then select the providers to include. By default, all the providers you monitor are included.
4. Set Alert when to any or all of the included providers reaching the status.
5. Under Status, select the status that triggers the alert: Degraded, Partial outage, or Major outage. This is the minimum status: the alert also fires on any worse status.
6. Set the Priority. Each status has a default you can change: P3 for Degraded, P2 for Partial outage, and P1 for Major outage.
7. Under Who to notify, set at least one of Team, Service, or Environment. The Notification Center uses these labels to route the notification.
8. Select Create alert.

The new alert appears in the Alerts list, and is applied to every selected provider.

Create a single-provider alert

A single-provider alert covers a specific combination of regions and services within one provider. To create one:

1. Select the provider, then select Create alert in the Alerts section of its side panel.
2. Optionally, replace the Name. Coralogix fills it in from the provider and status you select.
3. Under What to alert on, set the scope of the alert:
   • Region scope: Regions the alert applies to. Select Edit regions to edit, add, or remove regions. By default, all regions are included.
   • Services: Services the alert applies to. You can add or remove services. By default, all monitored services are included.
4. Set Alert when to any or all of the selected services reaching the status.
5. Under Status, select the status that triggers the alert: Degraded, Partial outage, or Major outage. This is the minimum status: the alert also fires on any worse status.
6. Set the alert Priority.
7. Under Who to notify, set at least one of Team, Service, or Environment. The Notification Center uses these labels to route the notification.
8. Select Create alert.

The new alert appears in the provider's Alerts list, alongside any cross-provider alerts that include it.

Edit, disable, or delete an alert

The Alerts tab lists every alert with the status it triggers at, its priority, and the labels it routes on. Filter the list by provider, or select Enabled only to hide alerts that are turned off.

To manage alerts:

• Use the Enabled toggle to stop an alert from firing without deleting it.
• Select Edit to modify an alert.
• Select Delete and confirm to delete an alert.

Limitations

• Availability history starts when you add the provider. Status updates that occurred before you added the provider are not reported.
• Connections are made by service name. Renaming a service does not carry its connections over, so connect the service again under its current name.
• Editing which components you monitor takes effect immediately, but past uptime is not recalculated. The Uptime history bar keeps the segments already recorded and reflects the new configuration from the moment you save. It does not indicate where the change occurred.