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
when you deploy a custom httpjson integration it does not create any component templates, and index template for the custom dataset name. Instead it only creates one for httpjson.generic.
The same applies to TCP; UDP; custom LOG; http_endpoint and I guess to everything that can be custom.
I would expect that the dataset name is used and a custom index template is created, similar to all the other integrations.
Screen.Recording.2022-04-06.at.19.37.03.mov
The text was updated successfully, but these errors were encountered:
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!
But it does create(at least on my 8.10.3) a composable template with the custom_integration_YourCustomName@custom
see in Component Templates if that is the case
Hi,
when you deploy a custom httpjson integration it does not create any component templates, and index template for the custom dataset name. Instead it only creates one for
httpjson.generic
.The same applies to TCP; UDP; custom LOG; http_endpoint and I guess to everything that can be custom.
I would expect that the dataset name is used and a custom index template is created, similar to all the other integrations.
Screen.Recording.2022-04-06.at.19.37.03.mov
The text was updated successfully, but these errors were encountered: