.stj
Templated file for your StackPack you need to perform a few steps in StackState Settings page and then edit the template file by hand.getOrCreate
functionality described a little further in this document.getOrCreate
functionality described in the Component + Relation Templates
section. Auto-generated components types will be created without an icon.component
and relation
identity extractor function. There are a few default Id Extractor Functions present in StackState. The Auto sync component id extractor
and Auto sync relation id extractor
are good starting points for your StackPack. You can go ahead and rename these, add a description if needed, and confirm the popup dialog to unlock these Id Extractor Functions from the Custom Synchronization
StackPack.Custom Synchronization
StackPack, it creates a Component Template called autosync-component-template
. Similarly, Custom Synchronization
StackPack, creates a Relation Template called autosync-relation-template
.ComponentType
from Auto-synced Component
to something that represents a generic component in your data source. The same goes for Layer
, Domain
and Environment
which defaults to Auto-synced Components
, Auto-synced Domain
,Auto-synced Environment
respectively. As this template is using the getOrCreate
functionality, these values are auto-created by StackState if they don't already exist. Find more on Templates here.update
and confirm the popup dialog to unlock this Template from the Custom Synchronization
StackPack.Custom Synchronization
StackPack, it creates a StackState DataSource called Internal kafka
. This data source is a good starting point for your StackPack. You can change the name of it, add a description if needed. You can observe the Integration Type
and Kafka Topic
are a representation of the information you supplied in the Custom Synchronization
StackPack instance details. More on Topology Sources hereupdate
and confirm the popup dialog to unlock this StackState DataSource from the Custom Synchronization
StackPack.Custom Synchronization
StackPack delivers a Synchronization called default auto synchronization
. You can find more on Synchronizations or proceed to edit this synchronization with the instructions below:Synchronization Name
and add a Description
if needed. There is no action required on Plugin
, it uses the Sts
plugin to synchronize data from the StackState Agent.Custom Synchronization
StackPack defines a default component mapping
which can be seen at the bottom of the wizard for all "Other Sources".Custom Synchronization
StackPack defines a default relation mapping
which can be seen at the bottom of the wizard for all Other Sources
.Custom Synchronizations
StackPacks.STS-EXPORT-ALL-{Date}.conf
button on the main screen. This exports all of StackState's configuration into a config file format..stj
template.stj
template file:node
objects that are owned by another StackPack. They all have a field called ownedBy
.Custom Synchronization
StackPack, will have their urn identifier
field with the following structure: urn:stackpack:autosync:{type_name}:{object_name}
.identifier
pattern that you can find across our StackPacks configuration is: urn:stackpack:{stackpack_name}:{type_name}:{object_name}
urn:stackpack:{stackpack_name}:instance:{{instanceId}}:{type_name}:{object_name}
where {{instanceId}}
is uniquely genrated for every instance of the StackPack..stj
template file.topicName
that generates a topic name for this instance based on the data provided by the user in the StackPack installation step.templateArguments
in your .stj
template file. In case of the topicName
you can replace the topic
value in the config
section of your StackState DataSource with this parameter: