Raja A.

Commented on Handling Future Timestamps in Trace Data for Arize·Posted inArize AX Support

Thanks for this debugging . If there is any code that I can refer to send traces to Arize. please let me know.

Commented on Handling Future Timestamps in Trace Data for Arize·Posted inArize AX Support

if __name__ == '__main__':
    session = px.launch_app()
    LangChainInstrumentor().instrument()
    main()
    df = px.Client().get_spans_dataframe()
    df.reset_index(drop=True, inplace=True)
    if df is not None:
        print(df.head())
    else:
        print("************** NULL ")
    SPACE_KEY = "<>"
    API_KEY = "<>"

    if SPACE_KEY == "SPACE_KEY" or API_KEY == "API_KEY":
        raise ValueError("❌ NEED TO CHANGE SPACE AND/OR API_KEY")
    else:
        print("✅ Import and Setup Arize Client Done! Now we can start using Arize!")
    
    arize_client = Client(space_key=SPACE_KEY, api_key=API_KEY)
    model_id = "generative-spans-tutorial-test" #the model name in Arize
    model_version = "1.0" #(optional) the model version
    
    response = arize_client.log_spans(
        dataframe=df,
        model_id=model_id,
        model_version=model_version, #optional
    )

Commented on Handling Future Timestamps in Trace Data for Arize·Posted inArize AX Support

Raja A.

Kiko C. - I can share the piece of code that is used for sending the data to platform

Commented on Handling Future Timestamps in Trace Data for Arize·Posted inArize AX Support

Raja A.

Kiko C. and Aman K.. I am not able to see the traces. Not sure whether the timestamp is getting messed up somewhere. I am going to take a deeper look and will come back with my findings. Appreciate the response.

Commented on Handling Future Timestamps in Trace Data for Arize·Posted inArize AX Support

Raja A.

Kiko C. - Hi Kiko - Any inputs or help ? I am running the app in Ubuntu VM which is hosted in different timezone.

Commented on Handling Future Timestamps in Trace Data for Arize·Posted inArize AX Support

Raja A.

to Arize platfom

Posted in Arize AX Support·

Raja A.

Handling Future Timestamps in Trace Data for Arize

I get the below exception with trying to push trace data to the platform. Detected future timestamp in column 'end_time'. Caution when sending spans with future timestamps. Arize only stores 2 years worth of data. For example, if you sent spans to Arize from 1.5 years ago, and now send spans with timestamps of a year in the future, the oldest 0.5 years will be dropped to maintain the 2 years worth of data requirement.

13Comments

Commented on Help Needed: SSLError When Loading Span to Arize P...·Posted inPhoenix Support

Raja A.

Detected future timestamp in column 'end_time'. Caution when sending spans with future timestamps. Arize only stores 2 years worth of data. For example, if you sent spans to Arize from 1.5 years ago, and now send spans with timestamps of a year in the future, the oldest 0.5 years will be dropped to maintain the 2 years worth of data requirement.

Commented on Help Needed: SSLError When Loading Span to Arize P...·Posted inPhoenix Support

Raja A.

I do see this issue in a different server.

Commented on Help Needed: SSLError When Loading Span to Arize P...·Posted inPhoenix Support

Raja A.

I found this issue happening in certain Dev servers and not all. not sure whether its missing any certificates.