Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Databrowser buffer: No history refresh with Epics Archiver Appliance

Abierto
  • ¿Algo no está bien?
#3,922 17 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
java
Área
backend

Línea de trabajo

Start by checking how the databrowser uses org.csstudio.trends.databrowser3/automatic_history_refresh and how it transitions from the live buffer to historical data from EPICS Archiver Appliance. Reproduce the reported behavior with the settings described in the issue and compare the red plot with a newly added green plot. Done means the existing plot continues retrieving archived data instead of flatlining when older data leaves the live buffer.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Hello,

I'm researching an issue with our databrowser in combination with Epics Archiver Appliance, but until now, to no avail. Please take a look at the following screenshot. It displays twice the same plot. The red plot is running for a while, the green plot has been added a couple of moments before the screenshot has been made.

Image

As you can see, the red plot fails to retrieve data from the Archiver beyond the live buffer. At a certain point in time, the plot flatlines. As new data comes in, old data falls out. The starting point of the flatline never shifts, except when increasing or decreasing the buffer. When changing the buffer, as expected, the observable amount of live data increases or decreases aswell. The green plot, on the other hand, demonstrates that the data has been correctly archived and can, in principle, be accessed by the databrowser.

I was very glad to discover

org.csstudio.trends.databrowser3/automatic_history_refresh = true

convinced that this will solve the issue, but in fact, it did not change the behavior.

These are the settings I use:

Image

There is no firewall involved, neither on the archivers side nor on the side of Phoebus.

A look at this last screenshot confirms that the point in time where both plots start flatlining is in sync, further confirming that the issue seems to be with the transition from live buffer to historical data.

Image

I'd love to here your ideas what could be a reason for this issue and what a possible solution might look like!

Kind regards!

Lenguaje dominante
Java
Estrellas
130
Forks
132
Merge medio
2 d 11 h
PR fusionados (30 d)
19

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ControlSystemStudio/phoebus

Todos los issues de ControlSystemStudio/phoebus

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.