You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the discussion of PR #1191, we brought up to support custom stream name for firehose. Currently, the stream name of firehose for data is autogenerated based on prefix (defined in conf/global.json), and schema name (defined in conf/schemas/*.json or conf/logs.json). In some rare cases the firehose needs to be recreated if the stream name is changed (e.g. rename the schema). With custom stream name support, users can keep the existing firehose without recreate a new one.
We plan to add a new optional field in the configuration field in the log schema. For example,
Background
In the discussion of PR #1191, we brought up to support custom stream name for firehose. Currently, the stream name of firehose for
data
is autogenerated based on prefix (defined inconf/global.json
), and schema name (defined inconf/schemas/*.json
orconf/logs.json
). In some rare cases the firehose needs to be recreated if the stream name is changed (e.g. rename the schema). With custom stream name support, users can keep the existing firehose without recreate a new one.We plan to add a new optional field in the
configuration
field in the log schema. For example,Desired Change
Support custom stream name for firehose both for
alerts
anddata
.The text was updated successfully, but these errors were encountered: