Files
backstage/plugins
Patrick Jungermann 34b772ef31 feat(splunk-on-call): use routing key instead of team name for triggered incidents
Use the routing key if it's available instead of team name when triggering incidents.

BREAKING CHANGE:
Before, the team name was used even if the routing key (with or without team) was used.
Now, the routing key defined for the component will be used instead of the team name.

Closes: #14453
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
2022-11-06 19:52:56 +01:00
..
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-11-04 14:03:11 -05:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-11-04 14:02:41 -05:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 01:29:46 +02:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-31 16:19:04 +00:00
2022-10-31 16:19:04 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-31 16:19:04 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00
2022-10-25 13:18:27 +00:00

Plugins

Backstage is a single-page application composed of a set of plugins. This folder holds numerous plugins that are managed by this repository.

For more information about the plugin ecosystem, see the documentation here:

https://backstage.io/docs/plugins/

You can also see the Plugin Marketplace for other open source plugins you can add to your Backstage instance.

Suggesting a plugin

If you start developing a plugin that you aim to release as open source, we suggest that you create a new Issue. This helps the community know what plugins are in development.

You can also use this process if you have an idea for a good plugin but you hope that someone else will pick up the work.