Stackdriver Logging doesn't recognize time field in JSON logInstalling StackDriver Logging agent on cos imageUse a wild card in StackDriver LoggingSpecifying resource in Stackdriver loggingGoogle Stackdriver Policy Alert Time PeriodKubernetes Nginx Ingress Controllers log to StackdriverStackdriver logs stopped appearing in GCP Stackdriver Logging Console

How was Apollo supposed to rendezvous in the case of a lunar abort?

Creating Fictional Slavic Place Names

Are academic associations obliged to comply with the US government?

Why use water tanks from a retired Space Shuttle?

Is the capacitor drawn or wired wrongly?

Humans meet a distant alien species. How do they standardize? - Units of Measure

What does War Machine's "Canopy! Canopy!" line mean in "Avengers: Endgame"?

How can a single Member of the House block a Congressional bill?

What does the behaviour of water on the skin of an aircraft in flight tell us?

What are the problems in teaching guitar via Skype?

Should this code fail to compile in C++17?

Do adult Russians normally hand-write Cyrillic as cursive or as block letters?

what's the equivalent of helper in LWC?

Can you please explain this joke: "I'm going bananas is what I tell my bananas before I leave the house"?

Applicants clearly not having the skills they advertise

Coding Challenge Solution - Good Range

Working in the USA for living expenses only; allowed on VWP?

Why don't I have ground wiring on any of my outlets?

Is there any Biblical Basis for 400 years of silence between Old and New Testament?

Estimate related to the Möbius function

California: "For quality assurance, this phone call is being recorded"

How do I get a cleat that's stuck in a pedal, detached from the shoe, out?

Recording the inputs of a command and producing a list of them later on

How can I grammatically understand "Wir über uns"?



Stackdriver Logging doesn't recognize time field in JSON log


Installing StackDriver Logging agent on cos imageUse a wild card in StackDriver LoggingSpecifying resource in Stackdriver loggingGoogle Stackdriver Policy Alert Time PeriodKubernetes Nginx Ingress Controllers log to StackdriverStackdriver logs stopped appearing in GCP Stackdriver Logging Console






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















I'm using Google Kubernetes Engine (GKE) in conjunction with Stackdriver Logging.



The Stackdriver's documentation says there are some special fields used by Logging agent to set fields in the LogEntry object.



As regard to severity field, it works fine. However, time field doesn't work as intended.



The following JSON is a MySQL error log, which was modified and redirected to stdout:



(beautified and annotated for clarity)




"prio": 0,
"err_code": 11323,
"component": "mysqlx",
"source_line": 154,
"source_file": "socket_acceptors_task.cc",
"function": "show_startup_log",
"msg": "X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060",
"err_symbol": "ER_XPLUGIN_LISTENER_STATUS_MSG",
"SQL_state": "HY000",
"subsystem": "Server",
"label": "System",

// Added for Stackdriver Logging
"severity": "INFO",
"time": "1548054692.636",

// This is the same time written in human-readable format.
"time.readable": "2019-01-21T07:11:32.636761Z"



And the following is the corresponding log recorded by Stackdriver Logging:



(beautified and annotated for clarity)




"insertId": "1jibhqgfw4kum0",
"jsonPayload":
// Both `severity` and `time` fields were removed.

"msg": "X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060",
"label": "System",
"prio": 0,
"err_code": 11323,
"time.readable": "2019-01-21T07:11:32.636761Z",
"subsystem": "Server",
"source_file": "socket_acceptors_task.cc",
"err_symbol": "ER_XPLUGIN_LISTENER_STATUS_MSG",
"function": "show_startup_log",
"SQL_state": "HY000",
"source_line": 154,
"component": "mysqlx"
,
"resource":
"type": "container",
"labels":
"namespace_id": "myproject",
"instance_id": "506697609301173766",
"zone": "asia-east1-b",
"pod_id": "demo-demoid1234567890-sns7g",
"project_id": "harai-development",
"cluster_name": "myproject",
"container_name": "mysql-errorlog-output"

,

// `timestamp` doesn't reflect the value in the original log,
// which is "2019-01-21T07:11:32.636761Z".
"timestamp": "2019-01-21T07:11:44Z",

// `severity` reflects the value in the original log
"severity": "INFO",

"labels":
"compute.googleapis.com/resource_name": "fluentd-gcp-v3.1.0-pwc9k",
"container.googleapis.com/pod_name": "demo-demoid1234567890-sns7g",
"container.googleapis.com/stream": "stdout",
"container.googleapis.com/namespace_name": "myproject"
,
"logName": "projects/harai-development/logs/mysql-errorlog-output",
"receiveTimestamp": "2019-01-21T07:11:49.560205566Z"



Although the both time and severity fields were removed, timestamp field in LogEntry doesn't reflect the time specified in the original time field.



How can I set timestamp to the time the log is created?










share|improve this question






















  • To verify that you are using structured logging (single line) as per 1 2, you may change the severity to something other than info, like “DEBUG”, would it reflect in the logs ?

    – Fady
    Jan 24 at 0:46











  • @Fady With respect to severity, it definitely reflects the value in the logs.

    – Akihiro HARAI
    Jan 24 at 3:03











  • So I assume you have tried a different severity like “debug” and it did show, correct ?

    – Fady
    Jan 24 at 3:36











  • @Fady Yes, I have output several log messages with different severities, and confirmed they were properly recognized by the agent.

    – Akihiro HARAI
    Jan 24 at 5:26






  • 1





    At this point I suggest opening an issuetracker report as to be investigated by the Stackdriver team. Include simple reproduction steps (e.g how did you configure structured logging) as to help the team with their investigation.

    – Fady
    Jan 24 at 5:42

















0















I'm using Google Kubernetes Engine (GKE) in conjunction with Stackdriver Logging.



The Stackdriver's documentation says there are some special fields used by Logging agent to set fields in the LogEntry object.



As regard to severity field, it works fine. However, time field doesn't work as intended.



The following JSON is a MySQL error log, which was modified and redirected to stdout:



(beautified and annotated for clarity)




"prio": 0,
"err_code": 11323,
"component": "mysqlx",
"source_line": 154,
"source_file": "socket_acceptors_task.cc",
"function": "show_startup_log",
"msg": "X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060",
"err_symbol": "ER_XPLUGIN_LISTENER_STATUS_MSG",
"SQL_state": "HY000",
"subsystem": "Server",
"label": "System",

// Added for Stackdriver Logging
"severity": "INFO",
"time": "1548054692.636",

// This is the same time written in human-readable format.
"time.readable": "2019-01-21T07:11:32.636761Z"



And the following is the corresponding log recorded by Stackdriver Logging:



(beautified and annotated for clarity)




"insertId": "1jibhqgfw4kum0",
"jsonPayload":
// Both `severity` and `time` fields were removed.

"msg": "X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060",
"label": "System",
"prio": 0,
"err_code": 11323,
"time.readable": "2019-01-21T07:11:32.636761Z",
"subsystem": "Server",
"source_file": "socket_acceptors_task.cc",
"err_symbol": "ER_XPLUGIN_LISTENER_STATUS_MSG",
"function": "show_startup_log",
"SQL_state": "HY000",
"source_line": 154,
"component": "mysqlx"
,
"resource":
"type": "container",
"labels":
"namespace_id": "myproject",
"instance_id": "506697609301173766",
"zone": "asia-east1-b",
"pod_id": "demo-demoid1234567890-sns7g",
"project_id": "harai-development",
"cluster_name": "myproject",
"container_name": "mysql-errorlog-output"

,

// `timestamp` doesn't reflect the value in the original log,
// which is "2019-01-21T07:11:32.636761Z".
"timestamp": "2019-01-21T07:11:44Z",

// `severity` reflects the value in the original log
"severity": "INFO",

"labels":
"compute.googleapis.com/resource_name": "fluentd-gcp-v3.1.0-pwc9k",
"container.googleapis.com/pod_name": "demo-demoid1234567890-sns7g",
"container.googleapis.com/stream": "stdout",
"container.googleapis.com/namespace_name": "myproject"
,
"logName": "projects/harai-development/logs/mysql-errorlog-output",
"receiveTimestamp": "2019-01-21T07:11:49.560205566Z"



Although the both time and severity fields were removed, timestamp field in LogEntry doesn't reflect the time specified in the original time field.



How can I set timestamp to the time the log is created?










share|improve this question






















  • To verify that you are using structured logging (single line) as per 1 2, you may change the severity to something other than info, like “DEBUG”, would it reflect in the logs ?

    – Fady
    Jan 24 at 0:46











  • @Fady With respect to severity, it definitely reflects the value in the logs.

    – Akihiro HARAI
    Jan 24 at 3:03











  • So I assume you have tried a different severity like “debug” and it did show, correct ?

    – Fady
    Jan 24 at 3:36











  • @Fady Yes, I have output several log messages with different severities, and confirmed they were properly recognized by the agent.

    – Akihiro HARAI
    Jan 24 at 5:26






  • 1





    At this point I suggest opening an issuetracker report as to be investigated by the Stackdriver team. Include simple reproduction steps (e.g how did you configure structured logging) as to help the team with their investigation.

    – Fady
    Jan 24 at 5:42













0












0








0








I'm using Google Kubernetes Engine (GKE) in conjunction with Stackdriver Logging.



The Stackdriver's documentation says there are some special fields used by Logging agent to set fields in the LogEntry object.



As regard to severity field, it works fine. However, time field doesn't work as intended.



The following JSON is a MySQL error log, which was modified and redirected to stdout:



(beautified and annotated for clarity)




"prio": 0,
"err_code": 11323,
"component": "mysqlx",
"source_line": 154,
"source_file": "socket_acceptors_task.cc",
"function": "show_startup_log",
"msg": "X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060",
"err_symbol": "ER_XPLUGIN_LISTENER_STATUS_MSG",
"SQL_state": "HY000",
"subsystem": "Server",
"label": "System",

// Added for Stackdriver Logging
"severity": "INFO",
"time": "1548054692.636",

// This is the same time written in human-readable format.
"time.readable": "2019-01-21T07:11:32.636761Z"



And the following is the corresponding log recorded by Stackdriver Logging:



(beautified and annotated for clarity)




"insertId": "1jibhqgfw4kum0",
"jsonPayload":
// Both `severity` and `time` fields were removed.

"msg": "X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060",
"label": "System",
"prio": 0,
"err_code": 11323,
"time.readable": "2019-01-21T07:11:32.636761Z",
"subsystem": "Server",
"source_file": "socket_acceptors_task.cc",
"err_symbol": "ER_XPLUGIN_LISTENER_STATUS_MSG",
"function": "show_startup_log",
"SQL_state": "HY000",
"source_line": 154,
"component": "mysqlx"
,
"resource":
"type": "container",
"labels":
"namespace_id": "myproject",
"instance_id": "506697609301173766",
"zone": "asia-east1-b",
"pod_id": "demo-demoid1234567890-sns7g",
"project_id": "harai-development",
"cluster_name": "myproject",
"container_name": "mysql-errorlog-output"

,

// `timestamp` doesn't reflect the value in the original log,
// which is "2019-01-21T07:11:32.636761Z".
"timestamp": "2019-01-21T07:11:44Z",

// `severity` reflects the value in the original log
"severity": "INFO",

"labels":
"compute.googleapis.com/resource_name": "fluentd-gcp-v3.1.0-pwc9k",
"container.googleapis.com/pod_name": "demo-demoid1234567890-sns7g",
"container.googleapis.com/stream": "stdout",
"container.googleapis.com/namespace_name": "myproject"
,
"logName": "projects/harai-development/logs/mysql-errorlog-output",
"receiveTimestamp": "2019-01-21T07:11:49.560205566Z"



Although the both time and severity fields were removed, timestamp field in LogEntry doesn't reflect the time specified in the original time field.



How can I set timestamp to the time the log is created?










share|improve this question














I'm using Google Kubernetes Engine (GKE) in conjunction with Stackdriver Logging.



The Stackdriver's documentation says there are some special fields used by Logging agent to set fields in the LogEntry object.



As regard to severity field, it works fine. However, time field doesn't work as intended.



The following JSON is a MySQL error log, which was modified and redirected to stdout:



(beautified and annotated for clarity)




"prio": 0,
"err_code": 11323,
"component": "mysqlx",
"source_line": 154,
"source_file": "socket_acceptors_task.cc",
"function": "show_startup_log",
"msg": "X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060",
"err_symbol": "ER_XPLUGIN_LISTENER_STATUS_MSG",
"SQL_state": "HY000",
"subsystem": "Server",
"label": "System",

// Added for Stackdriver Logging
"severity": "INFO",
"time": "1548054692.636",

// This is the same time written in human-readable format.
"time.readable": "2019-01-21T07:11:32.636761Z"



And the following is the corresponding log recorded by Stackdriver Logging:



(beautified and annotated for clarity)




"insertId": "1jibhqgfw4kum0",
"jsonPayload":
// Both `severity` and `time` fields were removed.

"msg": "X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060",
"label": "System",
"prio": 0,
"err_code": 11323,
"time.readable": "2019-01-21T07:11:32.636761Z",
"subsystem": "Server",
"source_file": "socket_acceptors_task.cc",
"err_symbol": "ER_XPLUGIN_LISTENER_STATUS_MSG",
"function": "show_startup_log",
"SQL_state": "HY000",
"source_line": 154,
"component": "mysqlx"
,
"resource":
"type": "container",
"labels":
"namespace_id": "myproject",
"instance_id": "506697609301173766",
"zone": "asia-east1-b",
"pod_id": "demo-demoid1234567890-sns7g",
"project_id": "harai-development",
"cluster_name": "myproject",
"container_name": "mysql-errorlog-output"

,

// `timestamp` doesn't reflect the value in the original log,
// which is "2019-01-21T07:11:32.636761Z".
"timestamp": "2019-01-21T07:11:44Z",

// `severity` reflects the value in the original log
"severity": "INFO",

"labels":
"compute.googleapis.com/resource_name": "fluentd-gcp-v3.1.0-pwc9k",
"container.googleapis.com/pod_name": "demo-demoid1234567890-sns7g",
"container.googleapis.com/stream": "stdout",
"container.googleapis.com/namespace_name": "myproject"
,
"logName": "projects/harai-development/logs/mysql-errorlog-output",
"receiveTimestamp": "2019-01-21T07:11:49.560205566Z"



Although the both time and severity fields were removed, timestamp field in LogEntry doesn't reflect the time specified in the original time field.



How can I set timestamp to the time the log is created?







google-kubernetes-engine google-stackdriver






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 21 at 8:27









Akihiro HARAIAkihiro HARAI

1305




1305












  • To verify that you are using structured logging (single line) as per 1 2, you may change the severity to something other than info, like “DEBUG”, would it reflect in the logs ?

    – Fady
    Jan 24 at 0:46











  • @Fady With respect to severity, it definitely reflects the value in the logs.

    – Akihiro HARAI
    Jan 24 at 3:03











  • So I assume you have tried a different severity like “debug” and it did show, correct ?

    – Fady
    Jan 24 at 3:36











  • @Fady Yes, I have output several log messages with different severities, and confirmed they were properly recognized by the agent.

    – Akihiro HARAI
    Jan 24 at 5:26






  • 1





    At this point I suggest opening an issuetracker report as to be investigated by the Stackdriver team. Include simple reproduction steps (e.g how did you configure structured logging) as to help the team with their investigation.

    – Fady
    Jan 24 at 5:42

















  • To verify that you are using structured logging (single line) as per 1 2, you may change the severity to something other than info, like “DEBUG”, would it reflect in the logs ?

    – Fady
    Jan 24 at 0:46











  • @Fady With respect to severity, it definitely reflects the value in the logs.

    – Akihiro HARAI
    Jan 24 at 3:03











  • So I assume you have tried a different severity like “debug” and it did show, correct ?

    – Fady
    Jan 24 at 3:36











  • @Fady Yes, I have output several log messages with different severities, and confirmed they were properly recognized by the agent.

    – Akihiro HARAI
    Jan 24 at 5:26






  • 1





    At this point I suggest opening an issuetracker report as to be investigated by the Stackdriver team. Include simple reproduction steps (e.g how did you configure structured logging) as to help the team with their investigation.

    – Fady
    Jan 24 at 5:42
















To verify that you are using structured logging (single line) as per 1 2, you may change the severity to something other than info, like “DEBUG”, would it reflect in the logs ?

– Fady
Jan 24 at 0:46





To verify that you are using structured logging (single line) as per 1 2, you may change the severity to something other than info, like “DEBUG”, would it reflect in the logs ?

– Fady
Jan 24 at 0:46













@Fady With respect to severity, it definitely reflects the value in the logs.

– Akihiro HARAI
Jan 24 at 3:03





@Fady With respect to severity, it definitely reflects the value in the logs.

– Akihiro HARAI
Jan 24 at 3:03













So I assume you have tried a different severity like “debug” and it did show, correct ?

– Fady
Jan 24 at 3:36





So I assume you have tried a different severity like “debug” and it did show, correct ?

– Fady
Jan 24 at 3:36













@Fady Yes, I have output several log messages with different severities, and confirmed they were properly recognized by the agent.

– Akihiro HARAI
Jan 24 at 5:26





@Fady Yes, I have output several log messages with different severities, and confirmed they were properly recognized by the agent.

– Akihiro HARAI
Jan 24 at 5:26




1




1





At this point I suggest opening an issuetracker report as to be investigated by the Stackdriver team. Include simple reproduction steps (e.g how did you configure structured logging) as to help the team with their investigation.

– Fady
Jan 24 at 5:42





At this point I suggest opening an issuetracker report as to be investigated by the Stackdriver team. Include simple reproduction steps (e.g how did you configure structured logging) as to help the team with their investigation.

– Fady
Jan 24 at 5:42










1 Answer
1






active

oldest

votes


















0














In the Fluentd configuration for GKE cluster, the time format is defined like this:



time_format %Y-%m-%dT%H:%M:%S.%NZ


Therefore, it will work as expected by setting the time field as "2019-01-21T07:11:32.636761000Z".



Ref: https://issuetracker.google.com/issues/123303610






share|improve this answer























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "2"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f950024%2fstackdriver-logging-doesnt-recognize-time-field-in-json-log%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    In the Fluentd configuration for GKE cluster, the time format is defined like this:



    time_format %Y-%m-%dT%H:%M:%S.%NZ


    Therefore, it will work as expected by setting the time field as "2019-01-21T07:11:32.636761000Z".



    Ref: https://issuetracker.google.com/issues/123303610






    share|improve this answer



























      0














      In the Fluentd configuration for GKE cluster, the time format is defined like this:



      time_format %Y-%m-%dT%H:%M:%S.%NZ


      Therefore, it will work as expected by setting the time field as "2019-01-21T07:11:32.636761000Z".



      Ref: https://issuetracker.google.com/issues/123303610






      share|improve this answer

























        0












        0








        0







        In the Fluentd configuration for GKE cluster, the time format is defined like this:



        time_format %Y-%m-%dT%H:%M:%S.%NZ


        Therefore, it will work as expected by setting the time field as "2019-01-21T07:11:32.636761000Z".



        Ref: https://issuetracker.google.com/issues/123303610






        share|improve this answer













        In the Fluentd configuration for GKE cluster, the time format is defined like this:



        time_format %Y-%m-%dT%H:%M:%S.%NZ


        Therefore, it will work as expected by setting the time field as "2019-01-21T07:11:32.636761000Z".



        Ref: https://issuetracker.google.com/issues/123303610







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered May 17 at 2:37









        Akihiro HARAIAkihiro HARAI

        1305




        1305



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Server Fault!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f950024%2fstackdriver-logging-doesnt-recognize-time-field-in-json-log%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

            Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

            Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020