Well...a product can produce multiple types of telemetry. There are also multiple versions of products that produce the same telemetry, but in different formats (string, json, xml, etc). so maybe vendor_telemetry_version_format?
05.10.2016, 11:14, "Carolyn Duby" <[email protected]>: > It would be helpful to have the function as well as we get more storm > components. For example vendor_product_parse > > On 10/5/16, 1:43 PM, "James Sirota" <[email protected]> wrote: > >> I agree. Would you like to put forth a recommendation for a naming >> convention? >> >> 05.10.2016, 10:33, "Simon Elliston Ball" <[email protected]>: >>> At present we do not have a formal convention. Many organizations will no >>> doubt want to create their own conventions to match existing naming >>> methodologies. >>> >>> However, it seems like an excellent idea to at least produce some >>> community driven recommendations for a standard baseline those without >>> strong existing methods could adopt. >>> >>> I like your vendor-product approach, but would consider adding something >>> around model / series / version to that. Does anyone have any thoughts on >>> how such a taxonomy would work best? >>> >>> Simon >>> >>>> On 5 Oct 2016, at 18:22, Vladimir Shlyakhtin >>>> <[email protected]> wrote: >>>> >>>> Hi >>>> >>>> Does Metron have any recommendation for name convention for parsers? >>>> Like vendor-product. >>>> >>>> Thanks >>>> >>>> - Vladimir >> >> ------------------- >> Thank you, >> >> James Sirota >> PPMC- Apache Metron (Incubating) >> jsirota AT apache DOT org ------------------- Thank you, James Sirota PPMC- Apache Metron (Incubating) jsirota AT apache DOT org
