Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AVR data sent via TS does not include timestamp #229

Open
ajgerace opened this issue Oct 11, 2022 · 0 comments
Open

AVR data sent via TS does not include timestamp #229

ajgerace opened this issue Oct 11, 2022 · 0 comments
Labels
bug Something isn't working untriaged Issue needs to be reviewed for validity

Comments

@ajgerace
Copy link

Environment

  • Telemetry Streaming Version: 1.31.0
  • BIG-IP Version: 15.1.6

Summary

AVR data does not include a timestamp field when data is sent via TS to an Elastic consumer.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Submit the following declaration:
{
    "class": "Telemetry",
    "controls": {
        "class": "Controls",
        "logLevel": "info"
    },
    "My_System": {
       "class": "Telemetry_System",
       "enable": false,
       "systemPoller": {
           "interval": 0
       },
       "host": "localhost",
        "port": 8100,
        "protocol": "http",
        "allowSelfSignedCert": true
    },
    "My_Listener": {
        "class": "Telemetry_Listener",
        "port": 6514
    },
    "my_elastic_consumer": {
        "class": "Telemetry_Consumer",
        "type": "ElasticSearch",
        "dataType": "_doc",    
        "host": "10.0.20.27",
        "index": "avr",
        "protocol": "http",
        "port": 9200,
        "apiVersion": "7.17.6",
        "trace": true       
    },
    "schemaVersion": "1.31.0"
}
  1. Observe the following error response:
    No error response, but you will not be able to create time series as their is no timestamp date field.
    There is a EOCTimestamp field, but that is a string field in Epoch seconds and does not automatically convert.
    example:
    "EOCTimestamp": "1665405300"

Expected Behavior

We should include a @timestamp field that is in date format so users do not need to convert/massage our data to use it.

@ajgerace ajgerace added bug Something isn't working untriaged Issue needs to be reviewed for validity labels Oct 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged Issue needs to be reviewed for validity
Projects
None yet
Development

No branches or pull requests

1 participant