This feature is currently only available through the Beta program and is not released for general availability. To request access to the Beta program, contact [email protected].
BigPanda takes the raw data from your systems and normalizes it into key-value pairs, called tags. Each tag has two parts: the tag name and the tag value. Tags are the fundamental data model for your alerts and incidents and provide vital incident enrichment.
In BigPanda, tags enable alert correlation, provide incident information in the UI, and help you configure environments, perform searches, and collect analytics.
Incident tags are key-value pairs that allow you to quickly see summary information for a particular incident rather than needing to review all of the related alerts.
Roles with the following permissions can access Incident Tags:
Full access - View, add, edit or remove the incident tag from incidents.
Read-only - View incident tags on incidents in some or all environments.
Read-only - View the Incident Tags section of the BigPanda Settings.
Full access - View, create and edit incident tags in the Incident Tags section of the BigPanda Settings.
To learn more about how BigPanda's permissions work, see the RBAC - Role Based Access Control documentation.
Incident tags will appear on both the Incident Feed and in the Overview tab of the Incident Details pane.
Incident tags add key enrichment to your BigPanda incidents, helping you see key information about the event.
You are able to create, edit, or inactivate incident tags to fit the needs of your organization. To learn more about configuring incident tags, please see the Managing Incident Tags documentation.
Incident tags may also be configured to automatically add to specific incidents based on incident or alert criteria. To learn more about configuring automatic tags, please see the Automatic Incident Tags documentation.
If an incident has been manually split, the new incident will be created without any incident tag values. If incidents are manually merged, only the incident tags from the destination incident will appear on the merged incident. Source incident tags will not be added to the destination incident.
Incident tags may take the form of Priority, Text, or Multi-value tags.
Priority tags create a sortable hierarchy to mark in which order incidents should be addressed. Priority tags make it easier to view the importance and urgency of your incidents at a glance.
By default, your environment will have Priority tags enabled, with pre-configured settings. These settings can be customized to better fit the needs of your organization. To learn more about customizing tags, please see the Managing Incident Tags documentation.
Priority tags are visible at the top left of incidents in both the feed and the details Overview tab, next to the incident severity. Incidents that have not been prioritized will not show the priority icon.
Priority can be assigned from the incident feed or from the Overview tab of the incident details pane. To learn more about using priority tags, please see the Prioritizing Incidents documentation
Text and Multi-value tags add data sets with additional information, details, or other enrichment to your incidents. Each tag is made up of a customized value pair similar to BigPanda alert tags.
Text and Multi-value tags appear at the top of the Overview tab of the incident details pane.
Each tag is made up of the name of the tag, and the tag value (e.g. Source_system: Nagios). For text tag types, the value is a single text string that appears in an editable text box. For multi-value tag types, the value is one or more individual text tags. These appear as individual items in the editable value field.
Configure text and multi-value tags such as “affected environment” or “region” to add context and enable better collaboration between your organization's teams.
Once configured, text and multi-value tags can be assigned to incidents from the Overview tab of the incident details pane. To learn more about using text and multi-value tags, please see the Adding Incident Tags documentation.
Updated 10 days ago